Your scrum team needs you
This is a companion post to The courage to be creative.Ken Schwaber describes the scrum master as a sheepdog who would do anything to protect the flock, and who never gets distracted from that duty.
The scrum master is the driving force behind scrum. The scrum team relies on the scrum master to ensure they live by scrum's values, enact scrum's practices, and abide by scrum's rules. The scrum master is responsible for bringing all the components of scrum together to function as a process. The scrum team's welfare is the scrum master's highest responsibility. He must demonstrate commitment to the scrum team so they can see that he's devoted to the team and will always protect and help them. However, if the scrum team breaks one of the scrum rules, the scrum master must insist that the team takes steps to ensure that it doesn't happen again. If someone isn't completing work, the scrum master takes the initiative and informs the rest of the scrum team so they can decide how best to help.
The scrum team looks to the scrum master to set them up for success. This is achieved by aligning roles and responsibilities, and organising and facilitating sprint planning meetings, sprint reviews and retrospectives. The scrum master helps the scrum team maintain productivity by removing obstacles, making prompt decisions when required, and by facilitating daily scrum meetings which provide a forum for the scrum team to synchronise, inspect and adapt. Engineering practices and tools are improved so that each increment of functionality is potentially shippable and progress is gauged by the scrum master and made visible to all parties with a public burndown chart.
The scrum master helps the product owner and the scrum team work together so that the product owner can drive the development effort directly. He also coaches the product owner on how to maximise the return on investment by selecting the most valuable product backlog to be developed in a sprint.
Tags: agile, scrum
posted by Simon Baker @ permalink
blinklist :
del.icio.us :
digg :
furl :
simpy :
spurl :
reddit
2 Comments:
Should scrum master code?
Please say only "Yes" OR "No"
Scrum master MUST code:
Scrum master MUST NEVER code:
Scrum master COULD code:
Scrum master SHOULD code if (s)he wishes to:
Scrum master MUST code: No
Scrum master MUST NEVER code: No
Scrum master COULD code: Yes
Scrum master SHOULD code if (s)he wishes to: No
But the world's not black and white. And it's not realistic to make binary rules for the scrum master. Personally, I prefer that the scrum master does not code. As a servant leader and facilitator for the team it's important that the scrum master maintains some neutrality and sits on the edge of the team, helping. If the scrum master is coding then a) his undivided attention is not being given to assisting the team through the scrum master duties, and b) it's possible that as a coder the scrum master becomes part of any problems.
Post a Comment
Links to this post:
Create a Link
<< Home