Here are some key Speed metrics you can track on Hivel's Cockpit screen.
- Formula = (Total number of PRs merged to master or main in that selected time period)/(Total number of days in the time period)
- Deployment frequency measures how often code is released. Elite Deployment Frequency represents a stable and healthy continuous delivery pipeline.
- This critical DORA metric would help you understand the number of PRs being pushed to production in a given time. This can work independently of your sprint cycle time. You can learn more about them here.
- Too low Deployment frequency indicates that there may be inefficient DevOps processes, bottlenecks in review, or requirements, and teams are delivering features at a slower pace.
- High deployment frequency shows that your team can quickly provide value and react to feedback or changes.
- Cycle time is the time it takes from the first commit to PR merged.
- If things are taking too long to release, it can impact the competitiveness of the product in the market, and customers may be waiting too long for requests.
- With the very smooth delivery system in place, things are moving rapidly. At this pace, even if we see production issues, things can be fixed faster, which is great for teams experimenting with new ideas.
- Merge time is the duration between when a pull request is opened and when it is merged.
- Faster merge (lower number) times represent efficient release processes.
- Longer merge time could be due to inefficient CI/CD processes.
- Review Time is the time it takes a PR to be reviewed since it's Open.
- Low Review Time represents highly collaborative team dynamics, with reviewers moving things faster and delivering higher-quality features to customers.
- High review time represents limited reviewers in the team, and every occupied senior engineer not finding time to do code reviews slows down the cycle times.
- Coding Time is the time it takes from the first commit until a PR is open.
- Short Coding Time represents less context switching by developers, small PR size and clear requirements, and great architecture.
- Longer coding time relates to committing large chunks of code, which could lead to a higher blast radius on production issues, longer review cycles, or sometimes even misses the review process due to fatigue.