10X: Program Increment Burnup by Feature

About this report

The Program Increment Burnup by Feature report shows the feature burnup for the PI, providing a detailed view, by feature, of work that has been accepted. A burnup chart shows how much work has been completed as well as the total amount of work. The accepted work is on the vertical axis and time is on the horizontal axis. This chart is especially useful for Portfolio Managers and Release Train Engineers for insight into the Teams' ability to deliver the in-scope features as planned. The display can be filtered by PI, program, release vehicle, product, theme group, and Scrum Masters/product owners.

 
Prerequisites

  1. PI must exist in the system and be tied to a program. 
  2. Features must be created and tied to the PI. 
  3. Stories, with point values, must be created and tied to features.

Note: If a feature has multiple program assignments, only the stories with a program that matches the Configuration bar selection are included in the report.

How are report values calculated? 

  1. Start Date = Start Date of PI minus one day (for example, the chart for a PI starting on June 1 will start at May 31)
  2. End Date = Finish Date of PI plus one day (for example, the chart for a PI ending on August 1 will end at August 2)
  3. Ideal Burn = Sum of all Effort Points on child stories of features on each day of the report Time period
  4. Accepted = Sum of all Effort Points on accepted child stories of accepted features on each day of the report time period
  5. Value Points Accepted = Sum of all Value Points on accepted child stories of accepted features on each day of the report time period
  6. Predicted = Predicted trend upward of Effort Points on accepted stories. The Predicted daily burn rate is calculated based on the sum of all scrum (Agile-type) teams in the programs’ average velocities during their last 5 completed sprints.
    Note: For detailed information on the Predicted daily burn rate, as well as the underlying team velocities used in the calculation, select the Burn Details button at the top-right of the report.
  7. Optimistic = Predicted Trend * 1.2
  8. Pessimistic = Predicted Trend * 0.8

PI_Burnup_by_Feature.png

Notes: 

  1. Effort and Value points for a feature are credited on the day the feature is accepted. Only Effort and Value points of accepted stories will be credited.
  2. If there are un-estimated child stories, those stories are not reflected in the scope or accepted numbers, as they do not have any points allocated to them. 
  3. The Program Increment Burnup by Feature will show the aggregated accepted story point totals of stories tied to the same PI selected in the Configuration bar.  The burndown may show points from stories not directly related to the selected PI, which may result in different scope lines on the burnup and burndown charts.
  4. If effort points are added or removed during the PI, the scope line will adjust upwards or downwards accordingly.
  5. If the accepted line is trending upwards slower than the Program Increment Burnup by Story accepted line, this is because stories are being accepted, but the parent feature is not being accepted. This indicates working on too many features at once without completing them, and/or orphaned stories being accepted that have no parent feature. Use the Work in Process report and the Work Tree report to identify these two issues. 

 

How to interpret this report

This burnup chart shows a detailed view, by feature, of what is accepted: LOE (dark blue line) or LOV (light blue line). The orange line shows how overall scope changed during the PI. If the PI is not yet finished, you will see three projected lines on the end of the orange accepted line—these predict normal, optimistic, and pessimistic trends for acceptance for the remainder of the PI based on previous acceptance rate. Use this chart to understand if you have too much scope in the PI (the orange line) to be able to finish on time. If the predictor lines do not approach the top of the orange line, you may need to decrease scope for the PI.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.