ISG Playbook
APIsLooking for the setup guide or training materials? Click here or View the dashboard in Jira here
Current Program Backlog
HealthComposition :: Current Program Backlog
CompositionHealth ::
Teams Backlog atFeatures in Status on PI Start Dates ::
Work Delivered by Type per PI ::Features Started and Closed per PI ::
Features in Status on PI Start Dates :: Average Age to Feature Resolution ::Team Backlog Composition at PI Start :: Work Delivered by Type per PI :: Cycle Times Report :: Program Feature Cumulative Flow
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
This graph shows the number of features in a status at the start of each PI
What to expect from the chart:
- The Ready For PI numbers would expand until program performance normalizes, as in the chart to the left
- The funnel numbers will increase over time as potential work is identified
- Refinement numbers will be higher when Ready for PI numbers are lower
- The number of items in the Analyzing status should mirror the WIP limit on the program kanban
| Anchor | ||||
|---|---|---|---|---|
|
This chart shows the number of features started (blue line) and the number of features completed (grey line). The curve of these lines should be similar with minor deltas.
Note: The numbers for the current PI reflect the state of features in the PI as of today. It does not represent all planned work for the PI.
| Anchor | ||||
|---|---|---|---|---|
|
This chart shows the ongoing average days of features created, and more importantly the average amount of days of all features from the beginning of implementation to playcompletion. Ideally the average stays significantly below the timebox of a Program Increment
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
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
...