➕Hivel Quadrant
With Hivel Quadrant you get an instant overview of team or user performance in relation to the entire organization. It uses three key metrics—Cycle Time (Speed), Hotfix PRs (Quality), and Deployment Frequency (Throughput)—to visualize where each team or user stands.
Metrics used in Quadrant
Cycle Time (Speed): Measures how quickly work items move from start to completion.
Hotfix PRs (Quality): Tracks the number of hotfix pull requests, indicating the quality of code and the need for urgent fixes.
Deployment Frequency (Throughput): Measures how often code is deployed to production, reflecting the overall productivity and efficiency of the team or user.
Quadrant Regions
1. Needs Improvement
Teams or users in this region are below the org average in both selected metrics. This indicates a opportunity for growth and improvement in both areas.
Example: A team with high cycle times and frequent hotfix PRs falls into this category.
2. Improve (Any of Speed/Hotfix PRs/Deployment Frequency)
Teams or users in these regions need improvement in only one of the metrics, where they lag behind the org average.
Example: A team might be shipping faster (less Cycle Time) but have many hotfix PRs, indicating a need to improve code quality.
3. Ideal State
Teams or users in this region excel in both metrics compared to the org average. They represent high performance in both speed and quality, serving as benchmarks for others.
Example: A user with a low cycle time and few hotfix PRs, along with high deployment frequency, exemplifies this ideal state.
Last updated
