This article examines 3 different ways to monitor how a sprint is progressing.

These are:

• Burndown
• Cardwall
• Mid-Sprint checkpoint.

Burn Down

The burn down is a graphical representation of how the team is progressing during the Sprint.  It compares work remaining verses time left.  The Y-Axis represents the work-remaining in hours, while the X-axis represents the time.

The ideal burn-down rate is the perfect rate a team would burn. It is often shown on the graph to be used as a comparison to provide a better understanding on whether or not the team is on track.

There are several tools which can be used to generate a burn down chart. A Spreadsheet application such as Microsoft Excel or Open Office Calc can be used; software is also available which will generate a burn down.

Card Wall

The card wall provides an easy way to quickly determine how the team is progressing. The card wall is typically in the team room and team members are encouraged to move the cards as they pick up sprint tasks. There are typically columns to show state of each sprint backlog item such as Not Started, In Progress, and Complete.

During sprint planning team members can create each task while they task out backlog items. That will save the scrum master some time.

The card wall is simply a communication tool that has been proven to work well. Electronic versions of card walls do exist and are available but I have found that the traditional card wall makes the work a little more tangible and is normally within a quick glance of the team members.

Mid-Sprint Checkpoint

The mid-sprint checkpoint is simply a pulse check. If the burn down or the card wall shows that it does not appear the team is on track for completing all of their sprint goals, the mid-sprint checkpoint provides the opportunity to address that.

The value of this checkpoint approach comes into play for Sprints that are longer term, for example a 4 week or monthly sprint.

If the team is not on track it is, this is where options are looked at for getting back on track. This could mean coming up with a plan to make a slice ‘thinner’, (still try to have something deliverable but maybe not have so many bells and whistles). A quick meeting could be called after the daily scrum / standup to spend 15 minutes brainstorming on ways the team can get back on track.

Mid-Sprint checkpoints are not typically part of the agile ceremonies however I have found it has been useful in the past. This may also be more useful on newly formed teams. Teams that have been together for a longer time typically will do this on a daily basis and most likely will not need this.

See the video version of this at SsZ.tv.

Posted by Brian Lawrence.