Scope Readiness for Development in Active Sprints
- Anastasia Baranouskaya
- Denis Olevanov (Unlicensed)
- Natallia_Mendzel@epam.com
Purpose
Scope Readiness for Development in Active Sprints shows a percentage of ready for development items at a sprint start date/time.
How metric helps
Scope Readiness for Development in Active Sprints helps to identify what items are not ready for development at a sprint start.
How metric works
Chart overview
Chart shows a a percentage of ready for development items at a sprint start date/time - number in the center. Target value is above the chart.
Drill down shows the list of not ready items at a sprint start.
Calculation
Scope Readiness for Development in Active Sprints = Ready/To do*100,
where
Ready - is a number of issues in an active sprint at its start date/time satisfying the criteria defined in Project Settings>Data sources>Task Tracking System>Scope management>Definition of Ready;
To do - is a number of issues in an active sprint at its start date/time satisfying the criteria defined in Project Settings>Data sources>Task Tracking System>Workflows>To do bucket and their issue/work item type are specified in Project Settings>Data sources>Task Tracking System>Scope management>Definition of Ready.
RAG thresholds: Green - metric value >= 95 %, Red - metric value < 95 %.
Assumptions
1 Calculation considers the latest active sprint. If there are several active sprints, metric sum ups values for all sprints. Assignment to a sprint matters.
2 Drill down shows the items that do not meet criteria at a sprint start: Project Settings>Data sources>Task Tracking System>Scope management>Definition of Ready.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).