Burndown report
We're going to talk about the burndown report. We've spent a little time previously looking at the burndown report in regards to how we use it during running a Sprint iteration, and how we use it with our team. But in this section, we're going to talk more specifically about the report itself and how we read it, and then what kinds of data we can use for a burndown report.
As we already know, burndown is used to measure progress within an iteration and helps us understand whether we are on track or off track from our ideal state. In a burndown, the vertical axis represents the total amount of work that exists inside of that iteration, and the horizontal axis represents time.
Burndowns tell stories. The more we look at them, the more we understand what may or may not have happened during an iteration, and we get pretty good at telling the story from looking at those burndowns. In a burndown, we can burn down all kinds of things, so we can burn down points, we can burn down hours...
