Purpose

Target Fulfillment shows a percentage of delivery cases when time spent for processing a delivery case met the target set for it.

How metric helps

Target Fulfillment helps to reveal how well a team deals with items of a high importance. If delivery targets are continuously violated a software development process in a team should be reviewed for efficiency.

Questions it answers:

• whether a team meets SLA targets
• how well a team deals with items of a high importance
• how a team handles requests
• how the team is accurate with estimations in the cases when team is required to set expectations basing on historical data
• how fast a team is identifying/removing roadblocks
• whether the team’s WIP is broken
• whether a team meets SLA targets

How metric works

Chart overview

Chart shows a percentage of delivery cases - Axis Y met the delivery target by priority/severity - Axis X. 

On hover over a column a hint appears with the following info:

• Delivery target - set in  Project Settings>Task Tracking System>On-time delivery targets;
• Average reaction/resolution time.

By click on a point a pop up appears with the following information got from a task tracking system about issues do not meet delivery targets: 

• Issue ID;
• Type;
• Priority;
• Summary.

TOP-5 problems metric identifies 

1. Testing starts late on time
2. Not ready for development backlog is taken into work
3. Unexpected blockers or dependencies during Sprint execution
4. Uncontrolled scope volatility
5. Too many dependent teams or stakeholders

Calculation

Reaction Time is a time period from the moment a case is created till the moment its initial workflow status is changed to another.

Resolution Time is a time period from the moment a case is created till the moment it gets a 'Done' status.

Data Source

Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).