This view has KPIs that explain the health and hygiene of Product Backlog. It is recommended to the be referred by the complete Scrum team that includes the Product owner, Scrum Master, developers, QA etc.
...
| Table of Contents |
|---|
KPI Name and brief | Rationale for capturing the KPI | Tools | Definition | Configurations |
Issues without Story link | The KPI has 2 data points
| JIRA/Zephyr/XRay | # of total defects without Story link: Count of all open defects that have been raised in the last 15 months # of total non-regression test cases without story link | |
Defect Reopen rate | The widget should show
| JIRA | Defect Reopen Rate measures number of defects reopened out of the total number of defects raised. | |
Backlog Readiness | The widget shows
| JIRA | Backlog Readiness KPI compares the total size of ready Product Backlog items (PBI) against the average velocity of last five sprints to ascertain if enough backlog items are always available for the team to start development. It also calculates the average time taken for Backlog items to be ready for development *When filters are applied, the Ready backlog and average cycle time will change on the filters. Backlog Strength will become '-' | |
Refinement Rejection Rate | The widget is a line graph which shows data for last 5 months. Each month user gets to see.
| JIRA | Refinement Rejection Rate measures the percentage of stories rejected during refinement as compared to the overall stories discussed. | Workflow status needs to be added in these 3 fields under mappings
|
Product defects ageing by priority | The KPI measures the effectiveness of Defect Backlog prioritization and is useful for Product Owner, Scrum Master and the development team | JIRA | This groups all open production defects that are created in the last 15 months by standard ageing buckets - <1 Month, 1-3 Month, 3-6 Month, 6-12 Month, > 12 Month. These defects can be filtered based on 'Priority'. | |
Lead time | Lead Timeis the time from the moment when the request was made by a client and placed on a board to when all work on this item is completed and the request was delivered to the client | JIRA | It is calculated as the sum of Ideation time, Development time & Release time Ideation time (Intake to DOR): Time taken from issue creation to it being ready for Sprint Development time (DOR to DOD): Time taken from start of work on an issue to it being completed in the Sprint as per DOD Release time (DOD to Live): Time taken between story completion to it going live.
|