Matt tells us about a failed agile transition, and what he learned from that experience. He also talks about one of the biggest threats to agile transitions all over the world: the “shiny object syndrome” that affects many organizations today.
Matt also recommends a book: Scrum and XP from the trenches by Henrik Kniberg: http://www.amazon.com/Scrum-Trenches-Enterprise-Software-Development/dp/1430322640
If you thought that Jeff Kosciejew learned about being a great Scrum Master from his software industry experience you’d be wrong. Jeff learned a lot about being a servant leader, and a champion for a high-performance culture in his days as a Bank Manager. He shares his story of how his Scrum-like principles and values helped him create a superior Bank experience for his customers. He details how he was able to build a self-organizing team in his Bank branch and how he learned to be a servant leader. It’s all about people, people! :)
Jeff Kosciejew discusses the three key questions for defining success and shares how his experience as a musician informed the definition of success as a Scrum Master. A very inspiring story of how Scrum Masters can fundamentally affect their team’s performance and each of the team member’s well-being.
Jeff Kosciejew shares his own, hard-earned, experience on how to hire great people. Including how to know in advance what skills you need, using conversation as a way to filter out candidates that are a bad fit and the Agile Coaching Competency framework. His most important question in recruiting interviews is one he asks himself: “will this Scrum Master fit our culture?”
Jeff, also refers to Jason Little’s personal Agile Coach NPS, a way to evaluate your own impact in the team and organization you work for
The worst enemy of this particular team, according to Jeff Kosciejew, was the pattern of avoidance. Avoiding problems is one of the pitfalls that our teams deal with.
On this Fail Monday episode, Jeff Kosciejew shares his ideas on how to look beyond the teams as the focus of our work as Scrum Masters. He also shares his very colorful and diverse history, and how being a Bank Manager helped him become a better Scrum Master.
Peter discusses how “variation” can affect negatively the team, and what benefits can come from acting on, and reducing variation.
Peter refers to the book where he first read about the effect of variation on work. This book was Freedom from Command and Control by John Seddon (http://www.amazon.com/Freedom-Command-Control-Rethinking-Management/dp/1563273276)
Peter also shares a tip on how to get management to be aware of what is discussed by teams during the retrospective, in order to create trust between management and teams.
Peter shares his unusual idea on how measuring the use of the word Scrum can give you real insights to your success as a Scrum Master.
Peter tells us the story of a ScrumMaster that seemed like a good choice but was too shy to help the team grow. He explains how he views the role of the ScrumMaster, and especially what is needed to help them evolve.
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.