CHOW #8– Updating the burn down

You could be a Scrum Master or a Team Member in a Scrum team. Everything is going well, except that the work remaining is not getting updated in the tool you are using. The team members forget to update, delay the updates. As a result though you learn a lot on what progress was made the previous day towards accomplishing sprint goals, you are unable to figure how the team is doing overall. What could be done to improve this situation?

Suggested solution:

Solutions tried out in different situations:

  1. Bring up the burn down chart at the start of the daily scrum, it works like a charm. The team members who have not updated their progress and work remaining will add “missed updating, will do right after the daily scrum”. The moment this data is made use of by the team, the need to keep it updated automatically syncs in.
  2. One team arrived at a unique mechanism, added a fourth question “Whether I have updated my progress and remaining hours?” This was suggested by a team member fresh out of college, I was skeptical, but thought why not give it a shot. This too works, tried in many teams. The beauty is that the fourth question is a transient one, in the sense that it gets dropped after a while, as it becomes redundant.
  3. This is done by those who have done scrum before, at the start they evolve team norms and the updating of progress and remaining hours is agreed upon as a team norm.
Leadership, Communication; Culture
What do you think?

One Response

Leave a Reply

What to read next