- Measure
- Set appropriate goal/SLA at different levels
- Global
- Team
- Developer (e.g. in one-to-one)
- If SLA broken
- Use the data to start a dialogue
- Might be some action we can take (see below)
- Reset goal/SLA
# Cycle time
```mermaid
graph LR;
A[Work requested]-- start time-->B;
B[First commit]-- fun time -->C;
C[PR issued]-- pick up time -->D;
D[PR picked up]-- review time-->E;
E[PR merged]-- release time -->F;
F[Work released];
B-- Merge time -->E;
B-- Cycle time -->F;
A-- Lead time -..->F;
```
## Time to open
Δt first commit and opening PR
Potential causes:
- Developers not having enough time to work in the first place
- Developers being unsure about requirements
- Developers struggling technically
Consider remediation:
- Track commit volume or PR size
- Discuss requirements in retrospective
- Conversation with Developer on the challenges, potential training and/or pair programming
## Time to first review
Δt opening PR and picked for review
Potential causes:
- Focus could be on individual work
- Time
- Priorities
- PR Size
- PR Distribution
Consider remediation:
- Re-prioritising reviews
- Tracking time taken for first feedback to be given
- Discuss PR size in retrospective
- Monitor/re-distribute work
## Time to approve
Δt review open
May share similar causes/remediation with [[Performance Metrics#Time to first review]]
Potential causes:
- Lack of knowledge (or siloed) means not confident enough to approve
- Team alignment
- Long review cycle (PR going back and forth between author and reviewerd)
Consider remediation:
- Knowledge sharing
## Time to deploy
Potential causes:
- Technical issues
- Missing automation
- Lack of confidence
Potential remediation:
- Monitor error rates
- Monitor build time
- Monitor build fail time
- Review deployment process
## Deploy frequency
Causes can be similar to [[Performance Metrics#Time to deploy]]
# Resources
https://linearb.io
https://codeclimate.com
# References
[Using metrics to remove bottlenecks and support your team](https://leaddev.com/productivity-eng-velocity/using-metrics-remove-bottlenecks-and-support-your-team) [archive](https://perma.cc/4GEP-DHQQ)
[Development metrics you should use (but don’t)](https://leaddev.com/reporting-metrics/development-metrics-you-should-use-dont) [archive](https://perma.cc/RY99-ETZR)