“Value stream flow metrics” dashboard template

This dashboard provides you with data that lets you analyze and measure the flow of value through a value stream. Flow metrics help you assess how efficient your value streams are at delivering value (feature work items) and meeting outcomes (program objectives). You can also use the metrics to help you identify bottlenecks and areas for process improvement.

Controls on the dashboard

Use the following controls to configure the dashboard:

Program	“Dropdown” control that: contributes to populate the options in the Program increments and Flow item types controls filters all charts for the program your work items are associated with
Program increments	“Dropdown” control that: contributes to populate the options in the Flow item types control filters all charts (except for Work in progress charts) for data relating to specific program increments that your work items are planned for
Flow item types	“Dropdown” control to filter all charts (except for the Business results and Key results charts) for specific types of work you want to report on Flow items are Jira Align capabilities or features with a Type field set to one of the following options: Architectural: Work that represents improvements and refactoring of development architecture. Business: Work that represents new value to the business. Debt: Work that represents technical debt, such as code refactoring. Defect: Work that represents fixes for quality problems that affect users. Enabler: Work that represents technical requirements for providing additional value. For example, building out more architectural runway for new technology. Non Functional: Work that represents documentation, process improvements, and other efforts that do not result in functional features or code. Supporting: Work that represents efforts that must be taken on outside of new value delivery, such as production support and maintenance. Risk: Work that represents security, privacy, or compliance. Not set: Work that has not yet been classified as one of the choices above. This category does not include items with an empty Type field.

Program

“Dropdown” control that:

contributes to populate the options in the Program increments and Flow item types controls
filters all charts for the program your work items are associated with

Program increments

“Dropdown” control that:

contributes to populate the options in the Flow item types control
filters all charts (except for Work in progress charts) for data relating to specific program increments that your work items are planned for

Flow item types

“Dropdown” control to filter all charts (except for the Business results and Key results charts) for specific types of work you want to report on

Flow items are Jira Align capabilities or features with a Type field set to one of the following options:

Architectural: Work that represents improvements and refactoring of development architecture.
Business: Work that represents new value to the business.
Debt: Work that represents technical debt, such as code refactoring.
Defect: Work that represents fixes for quality problems that affect users.
Enabler: Work that represents technical requirements for providing additional value. For example, building out more architectural runway for new technology.
Non Functional: Work that represents documentation, process improvements, and other efforts that do not result in functional features or code.
Supporting: Work that represents efforts that must be taken on outside of new value delivery, such as production support and maintenance.
Risk: Work that represents security, privacy, or compliance.
Not set: Work that has not yet been classified as one of the choices above. This category does not include items with an empty Type field.

Charts on the dashboard

Quick overview

The quick overview section displays flow metric statistics about the work associated with the selected program and program increment(s).

Cycle time

Displays the average cycle time for features in the selected filters. Cycle time represents the time to market for work, and is measured from when work begins until work completes. Cycle time for a feature includes waiting (blocked) working time.

For each feature, cycle time is calculated as: (accepted date) - (in progress date)

When in progress date is null, dev complete date is used: (accepted date) - (dev complete date)
When in progress date and dev complete date are null, test complete date is used: (accepted date) - (test complete date)

Efficiency

Displays the average efficiency across features in the selected filters. Efficiency is a metric that indicates if there is waste or bottlenecks in a value stream. Efficiency is measured as a ratio of active time worked on a flow item versus the total cycle time. A feature is inactive or waiting when the Blocked field is checked.

For each feature, efficiency is calculated as: ((number of days elapsed between accepted and in progress status) - (number of days blocked)) / (number of days elapsed between accepted and in progress status)

When in progress date is null, dev complete date is used
When in progress date and dev complete date are null, test complete date is used

Throughput

Displays the count of completed features in the selected filters. Throughput represents the number of flow items delivered by the program.

Work in progress

Displays the count of features that are in progress in the current program increment. “Work in progress” represents the number of flow items that are in an active or waiting (blocked) state.

A feature is considered in progress when its State field is set to In Progress, Dev Complete, or Test Complete.

Business results

Displays the count of completed program objectives in the selected filters. “Business results” represents the number of program objectives successfully achieved during the specified program increments.

Key results

Displays the average score from key results associated with completed program objectives in the selected filters.

Flow metrics analysis

Displays four charts that explain how cycle time, efficiency, throughput, and work distribution have changed during multiple program increments.

Cycle time trend

Displays the average cycle time for features in the selected filters. The chart provides visibility into whether cycle time is increasing or decreasing over time. Increasing cycle time may be an indication of a bottleneck or inefficiency within a program.

Efficiency trend

Displays the average efficiency, a percentage ratio, over multiple program increments. A higher percentage indicates that features spend less time waiting (blocked status).

Throughput

Displays the number of completed features, by flow item type, in each of the selected program increments. The chart provides insight into if throughput is increasing, consistent, or decreasing over time. A throughput that trends lower over time indicates a potential bottleneck or issues within the program that are slowing down delivery.

Work distribution

Displays the count of features, by flow item type, in each of the selected program increments. The chart can help highlight imbalances across the types of work planned during program increments. For example, if more time is spent working on defect and debt features, less capacity and time is available to deliver business features.

Business results analysis

Objective score trend

Displays a box plot chart with the range of average key result scores (maximum, median, and minimum) from program objectives in the selected filters. The chart provides insight into the business value delivered to customers and the business. Increasing average scores can indicate that a program is delivering more value to customers.

Business results and flow item insights

Displays tables of features and program objectives that allow you to view which attributes may affect the delivery of value.

Cycle time

Displays details from the features that the cycle time average and charts on the dashboard are based on. The table provides insight into each feature’s cycle time, in progress and accepted dates, program increment assignment, and parent work item (capability or epic). The table is intended to help you pinpoint features with excessive cycle time.

Blocked features (in waiting)

Displays details from the features that were considered in waiting (blocked) during the selected program increments. The table provides insight into each feature’s days in waiting, blocked reason, in progress and accepted dates, and parent work item (capability or epic). The table is intended to help you identify potential bottlenecks in the program.

Work in progress

Displays details on the features that are in progress in the current program increment. The table is intended to provide you with detailed information on features contained in work in progress counts and charts.

Business results: program objectives

Displays details on program objectives, key result scores, and associated features. The table provides you with the connection between the value delivered and the measurement of business outcomes.

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant