A sprint burn-down chart tracks the size of the sprint backlog over the course of the sprint. During the sprint retrospective, the burn-down chart can provide valuable data about how the sprint went. Mike Sutton uses annotations to capture more data on the burn-down chart, making it even more useful during the retrospective.
During a sprint, the burndown chart keeps the team, and anyone else who looks at it, informed as to how big the sprint backlog currently is, and how quickly it is shrinking. Ideally, the chart is trending down such that it will hit 'zero work left' at or before the end of the sprint
A retrospective timeline is a tool for helping the team reconstruct the key events of the sprint. A common approach is to mark off a timeline on a wall or whiteboard, and have team members put sticky notes on the timeline for events that occurred. The notes may say things like: "Mike joined the team.", "Build was broken", "Build finally fixed!", "Big demo for customer went well!", "The big bug was reported", and so on.
Mike Sutton described how he is capturing timeline information, as it happens, on the team's burndown chart. When a team member reports an impediment at the daily stand-up meeting, the impediment is recorded on a sticky note. The sticky note is then placed on the burndown chart, next to the trend line point for that day. The sticky note includes a short description of the impediment, and any relevant context. When the impediment is resolved, the resolution date is added to the sticky. The sticky note remains on the chart. When the team does their sprint retrospective, the can easily refer to the annotated burn-down chart to help them remember the key events of the sprint.
What types of data does your team collect and use during retrospectives? What tools do you use to collect the data? Leave a comment and share.