Before we create the burndown, let us give a quick
explanation of what a burndown chart is for. An XP or Scrum project uses some
type of report like this updated frequently (in our case 2 - 3 times a week).
Use the burndown chart to show how many points remain in your project. The
chart also shows the (hopefully) downward trend of the points completed for each
As we work through each iteration, our team finishes a
certain amount of points. This series of articles assumes that we capture
those points for the team in a scenario work item in TFS. With TFS as the backend
for your reporting, keep in mind that you have version information there that
can be added to the data shown in this report.
For the data to create the burndown chart, I assume that TFS
fields are used in the same manner elaborated on in Parts 1 and 2. We use the
MSF Agile templates and Rank is used to capture iteration information. The Rough
Order of Magnitude field captures the number of points for the story.
Some of the other fields can be used when you need to do
more analysis. For instance, the date fields are helpful when looking at when
more points are added to the total. Using that data for a report is beyond the
scope of this article, but we may explore that later.