10X: Program Increment Health

About this report

The Program Increment Health Report displays the overall progress of the selected PI via an array of fuel bars on the left of the report, as well as through sprint progress markers by team on the right. The health of the PI is indicated through key metrics detailed below, and displayed using a scale from Worse to Better, where each bar on the fuel gauge equals 20%. 

Summary Program Increment Metrics:

  • Percent Complete: The percentage of stories planned in the PI that have been accepted.
  • Impediments: Based on the number of open impediments for the PI.
  • Risks: Based on the number of open risks for the PI.
  • Test Cases Created: Based on the number of test cases created for the PI.
  • Critical Defects: Based on the number of open critical defects for the PI.
  • Open Defects: Based on the total number of open defects for the PI.
  • Defects Per Dev: Based on the total number of defects divided by the number of developers for the PI.

Per Sprint Program Increment Metrics (by Agile Team):

  • Percent Complete: The percentage of stories completed by per sprint.
  • Impediments: Based on the number of open impediments.
  • Test Cases Created: Based on the number of test cases created to date for the sprint.
  • Velocity (LOE): Based on the story points of the accepted stories per sprint.
  • Velocity (LOV): Based on the value points of the accepted stories per sprint.
  • Stories Split: The stories split per sprint.
  • Task Burn Per Day: Based on the average task burn per day per sprint.
  • Defect Burn Per Day: Based on the average defect burn per day per sprint. 

Navigation

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

  1. Program Increment (PI) must exist in the system and be tied to a program. 
  2. Sprints must exist in the system and be tied to a team. 
  3. Features must be created and tied to the PI. 
  4. Stories, with point values, must be created and tied to features.
  5. Stories must be assigned to the selected sprint. 

How are report values calculated?

The visual indicators displayed in both the "Summary Program Increment Metrics" and the "Per Sprint Program Increment Metrics" are definable within the Jira Align Administration area under the "Program Increment Health Thresholds" and "Iteration Health Thresholds" areas respectively, and apply to all of the metrics below.

Summary Program Increment Metrics:

  1. Percent Complete = (the sum of stories planned) /(stories accepted) yields a percentage. This percentage is then aligned with visual indicators corresponding to the Program Increment Health thresholds defined by your Jira Align administrator. Generally, these are 20% per fuel bar on the fuel gauge.
  2. Impediments = count of open impediments in the PI. Visual indicators from better to worse, are defined using reference values, for small teams 1, 7, 8, 9, and 10 typically define fuel bar level. Where only 1 impediment or less, is rated 100%, while 10 impediments or greater is equivalent to 0% health.
  3. Risks = (the count of open risks) / (total risk count). Like percent complete, this percentage is then aligned with visual indicators corresponding to 20% per fuel bar on the fuel gauge.
  4. Test Cases Created = Count of test cases created over the PI period. The system will then use the defined reference values to set the fuel bar level. Administrators should conduct analysis to determine the average number of test cases created per PI to define reference values. 
  5. Critical Defects = Count of open critical defects for the PI and compared to reference values.
  6. Open Defects = Count of open defects for the PI and compared to reference values.
  7. Defects Per Dev = (Count of total defects) /(Count of developers on the PI).

Per Sprint Program Increment Metrics (by Agile Team):

  1. Percent Complete = (Count of stories completed to date in sprint ) / (Count of all Stories in sprint), compared to Iteration Sprint Health reference values 
  2. Impediments = Count of all impediments to date in sprint compared to Iteration Sprint Health reference values 
  3. Test Cases Created = Count of all test cases created to date for the sprint compared to Iteration Sprint Health reference values 
  4. Velocity (LOE)=  Sum of story points for all accepted stories in the sprint compared to Iteration Sprint Health reference values 
  5. Velocity (LOV)= Sum of value points for all accepted stories in the sprint compared to Iteration Sprint Health reference values 
  6. Stories Split = Count of stories split during the sprint compared to Iteration Sprint Health reference values 
  7. Task Burn Per Day = (Count of tasks completed to date) / (# of days in sprint to date) compared to Iteration Sprint Health reference values.
  8. Defect Burn Per Day =  (Count of defects completed to date) / (# of days in sprint to date) compared to Iteration Sprint Health reference values.

Release_Health_Final.png

 How to interpret this report

This report is a quick way to appraise the overall health of the PI as well as the PI health of the team by sprint. Problem areas quickly jump out as they are clearly visible due to the Harvey Ball icons and color-coding provided for each area. Organizations that analyze performance and adjust the reference values in the Program Increment Health and Iteration Health areas will get more value from these reports. 

 

 

 

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.