LACE (CCSQ Lean Agile Center of Excellence)

Page tree

Versions Compared

Old Version 4

changes.mady.by.user Seth Evans

Saved on

compared with

New Version 5

changes.mady.by.user Seth Evans

Saved on

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


Program Backlog Health ::

Historical Delivery by Work Type

Current Program Backlog Composition :: Time in Status :: Defect Management :: Average Time to Realized Value :: Planning Variance :: Cumulative Flow

 

Anchor
PgrmBacklogHealth
PgrmBacklogHealth

Program Backlog Health

Section


Column
width50%


Column
width50%

This pie chart shows the different work item types by percentage in a team’s backlog. 

Similar to the program backlog, teams are responsible for applying capacity allocation to team backlog in order to determine how much of their total efforts can be used for each type of activity in a given iteration. 

The composition of the team's work helps optimize the delivery of value.

This chart shows:

  • Value delivery through enablers and user stories.
  • The team’s support of program capacity allocation.
    • If any adjustments to capacity allocation should be made.



    Anchor
    PgrmBacklogComposition
    PgrmBacklogComposition

    Current Program Backlog Composition


    Section


    Column
    width50%

    Image RemovedImage Added


    Column
    width50%

    This chart shows the different work item types by percentage in a team’s backlog. Similar to the program backlog, teams are responsible for applying capacity allocation to team backlog in order to determine how much of their total efforts can be used for each type of activity in a given iteration. 

    The composition of the team's work helps optimize the delivery of value.

    This chart shows:

  • Value delivery through enablers and user stories.
  • The team’s support of program capacity allocation.
    • If any adjustments to capacity allocation should be made.

















    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.



    Anchor
    RealizedValue
    RealizedValue

    Average Time to Realized Value

    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

    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