If you value quality within your delivery capability then this pair of metrics should be at the heart of your core metrics.
First Time Pass Rate (FTPR) and Return Rate are completely configurable to allow you to accurately track trends over time of your team's ability to deliver first time from ticket creation through to completion. See the Configuring FTPR and Return Rate section below on how to do so.
FTPR and Return Rate can be understood and broken down by any available field against your tickets. Above we are comparing tickets in 3 different teams.
How does Plandek calculate these values?
The calculations for FTPR and Return Rate are below:
When clicking on any of the FTPR or Return Rate percentage values you will drill down to a table of ticket data relating to that percentage. The table will contain all completed tickets based on time range and filters.
Within the table you can understand if a ticket has a return or defect via the count in these columns:
Total returns/defects - sum of the next 3 columns
Return transitions - the number of times the ticket went through any of the selected return transitions
Defect issue types - the number of selected defect subtask issue type tickets raised against the ticket
Defect transitions - the number of times the above defect subtask issues type tickets went through any of the selected return transitions
Configuring FTPR and Return Rate
Although the calculations for, and therefore insights from, these two metrics are different the configuration is the same as described below:
1) Click add a metric in the top right by the date picker. Under Process, select First Time Pass Rate or Return Rate and add it to your dashboard.
2) Once it's on your dashboard, open the metric by clicking Explore, and then go over to the metric settings panel to the right of the screen (this section will already be expanded).
3) In Calculation, first add all transitions that you want to represent a return in your workflow (e.g. In Test => In Dev, Review => In Progress)
4) Next, still within Calculation, you can also add any subtask issue types that represent a defect in your workflow (e.g. In sprint bug, Defect). These do need to be a subtask of the completed ticket (i.e. Story, Task etc)
5) Click Save. You will notice that the data refreshes, and you will now see an over time line chart showing the FTPR or Return Rate percentage at each time point and an absolute average across the whole range in the top left corner.
6) You can then add any additional Breakdowns and/or Filters to refine your metric. Also, the Sprint Override option can also be used if you want to scope the metric to completed tickets within a certain sprint.
7) Finally, remember to rename as required in Metric Settings and select the Make Dashboard Chart option so that you retain your chosen view back on the dashboard.