Purpose
Enable Train uses dashboards to visualise data from Jira to understand team trends.
This data is visualised per quarter (90 days, 7 iterations), and utilised in retrospectives and gemba walks.
Template examples
There are two templates: Kanban or Scrum.
- The Scrum template shows data per sprint. Examples: SNES, Sparkle
- The Kanban template shows data per day, or where able per artificial 2-week interval. Examples: Cloud-Rangers, Engine, Frameworkers, Onyx
Template categories
The dashboards follow the four metric categories defined by the Yamaha Project Management Office.
Flow
Flow metrics are about being able to continue working, and can be recognised by their light blue border.
Output
Output metrics are about our efforts to complete work and can be recognised by their dark blue border. Team Happiness should be filled each quarter in the linked survey.
Quality
Quality metrics are about the technical quality of our systems and software, and can be recognised by their purple border. Definition of Done should be stored in the linked location on Confluence.
Outcome
Outcome metrics are about business value realised and commuicated, and are not automated. You are expected to maintain these outside Jira.
The Kanban template
Flow charts
The cumulative flow diagram is linked to a Kanban Board, and shows tickets progress through the statusses shown on that board over time.
Ideally, the tiles between New and Done are thin, showing that the team is able to focus.
The steeper the chart, the better, because that would show that tickets are closed quickly.
The WIP Run Chart is linked to a Kanban or Scrum board.
Ideally, the amount of tickets in progress simultaneously is low, showing that the team is able to focus.
A rising trend line means that the team is increasing their WIP and is a warning sign for the team.
The Cycle Time Trend breaks work done up into 2-week periods, and shows the average amount of days the tickets solved in that period took.
On the right hand top the average for the entire quarter is shown.
A rising trend line means that the team is increasingly taking longer on average to solve their tickets and is a warning sign for the team.
The Kanban Velocity breaks work done up into 2-week periods, and shows the amount of items solved within each period.
On the right hand top the average solved per two weeks over the entire quarter is shown.
A dropping trend line means that the team is steadily decreasing the amount of tickets they solve over time and is a warning sign for the team.
The Backlog Readiness shows what the Definition of Ready is for open items in this team's backlog.
This is measured by counting the field "DoR" present on all YIS tickets. SD tickets will show in this graph as "None".
Ideally a team has all items in process at the stage "ready for sprint", and roughly an equal amount at "acceptance criteria defined" (ready for next period).
Output charts
Quality charts
The Scrum template
Flow charts
Output charts
Quality charts
Overview
Content Tools