Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Anchor
PgrmBacklogHealth
PgrmBacklogHealth

Program Backlog Health

Section


Column
width50%


Column
width50%

This pie chart shows the current status of Program features on your backlog. As you get closer to the next PI start date you should see less work in Analyzing or Refining state and more work in Ready for PI state.



Anchor
PgrmBacklogComposition
PgrmBacklogComposition

Current Program Backlog Composition

Section


Column
width50%




Column
width50%

This chart shows the


















Anchor
DefectManagement
DefectManagement

Defect Management

Defect Management chart shows the average life of defects and bugs, number of defects and bugs created vs resolved, and how many defects and bugs are currently unresolved

This chart also shows the average resolution days within a given time to comprehend the number of defects/ bugs arising each iteration which helps with built-in quality by reducing defect debt during each iteration.



New Report



Anchor
RealizedValue
RealizedValue
Average Time to Realized Value
New Report

This report shows the average resolution time for all team level issue types.

  • This report represents the total cycle time of an issue, from the time of creation until the time of resolution
  • Ideally

    the

    line on this chart remains as flat as possible. but a decreasing trend indicates improvements

    Potential Explanations for upward slope:

  • Unused backlog items not being removed or abandoned
  • Team size is not adequate for workload



    Anchor
    PlanningVariance
    PlanningVariance

    Planning Variance

    New Report

    This chart allows you to see the number of points completed based on the commitment at the beginning of the iteration. In high performing teams, this variance should be zero most of the time.

    Potential reasons for seeing variance:

    • Work injection from outside the team
    • Work not well understood before commitment
    • Adjusting story points during the iteration
    • Splitting stories within the iteration
    • priority changes post iteration planning 
    • underestimating efforts
    • changing in teams composition

    The orange line, which represents the average variance, should remain at or close to zero.








    Anchor
    CumulativeFlow
    CumulativeFlow


    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