Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Looking for the setup guide or training materials? Click here or View the dashboard in Jira here

*NOTE: EazyBI labels Features as EPIC. If you see EPIC on a report it is actually Features in JIRA.


Program Backlog Health

This pie chart shows the current status of Program features on the backlog. As the next Program Increment nears there should be less work in Analyzing or Refining state and more work in Ready for PI state. If there are many features in Analyzing and Refining consider adding WIP (work in progress) limits to your feature kanban to increase throughput and preparedness for PI Planning.

Current Program Backlog Composition


This pie chart shows the current Feature backlog make-up by type. A healthy backlog is comprised of:

  • Features that deliver user functionality
  • Enablers that deliver architectural runway and system enhancements
  • Exploration Enablers that represent activities needed to develop an understanding of system solutions or customer needs

A program should measure and track how much of their PI capacity is going to Enabler work so system operation and optimization can be reduced over time. As a system matures operational spend should reduce allowing more capacity for feature based user enhancements.




All Program Teams backlog composition at PI Start

<insert report screenshot here>

This pie chart shows ...




Work Delivered by Type per PI

<insert report screenshot here>

This pie chart shows ...



<insert report screenshot here>

Features Started and Closed per PI


This report shows the ...



Features in Status on PI Start Dates


This report shows the ...

<insert report screenshot here>



Average Age to Feature Resolution


This chart allows you to see ...

<insert report screenshot here>






Cumulative Flow Diagram (CFD)

This is an area chart that shows the various statuses of work items for an application, version, or iteration. The horizontal x-axis in a CFD indicates time, and the vertical y-axis indicates cards (issues). Each colored area of the chart equates to a workflow status (a column on your board). Status groupings are used for standardization. (See Status Grouping Matrix for more detail)

The CFD can be useful for identifying bottlenecks. If your chart contains an area that is widening vertically over time, the column that equates to the widening area will generally be a bottleneck.

CFD shows the tasks at each stage of the project over time. In the example on the left, the purple area represents the tasks that are completed, the yellow area represents items in development, and the light blue area covers the backlog refinement.

CFD may seem complicated at first but upon closer look, it can provide a number of useful insights. For example, the vertical axis of the chart shows the number of tasks currently being worked or completed. 

The horizontal line represents cycle time. 

Click here to read more about CFD


  • No labels