Allstacks believes that all team should measure the following metrics, broken into the following themes:
Completion: Roadmap Focus, Velocity, Sprint Attainment
Efficiency: Cycle Time, Lead Time, Issue Time in State, Coding Days, PR Response Time
Quality: Currently Open Defects by Priority, Defects Created Over Time
Readiness: Refined Backlog
Note: All of these metrics can be up-leveled in visualizations for engineering directors and VPs. Please reach out to your Allstacks representative with any questions.
| Table of Contents |
|---|
Completion:
Roadmap Focus
...
Why:
Understand how much of your team’s effort is going towards roadmap work vs maintenance and tasks.
Answer the question “How long do you think this will take?” with confidence knowing how focused you’ve historically been on planned work.
...
Using the “Descendants of” selector, choose the individual sprints that your team wants to track.
Efficiency:
Cycle Time
...
Why:
Understand if your team is consistently sizing and estimating work.
...
Aggregate by median
Group monthly
Refined Backlog Ready to Work
...
Pull request response time
...
Why:
Determine the depth of refined work ready for the engineering teamOlder pull requests cause merge conflicts, and are more difficult to review after they are no longer top of mind.
Goal:
Two to three sprints work of fully refined workBetween one-half and three days.
Starting Metric:
Burndown: Remaining Issues by State (In Issue Count or Story point modes)Pull Request Response Time
Settings to Apply:
Advanced filters to match returned cards to your team’s backlog.Aggregate based on average instead of median.
Coding Days
...
Why:
Understand how frequently your team is able to commit code. Use as a proxy for development coding time availability.
Goal:
3-4 average days
Typical product/feature based dev teams.
Can be less for teams with architects, data scientists, QA, devops
Starting Metric:
Coding Days
Settings to Apply:
None Needed
Quality:
Currently Open Defects by Priority
...
Series: By priority/severity
Include Disabled Team Members filter
Filter to the relevant backlog of the team via Advanced Filters
Pull request response time
...
Readiness:
Refined Backlog Ready to Work
...
Why:
Older pull requests cause merge conflicts, and are more difficult to review after they are no longer top of mindDetermine the depth of refined work ready for the engineering team.
Goal:
Between one-half and three daysTwo to three sprints work of fully refined work.
Starting Metric:
Pull Request Response TimeBurndown: Remaining Issues by State (In Issue Count or Story point modes)
Settings to Apply:
Aggregate based on average instead of median.
Coding Days
...
Why:
Understand how frequently your team is able to commit code. Use as a proxy for development coding time availability.
Goal:
3-4 average days
Typical product/feature based dev teams.
Can be less for teams with architects, data scientists, QA, devops
Starting Metric:
Coding Days
Settings to Apply:
None NeededAdvanced filters to match returned cards to your team’s backlog.