Introduction
No one in our shop questions the value of having a highly visible burndown chart in order to track our daily progress, but as we move to a more distributed team with developers working remotely or from home, we are presented with some challenges in both updating and making the burndown chart available.Discussion
Our teams will generally update the burndown charts daily. We simply add the number of remaining story points (for the current release) as recorded in our issue tracker and mark that number on our burndown chart. The chart was usually kept in the hallway or some other room where it was highly visible.With distributed team members, we had to find a way to share a burndown chart easily. We tried several methods and finally decided to go with a Google spreadsheet. The spreadsheet allows us to display a chart for our burndown, update it daily and share it with management or testing.
Sample of the Completed Burndown |
Step 1: Create a Google Spreadsheet
You'll need to start by creating a new Google spreadsheet with two sheets. The first sheet should be named chart and the second sheet named data.Detail of the 2 sheets |
Step 2: Setup the Data Columns
Select the DATA sheet, and add the columns that you will need for your chart; Sprint, Date, Actual, Projected, Ideal. Sprint is used for reference and does not display in the burndown chart.In the chart edit dialog, set the data range to "DATA!B1:E100" and select line chart as the type. Select OK or update.
0 comments :
Post a Comment