In my daily life as a Scrum Master, I witness many crazy situations. I want to share my experiences via this comic series featuring Koos Coach, the silly Scrum Master struggling to understand and master Scrum.
Failing is Learning
Empirical Process Control is at the heart of Scrum and required to work in complexity. Failing is an intrinsic part of learning. Trust and safetly are needed to create an environment in which teams get the space to learn.
Some thoughts:
- Too much tolerance on failing (teams not finishing the work in the sprint for instance) is an impediment for Scrum.
- Too little tolerance on failing (blaming people for mistakes) reduces transparency.
- How is failing perceived in your organization?
The Daily Scrum
The Daily Scrum is a key inspection moment. The Scrum Master needs to ensure that the event takes place. This is true, but the Scrum Master also needs to assess if the team is mature enough to self-organise.
If this story resonates with you, please share:
- What does this behavior tell you?
- How would you call this kind of Scrum?
- What actions can the Scrum Master take to improve the quality of the Daily Scrum?