"Cross-team DevOps effectiveness scorecard" template

This dashboard template is only available for Atlassian Data Lake connections that include Jira data and have scope of data set to “All”. Read more about how to connect to the Atlassian Data Lake.

This dashboard displays a set of key scorecards that help to highlight common problem areas across your department by using the data from your development tooling. In this dashboard, we determine a department as the teams working on projects of the same category, which is based on the “Dropdown” control labeled Project category.

Controls on the dashboard

Use the following controls to configure the dashboard:

Date range	“Calendar” control to filter charts to display data relating to work items completed during the selected date range.
Date bucket	“Dropdown” control to group data by week, month, quarter, or year.
Project category	“Dropdown” controls to specify the departments that this dashboard should focus on. If you reset this control, the charts will look at work items across all project categories.
Work types to consider	“Dropdown” control to select specific work types that you want this dashboard to consider. If you reset this control, the charts will look at work items of all types.
Work item labels to ignore	“Dropdown” control to select specific work item labels that you want this dashboard to ignore. If you reset this control, the charts will look at all work items with any label.
Work types to configure as bugs	“Dropdown” control to select specific work types that you want this dashboard to consider as bugs. If you reset this control, the charts will look at work items of all types.

Mapping categories of work

Mapping work items into categories of work helps teams keep track of and prioritize the effort spent in each category. At Atlassian, we bucket the work (in other words, Jira work items) into four categories: Run the business, Change the business, Developer productivity, and Team management.

To map the work categories:

Use the “Text input” controls to specify the names of the categories of work.
Use the “Dropdown” controls to specify the labels of Jira work items that map to each category of work.

Note the following:

If a work item maps to multiple labels, the charts will map the work item to the first label match in the list.
The first category of work (default is “Run the business”) in this mapping is also used as the target goal in some charts, as we believe teams should spend less than 10% of their time working on this category.

Mapping statuses of work in review

Specify which work item statuses indicate “In review”. This mapping ensures that the “Teams with work items spent less than 50% of time reviewing work” and “Time spent in ‘In review’ status” charts properly display the proportion of time spent on work in review.

Charts on the dashboard

Quick overview

The quick overview gives a holistic view of your engineering health over the last four weeks, helping you see where your strengths and weaknesses are. The trends beside the number indicate the movement of the metrics in last four weeks.

Median work item cycle time

The median number of days it took for work items to move from “To do” to “Done” in the last four weeks.

Work items completed

The number of work items completed in the last four weeks.

Deployment frequency

The average number of production deployments in the last four weeks.

Bugs raised

The number of bugs opened in the last four weeks.

Four quick overview metrics for cross-team engineering effectiveness

Speed of delivery

Teams with work item cycle time over or under 7 days

Work item cycle time looks at the total time a work item spends “In progress”. Assess the workflows of your teams by seeing how many teams are meeting or missing the target cycle time each month.

Supporting metrics for cycle time

Shows the median development, work item, and PR cycle times side by side for easy comparison and analysis.

A bar chart and 3 single value charts to monitor team's issue cycle time.

Cycle time per team

A listing of all projects, the number of work items worked on, and their median cycle times each month.

Table chart showing issue count and median cycle time for each Jira project.

Teams deploying at least four times a month

Deployment frequency counts the number of times a change gets deployed to production. Assess the spread of teams meeting or missing the target of at least four deployments per month.

Supporting metrics for deployment frequency breakdown

A quick overview of deployment success rate, median deployment time, and maximum deployment time to quickly isolate the outlier services.

Bar chart and 3 single value charts to monitor a team's deployment frequency.

Deployments per team

A listing of all projects and the number of deployments during the selected date interval.

Table chart showing number of deployment for each project.

Work breakdown

Development time breakdown

A breakdown view of the time spent by the teams in each development category. Use this chart to identify anomalies in the spread of time.

Pie chart showing the distribution of time a team spent on each development category.

Activity breakdown per team

A listing of all projects and their time spent in each development category.

Table chart showing time spent in each development category for each project.

Teams that spent less than 50% of time reviewing work

The number of teams that are meeting or missing the target for the amount of time spent reviewing work items. Teams that spend too much time “In review” may need to improve their review process.

Bar chart showing number of teams spending the target amount of time reviewing work.

Time spent in “In review” status

A listing of all projects, the number of work items worked on, and the percentage of time spent reviewing work items during the selected date interval.

Teams that spent less than 10% of time to run the business

The number of teams that are spending the appropriate amount of time working on “Run the business” work items.

Time spent to run the business

A listing of all projects, the number of work items categorized as “Run the business”, and how much time was spent working on these work items each month.

Table chart showing percentage of categorized issues and percent of time spent on RTB issues for each team.

Bottlenecks

Teams that have at most 10% overloaded assignees

The number of teams that have more or less than 10% of team members with more than three concurrent work items in progress.

Supporting metrics

Provide a percentage distribution of work items that needs attention — categorized as “Blocked work items”, “Handed over work items”, and “Stuck work items”.