The Burndown chart is one of the major artifacts of the Scrum framework. Looking at the single chart can give you an indication of how much was planned, how teams are doing over a period of time in a Sprint, and whether teams will be able to achieve what they have committed to.
In this chapter, we covered the importance of the Burndown chart and some typical charts to compare your team state. In the next chapter, we'll cover how you would be able to state team status and progress looking at your team chart.
We also covered how to generate a Burndown chart in GreenHopper for your team. You can use Story points, ideal hours, or business value estimations to generate your Burndown chart.
In the upcoming chapters we will be covering to end a Sprint, generate Sprint report, and also finish an Epic. We will be able to generate different project reporting charts.
We also covered the scope change representation of work in the Burndown chart itself. You can also configure working and non-working...