It’s hard enough to deliver a small increment of a product, yet we often find ourselves and our teams in positions where they need to deliver a whole product, project or release in 1 go. No change for mistake. And you know what happens: when failure is not an option, failure is the only option!
About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.
There are many ways to fail, but there are some ways that are just way too common. Tony shares what is probably the most common way to fail at Scrum. In this episode we also share 7 other tools and tips for Scrum Masters.
Tony is an Agile coach working with a global insurer wanting to become more Agile. Starting his career as a software developer working with Toyota he has a background in Lean and came across Agile in 2010 as part of a test and learn initiative. He is keen to help leaders understand their role in creating an environment where Agile can flourish. To support this he has been working on a game inspired by the research of Michael Spayd and Lyssa Adkins to support this journey.
Many will say that helping team meeting commitments is how Scrum Masters best do their work. Seann shows us another side of the job: developing teams. Helping them develop their skills, their collaboration, and focus on outcomes, not outputs.
We discuss that knowing “why” is often more important than focusing on the work at hand, and we mention the book by Simon Sinek: Start with Why.
About About Sean Dunn
Sean is an Enterprise Agile Coach with IHS Global. He has been involved with agile development for 8 years as a developer, product owner, and agile coach. Prior to his exposure to agile development Sean spent 13 years in the Canadian Army. In fact, Sean is known to point out that the Army is far more agile than most people think.
That background in the Canadian Army influenced his view of Leadership and the role of Leadership in creating and developing great teams.
You can connect with Sean Dunn on LinkedIn, check out Sean Dunn on the Scrum Alliance or email him at email@example.com.
Check out Sean Dunn’s blog on leadership.
Technology enthusiast. Change artist. Culture hacker. People focused. Helping organizations provide their employees with the most meaningful and fulfilling experience they could have while delivering solutions that change the world. Ebenezer is also a Tech Director at Mannheim.
You can link with Ebenezer Ikonne on LinkedIn, and contact Ebenezer Ikonne on Twitter. You can also read his thoughts on Agile on his blog.
Talking about self-destructive behaviours may make people feel they are being judged, and Sebastian prefers to stay away from judgements. Instead, he wants to focus on behaviours that affect the team and must be addressed. Sebastian also shares with us a sabotage technique that is sometimes used by team members and teams in their work.
The sabotage technique is also available in the Simple Sabotage Field Manual a document used by a precursor to the CIA to explain how individuals could sabotage countries, factories and other potential targets. Are you aware of all the sabotage behaviors your team can perform on itself?
About Sebastian Schürmann
Sebastian has an extremely strong work ethic, a great passion to his work, unwavering desire for excellence, and unabated willingness to share his rich knowledge.
Driven by his strong work ethic, he takes several key roles: as scrum master, agile coach, mentor, as protector of the young development teams, after all, a humble leader who takes risks and responsibilities at extremely critical moments, creates a vision which the other follow by heart – with excellent outcome.
You can find Sebastian Schürmann on twitter, and link with Sebastian Schürmann on LinkedIn.
You can find Sebastian Schürmann’s website, and his blog.
What can you do, as a Scrum Master when the team is stuck in a pattern of negativity and self-destruction? Stephen explains the situation of a team that was in that situation, and what were the symptoms that characterized the problems the teams were facing. He discusses how communication suffers, how the us versus them dynamic emerged and how hard it was to help the team in that situation. We also discuss the techniques you can use to help the team get out of that pattern of self-destruction.
About Stephen Thomas
Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.
Being a slave to the backlog, and just going through the motions without interacting with the other team members or stakeholders. This is further amplified in Death-march like projects.
About Peter Hilton
Peter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.