Tuesday, October 30, 2012

The All Mighty Scrum Master

It is absolutely true that a correctly set up team of professionals does not need a dedicated Scrum Master.

Problem statement: However, sooner or later, they will fall in the trap of the everyday ordeal. You can easily recognize it by retrospective action items not done, or a messy Jira, or continuous overcommitment. There might be other signs, specific for your team.

As to why it happens: The answer can be found in team dynamics. Sooner or later, the team reaches the stage after "form-storm-norm-perform". This stage still does not have a name. It is characterized by the old "common sense" taking rule.

Solution: This is the right time to reintroduce the role of the Scrum Master. It must be someone with knowledge of the project history, as well as with a lot of trust from the team. The only missing ingredient from the recipe is human interaction and dedicated discussions on how to overcome the good old common sense. For inspiration how to continue, refer to Beware of Common Sense


No comments: