Daily Scrum — story by story
This post is part of 101 ideas for agile teams.
Context
It’s hard to get a picture of the progress of each Sprint backlog item during the Daily Scrum when each team member answers the three questions (what have I done, what will I do today and what impediments exist) in a round-robin. There is a lot of jumping between User Stories — back and forth.
Action
Instead of everybody answering the three Daily Scrum questions one after the other, go through the Sprint backlog items from top to bottom. For every item, the team states what’s the progress since the last Daily Scrum, what impediments there are to complete the item, and what the team will do to make progress on the item till the next Daily Scrum.
What you gain
More focus on Sprint backlog items than on individual team members, which fosters collaboration and getting items done.
Less repetition or “well, Tim already said everything, because I pair programmed with him”.
How to strengthen
The Scrum Master can moderate the Daily Scrum and help the team to use this method.
Risks
Team members can hide, because not the team members stand in the light but the Sprint backlog items. But remember, Scrum is not about controlling.
More ideas at 101 ideas for agile teams
Many thanks to bbv Software Services for making this blog post possible.
