Developer's Guide to Hivel
Last updated
Last updated
Get started with Hivel by using this guide to know exactly what metrics to check—and when to check them. Organized around key events and check-in times, this resource will guide you in monitoring the metrics that matter most, from daily cycle time reviews to quarterly performance benchmarks, making it easy to stay on track and continuously improve.
| Key Event | What to Check | What to do |
|---|---|---|
Missed Deadlines
PR Bottlenecks
Use the Pull Request Screen to check for PRs awaiting your review or merge, or PRs with 5+ days cycle time. Prioritize reviews or break down large PRs into smaller ones. You can also escalate by adding more reviewers to the process.
Check the Process Screen to analyze whether long coding or review phases are contributing to missed deadlines.
On the Coding Screen, see how much of your effort went towards code churn.
On the Delivery Accuracy screen, see how much unplanned ad-hoc work was completed in the last sprint, and how that affected your planned roadmap items.
New Feature Deployment
Check Cockpit to ensure you’re deploying frequently (daily or weekly).
Track failures in the Process Screen to see how often deployments require rollbacks or fixes. If failure rates are high or deployments are few, work on improving testing and CI/CD processes.
Critical Production Issue
On the PR screen, see how many PRs were hotfix related, and see the trends on Cockpit.
Use the PR Screen to check how quickly production issues are resolved. Work on improving your response time during production issues and ensure that reviews, even under pressure, are thorough to prevent future failures.
Review the PR Screen for any rushed, surface-level reviews.
Daily Check-In
Open PRs
See which PRs are open for you to review and to merge on the Pull Request screen.
Weekly Check-In
Check the Process Screen to analyze whether long coding or review phases are contributing to missed deadlines.
Coding Focus Time
On the Activity Screen, ensure your coding focus time is maximized.
Check Cockpit to ensure you’re deploying frequently (daily or weekly). If your cycle time is increasing or your deployment frequency is low, work on breaking tasks into smaller pieces and improving team collaboration.
Biweekly Review
Track failures in the PR Screen to see how often deployments require rollbacks or fixes. If failure rates are high or deployments are few, work on improving testing and CI/CD processes.
On the Pull Request Screen, track how long your PRs are sitting in the review stage. Improve testing and ensure clear communication during the review process if failure rates or review times are high.
Monthly Review
Code Churn
Check the Coding Screen to see how much time you're spending on new work versus rework and maintenance. Aim to write well-tested code that minimizes rework, and advocate for regular refactoring if maintenance is high.
On Custom Dashboards, see how long you spent in meetings vs. doing deep work.
On the Cockpit analyse your trends for Commits, PRs Opened, and PRs merged.
Overall Activity
On Dev360, see what type of work you spent the most time on, and whether you had consistent activity trends.
Quarterly Review
Team Performance Alignment
Use the Dev360 and Cockpit to compare your performance metrics (cycle time, review time, rework %) to team averages.
Propose improvements and celebrate progress as necessary.
Long-term trends
Review your personal trends across multiple sprints using the Custom Dashboards and Goals Screen.