Program increment progress drill down

About this report

Drillable PI burndown charts are available as an extension of the program increment progress report. Click the Drill Down button on the top-right of the program increment progress report page to access granular burndown charts of themes, programs, epics, and teams working against the program increment or portfolio.

A burndown chart represents work remaining versus time; the outstanding work is on the vertical axis and time is on the horizontal axis. These charts are especially useful for Portfolio Managers and Release Train Engineers for predicting when all work will be completed; it provides a high-level understanding of whether the work for a PI is on track. A toggle is also available to switch the view to burnup charts.

To navigate to this report:

1. Select Portfolios, Solutions, Programs, or Products in the top navigation bar and select the entity you want to view information about.
2. On the sidebar, select Reports in the list of options.
3. Select Program increment progress; the report displays.
4. Select Drill Down on the toolbar.

Prerequisites

1. PI must exist in the system and be tied to a program.
2. Program must exist in the system and be tied to the portfolio.
3. Themes must exist in the system and be tied to a program, PI, and strategic initiative.
4. Epics must be created and assigned to a program and PI.
5. If the portfolio uses capabilities, capabilities must be created and assigned to a program and parent epic.
6. Teams must be created and assigned to sprints.
7. Features must be created and tied to the PI. 
8. Stories, with point values, must be created and tied to features.

How are report values calculated? 

Burndown

1. Ideal burn: Ideal trend downward of effort points from accepted child stories of features from the PI's start date to end date.
2. Remaining: Sum of all effort points from child stories of unaccepted features on each day of the report's time period. 
3. Value Points Remaining: Sum of all value points from child stories of unaccepted features on each day of the report's time period. 

Burnup

1. Start Date: The start date of the PI.
2. End Date: The finish date of the PI, plus one day.
3. Predicted: Predicted trend upward of effort points from accepted stories. The average velocity of the previous 10 completed sprints within the program increment is used to determine the trend.
4. Pessimistic: Predicted Trend times 0.8.
5. Optimistic: Predicted Trend times 1.2.
6. Accepted: Sum of all effort points from accepted stories on each day of the report's time period.
7. Scope: Sum of all effort points from stories on each day of the report's time period.

Notes: 

1. Hovering your cursor over the any chart line will display detailed data in the following intervals, depending on the range of dates displayed in the chart. These intervals are enforced to ensure good chart performance: 
   1. Date range <= 60 days: Intervals provided daily.
   2. Date range <= 12 months: Intervals provided weekly.
   3. Date range <= 60 months: Intervals provided monthly.
   4. Date range <= 120 months: Intervals provided quarterly.
   5. Date range > 120 months: Intervals provided yearly. 
      
      Accepted, Predicted, Pessimistic, and Optimistic lines will follow these interval rules during a current program increment. For example, if you're viewing a chart that covers more than 12 months and uses weekly intervals, the accepted line will end one week after the current date while prediction lines will begin one week after the current date. 
2. Scope lines use historical data snapshots, which may cause data to appear inflated after a deletion or reassignment. For example, If a story is present on May 5, then moved to the recycle bin on May 6, the scope line will display that story's points when viewing May 5. This can happen when changing any data that the chart is using to filter, such as program, release vehicle, and product.

How to interpret this report

As features are accepted, the orange line trends downward. The orange line shows the effort points (LOE) remaining and the yellow line shows the value points (LOV) remaining, so you can choose either effort or value as the burndown display. The blue line shows the ideal burn rate for accepting features. The y-axis is the sum of story points for all child stories of the features. The x-axis is a time period determined by the start and end dates of the PI*.

Notes: 

• *If filtering by a release vehicle:
  • The start date of the x-axis will be the start date of the release vehicle when earlier than the program increment's start date.
  • The end date of the x-axis will be the end date of the release vehicle when later than the program increment's end date. 
• If program increment length is less than 60 days, the Prediction line will not render for the last day of the program increment.
• If program increment length is between 60 days and 12 months, the Prediction line will not render for the last 7 days of the program increment.