MILESTONE BURNUP CHART

The milestone burnup chart allows you to track your progress towards a milestone such as completion of a customer project or a new product release. In addition to being able to track your progress with a burnup chart, you also get a forecasts based on your team's past velocity. 

 

TRACK YOUR PROJECT PROGRESS

Screen Shot 2014-12-16 at 17.26.40.png

The milestone burnup chart consists of two lines, a yellow line representing the project scope, and a white line representing the work done. As time progresses the white line approaches yellow line helping you to track how much work is still to be done. The numbers can represent estimations, if available, or simply task counts. 

 

 ARE YOU IN DANGER OF A SCOPE CREEP?

The yellow dotted line shows the total amount of work allocated for the project and the changes made to the scope along the way. Whether you're working on a new product release or a customer project, you'll be faced with a situation in which you need to manage the scope of the work and start saying no to all new feature requests that are pouring in. 

Screen Shot 2014-12-01 at 12.40.48.png
 

WHAT ARE THE LIKELY SCENARIOS FOR COMPLETION?

Screen Shot 2014-12-01 at 17.50.12.png

What's really cool in this chart is that you can get forecasts based on your team's historical velocity. Once your team's velocity will stay within the same boundaries as in the past, it allows you to gauge your worst/best/most likely completion dates. Avoid scope creep by having a real-time view to your milestone progress! 

 

 

Learn more



Common questions

What do the numbers on this chart mean?

The milestone burnup chart is based on monitoring the completed tasks and non-completed tasks. The white line represents the number of tasks that are completed. The yellow line represents the scope of the project, it is the number of the completed and non-completed tasks. The difference between those is the amount of work that remains to be done. 

How is the most likely completion date estimated?

The forecast date is calculated by taking an average of the team's velocity and the remaining scope, and then calculating how many days it would take to complete the remaining scope at that velocity. The best and worst case dates are calculated in a similar fashion, but the best and worst two weeks are ignored if there's more than 5 weeks of velocity history available.

How is the team velocity calculated?

The velocity trend on the bottom right of the chart shows the number of completed tasks, or the sum of their estimates, per calendar week for the past 10 weeks. The weekly velocity is the average of last 10 weeks (or as many as there are available) except:

- Leading zeros are filtered out (but if there are zero weeks after one non-zero week then those are included)

- The highest and the lowest values are filtered out as outliers

How long will it take before you start to see data?

This depends on how quickly you start completing tasks. The chart is shown after there is at least one whole calendar week where at least one task has been completed.

My team is agile. How could we possibly do longer time planning?

We strongly encourage you to ship incremental releases as quickly as you possibly can. The milestone burnup chart is useful for tracking a larger body of work that may consist of several product increments, which you want to bundle together when tracking and communicating progress.