Get started with Atlassian Analytics
Learn how to add Atlassian Analytics to a site and understand what you need to query data and create charts.
"Cross-team effectiveness scorecard" dashboard template
This dashboard displays a set of key scorecards that help to highlight common problem areas across your department. 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:
Current date interval | “Calendar” control to filter charts to display data relating to issues 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 issues across all project categories. |
Issue types to consider | “Dropdown” control to select specific issue types that you want this dashboard to consider. If you reset this control, the charts will look at issues of all types. |
Issue labels to ignore | “Dropdown” control to select specific issue types that you want this dashboard to ignore. If you reset this control, the charts will look at all issues with any label. |
Mapping categories of work
Mapping issues 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 issues) 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 Jira issue labels that map to each category of work
Note the following:
If an issue maps to multiple labels, the charts will map the issue 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 issue statuses indicate “In review”. This mapping ensures that the “Teams with issues spent <50% of time in ‘In review’ status” and “Time spent in ‘In review’ status” charts properly display the proportion of time spent on work in review.
Charts on the dashboard
Drilldowns are set up for the bar charts on this dashboard. When you select a bar segment, the corresponding table chart (in other words, the table chart directly to the right) will update to show data relevant to the selected bar segment. Learn more about using charts as controls to set up drilldowns.
Teams with cycle time <7 days
Issue cycle time looks at the total time an issue spends “In progress”. Assess the workflows of your teams by seeing how many teams are meeting or missing the target cycle time each month.
“Insufficient data” means there isn’t enough information to determine whether they met or missed the target. For example, the teams may not have had enough issues assigned to them.
Cycle time per team
A listing of all projects, the number of issues worked on, and their median cycle times each month.
Teams with issues spent <50% of time in “In review” status
The number of teams that are meeting or missing the target for the amount of time spent reviewing issues. Teams that spend too much time “In review” may need to improve their review process.
Time spent in “In review” status
A listing of all projects, the number of issues worked on, and the percentage of time spent reviewing issues each month.
Team has at most 10% overloaded assignees
The number of teams that have more or less than 10% of team members with more than three concurrent issues in progress.
Work in progress per team
A listing of all projects and the percentage of overloaded assignees each month.
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” issues.
Time spent to run the business
A listing of all projects, the number of issues categorized as “Run the business”, and how much time was spent working on this issues each month.
Teams that categorized more than 90% of their work items
Teams should try to categorize their work items to help determine how much of each type of work is assigned to them.
Team with categorized work items
A listing of all the project teams, how many categorized issues they have, and the percentage those categorized issues contribute to the total issues assigned to the team each month.
Link scorecard dashboards together by using drilldowns
You can set up drilldowns to link a table chart in the Cross-team VSM scorecards dashboard to the Team VSM scorecards dashboard. By doing so, dashboard viewers can select a row in a table chart in the “Cross-team VSM scorecards” dashboard to see the “Team VSM scorecards” dashboard with data relevant to the selected team and time period.
To set up drilldowns for the table charts in this dashboard:
You must have permission to edit or manage the dashboard to set up drilldowns.
Make sure you’ve created both the Cross-team effectiveness scorecard dashboard and the Team effectiveness scorecard dashboard.
Hover over the table chart then select More actions () > Edit settings.
Go to the Drilldown tab of the chart settings.
For the Linked dashboard, select your Team effectiveness scorecard dashboard.
Under Drilldown variables, make sure to pass:
Period to the {CALENDAR} dashboard variable
Project ID to the {PROJECT_ID} dashboard variable
Select Save.
Was this helpful?
Still need help?
The Atlassian Community is here for you.