Rules

Secret ingredients to quality software

Edit
Info

Watch - Do You Get Regular Updates on Costs and Progress (aka Project Progress, Burndown, etc.)?

Last updated by Tiago Araújo [SSW] on 27 Feb 2021 02:00 am (4 months ago) See History

You're the one paying the bills, make sure you know where the costs are and how the project is progressing.

Insist on receiving these 3 reports in every Review Meeting:

  • Project Progress ($ spent)
  • Burndown (ETA)
  • Story Overview (testing quality)

Let's look at those 3 reports:

1. Current project costs

This allows you to see the actual costs of the project on a weekly basis.

projectprogresscapture
Figure 1: Project Progress – There is $30k spent and $8K outstanding

2. Current hours remaining and hours completed for the current sprint

burndown
Figure 2: Burndown report - Shows the progress of the team in the current sprint – ETA is March 29 and Ana has no work to do

Questions that the Burndown and Burn Rate report help answer:

  1. Is the team likely to finish the iteration on time?
  2. Will the team complete the required work, based on the current Burn Rate?
  3. Has the team added work to the iteration?
  4. How much work does each team member have?

See how to use the Burndown and Burn Rate Report.

3. Story Overview - See how each task is tracking

storiesOverview
Figure 3: Stories Overview report - Shows the progress of the User Stories in the current sprint and nothing has been tested and no active bugs

Questions that the Stories Overview report help answer:

  1. How much work does each story require?
  2. How much work has the team completed for each story?
  3. Are the tests for each story passing?
  4. How many active bugs does each story have?

See how to use the Stories Overview Report.

Adam CoganAdam Cogan

We open source. This page is on GitHub