ISG Playbook
APIs
The CCSQ Program Dashboard allows Programs to easily access key data and metrics to make informed decisions, ask valuable questions, and take action. The dashboard is designed to highlight Program Increment preparedness and delivery metrics. Read about each chart and how to interpret it below.
Looking for the setup guide or training materials? Click here or View the dashboard in Jira here
Program Backlog Composition
This pie chart shows the current Feature backlog make-up by type. A healthy backlog is comprised of:
- Features - deliver user functionality
- Enablers - deliver architectural runway and system enhancements
- Exploration Enablers - activities needed to develop an understanding of system solutions or customer needs (requires Feature to be labeled "Exploration Enabler")
Compare this chart to PI capacity allocation for the PI to ensure the backlog supports the program's needs for features, Enabling work, and technical debt.
Program Backlog Health
This pie chart shows the current status of Program features on the backlog and can be used to measure readiness for the upcoming PI (Program Increment). As the next PI nears you would expect an increase of 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.
Enterprise Work Management Standards defines the scheme for labelling enablers, using one of the four enabling types(Architectural, Compliance, Exploration, Infrastructure) as defined by the Scaled Agile Framework (SAFe). To support enterprise clarity into how much of each type of enabling work is being completed, please use the enterprise label schema for all enablers. When adding the appropriate enabler labels, also remove the enabler label if you are currently using it to identify enablers in your program. Enabler labels exist in Jira, in the format <EnablerType>_Enabler, ie. "Architectural_Enabler" for more information, select the "Enablers" tab on the Enterprise Work Management Standards page.
Enterprise Work Management Standards for feature workflow leverage the Scaled Agile Framework's (SAFe) program Kanban. The use of statuses not included in the SAFe program Kanban may cause your program's data to be inaccurate and create disconnects and the associated communications overhead to clarify. To ensure the best quality of data, ensure the timely and accurate transition of work items through the full workflow, providing program and enterprise stakeholders an accurate picture of the overall preparation level of the program backlog for upcoming PI's. It also benefits program leaders, as they can see if the backlog supports the intended capacity allocation for the upcoming PI. Learn more about the Enterprise Standard Program Kanban Statuses and Workflow by selecting the "Features" tab on the Enterprise Work Management Standards page.
Features Started and Closed per PI
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
- Helps program leaders determine if the backlog supports the intended capacity allocation for the upcoming PI
Enterprise Work Management Standards for feature workflow leverage the Scaled Agile Framework's (SAFe) program Kanban. The use of statuses not included in the SAFe program Kanban may cause your program's data to be inaccurate and create disconnects and the associated communications overhead to clarify. To ensure the best quality of data, ensure the timely and accurate transition of work items through the full workflow, providing program and enterprise stakeholders an accurate picture of the overall preparation level of the program backlog for upcoming PI's. It also benefits program leaders, as they can see if the backlog supports the intended capacity allocation for the upcoming PI. Learn more about the Enterprise Standard Program Kanban Statuses and Workflow by selecting the "Features" tab on the Enterprise Work Management Standards page.
Features In Status at PI Start
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.
The Enterprise Work Management Standards Best Practice for Feature management is to close Features within the PI they are delivered. However, the report will include any features closed within the first 8 days of the subsequent PI. As with all work, the Enterprise Work Management Standards define the timely and accurate transition through the program workflow. For more information on the Feature Workflow, select the "Features" tab on the Enterprise Work Management Standards page.
Cycle Time
The Cycle Time report is used to measure the amount of time it takes to complete a Feature. It can be used to identify bottlenecks or inefficiencies in a process, and can help a Program to improve their efficiency and productivity.
Resolution days: The total number of days from when the issue was created to when the issue was resolved.
The Minimum and Maximum resolution days shows the range of time it takes for a Feature to be completed, from the shortest amount of time to the longest. The point at the time boundary for Min/Max resolution days represents the Feature that was open for the shortest or longest time, and was resolved within the time period. This can be useful for identifying outliers or unusual occurrences in the data, and can help a Program understand the typical range of time it takes for a Feature to be completed. The minimum and maximum resolution days can also be used to identify trends and patterns over time. Drilling through the Min and Max will show the complete list of issues resolved during the time period, and their total number of days from when the issue was created to when the issue was resolved.
The MAX cycle time indicator represents the longest amount of time it took for any Feature included in the report that was moved from an 'In Progress' status to a 'Done' status. This metric can be useful for identifying outliers or unusual occurrences in the data, and can help a Program understand the typical range of time it takes for a Feature to be completed. By analyzing the MAX cycle time indicator, a Program can identify areas for improvement and make changes to reduce the overall cycle time. For example, if the MAX cycle time indicator is significantly higher than the Average days in cycle indicator, it may indicate that there is a bottleneck or inefficiency in the process that is causing delays. In this case, the Program can focus their efforts on addressing this issue in order to reduce the overall cycle time.
The Average days in cycle represents the average amount of time it takes for Feature to be completed. This metric is calculated by dividing the total time it takes to complete all of the Features included in the report by the total number of Features. The average cycle time can be a useful metric for identifying trends and patterns over time, and can help a Program identify areas for improvement and make changes to reduce the overall cycle time. Ideally, the average cycle time stays below the time-box of your Program Increments. If you see an average higher than your Program Increment you may need to improve your work item management practices to ensure Features are moving to the proper working states during the PI.
This chart shows the approximate percentages of all teams' backlogs work items open at the start of the PI. The horizontal x-axis indicates the percentage of all ART teams work items while the vertical y-axis indicates the PI name.
Each chart represents work item types used by most programs in CCSQ:
User Stories include (Story, Action Item, Improvement, Insight, Prb/Enh); Team Enablers include (Portfolio Enabler and Enabler); Research includes (Spike, Research Design, Discovery Initiatives) and Bug (only Bug).
To support enterprise clarity into backlog composition and delivered work please use one of the existing User Story, Enablers, or Research work item types. Selecting the right work item type is critical to get value from both charts.
Visit the "User Stories", "Enablers", and "Research" Tabs on the Enterprise Work Management Standards page to get more detail about how ART teams should use existing work items and label tagging to represent program work on their backlog.
This chart shows the percentage of work item types completed by all program teams in each PI. The horizontal x-axis indicates the percentage of all ART teams work items while the vertical y-axis indicates the PI name.
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).
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