Backlog Dashboard

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.

Backlog Dashboard

Issues without Story link

Defect Reopen rate

Backlog Readiness

Refinement Rejection Rate

Product defects ageing by priority

KPI Name and brief	Rationale for capturing the KPI	Tools	Definition	Configurations
Issues without Story link	The KPI has 2 data points Defect count without story link - Tagging defects to stories is a good practice as it helps in requirement traceability and enables the team to optimize regression testing effort for every release Test cases without story link - Tagging test cases to stories empowers the team to track the coverage of execution cycle (both manual and automation)	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 Reopened /Total Reopen Rate Avg. Time to Reopen	JIRA	Defect Reopen Rate measures number of defects reopened out of the total number of defects raised.
Backlog Readiness	The widget shows Ready backlog in terms on issues and Story Points Backlog strength Readiness cycle time	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. Total stories Accepted stories Rejected stories	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 Ready for refinement status Accepted in refinement status Rejected in refinement status
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'.