BACKLOG Governance

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.

1 Backlog Count by Issue type
2 Backlog Count by Status
3 Defect Count by Type
4 Issues without Story link
5 Defect Reopen rate
6 Backlog Readiness
7 Refinement Rejection Rate
8 Product defects ageing by priority
9 Iteration Readiness
10 DOR Compliance
11 Epic Progress
12 Lead time
13 Time in Statuses (Cycle Time)
14 Flow Load
15 Flow Distribution

Anything that is in RED is part of the backlog

Sub tab	KPI Name and brief	Rationale for capturing the KPI	Tools	Definition	Maturity Range	Configurations
Summary	Backlog Count by Issue type		JIRA	Provides a detailed breakup of the total issue count in the backlog based on issue types. enabling effective issue management and prioritization.
Summary	Backlog Count by Status		JIRA	Provides a detailed breakup of the total issue count in the backlog based on Status. enabling effective Status management and resolution.
Summary	Defect Count by Type		JIRA	Provides a detailed breakup of the total issue count in the backlog based on Defect types. enabling effective defect management and resolution.
Backlog Health	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
Backlog Health	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 Health	Backlog Readiness	The widget shows Ready backlog in terms on issues and Story Points Backlog strength Readiness cycle time	JIRA	Ready Backlog = No. of issues which are refined in the backlog. This is identified through a status in jira/azureboards Backlog Strength = Size of issues refined in the backlog / Average velocity of last 5 sprints It is calculated in terms of no. of sprints. Recommended strength is 2 sprints Readiness cycle time - average time taken for Backlog items to be refined
Backlog Health	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
Backlog Health	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'.
Backlog Health	Iteration Readiness	Depicts the readiness of a forthcoming iteration in relation to the quality of the Refined backlog. enabling effective iteration planning and execution.	JIRA	Depicts the readiness of a forthcoming iteration in relation to the quality of the Refined backlog. enabling effective iteration planning and execution. Configuration to have fields Status to identify completed - Show on Graph as ‘Closed’ - Rare possibility but may happen Status to identify In Progress - Show on Graph as 'In Progress; - Could be because of spilled over issues Status that meet DOR - Show on Graph as ‘DOR met’ Status that do not meet DOR - Show on Graph as ‘DOR not met’
Backlog Health	DOR Compliance	explains the issues that meet DOR based on status also comply with other ready criteria like Sizing & Acceptance criteria	JIRA	DOR compliance shows 2 data points Issues Sized Issues with Acceptance Criteria (AC)
Epic View	Epic Progress	Showcases the progress of each epic in a backlog, presenting the total count and percentage completion, assisting in the monitoring, and tracking of epic progress.	JIRA
Flow KPIs	Lead time	Lead Time is 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		M1 : > 60 days, M2 : 45-60 days, M3 : 30-45 days, M4 : 10-30 days, M5 : <10 days
Flow KPIs	Time in Statuses (Cycle 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.	JIRA	Each of the KPIs are calculated in 'Days' . Lower the time, better is the speed & efficiency of that phase
Flow KPIs	Flow Load	It indicates how many items are currently in the backlog. This KPI emphasizes on limiting work in progress to enabling a fast flow of issues	JIRA
Flow KPIs	Flow Distribution	It evaluates the amount of each kind of work (issue types) which are open in the backlog over a period of time	JIRA

BACKLOG Governance

Backlog Count by Issue type

Backlog Count by Status

Defect Count by Type

Issues without Story link

Defect Reopen rate

Backlog Readiness

Refinement Rejection Rate

Product defects ageing by priority

Iteration Readiness

DOR Compliance

Epic Progress

Lead time

Time in Statuses (Cycle Time)

Flow Load

Flow Distribution