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.
| | | 2. Cycle Time | Check the Process Screen to analyze whether long coding or review phases are contributing to missed deadlines. | | | 3. Rework & Maintenance | On the Coding Screen, see how much of your effort went towards code churn. | | | 4. Unplanned Completed Work | 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** | 1. Deployment Frequency | Check Cockpit to ensure you’re deploying frequently (daily or weekly). | | | 2. Change Failure Rate |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** | 1. Change Failure Rate | On the PR screen, see how many PRs were hotfix related, and see the trends on Cockpit. | | | 2. MTTR (Mean Time to Restore) |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.
| | | 3. Flashy Reviews | Review the PR Screen for any rushed, surface-level reviews. | | {% endtab %} | | | {% tab title="🕒 Key Times" %} | **Key Event** | **What to Check** | **What to do** | | -------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Daily Check-In** | 1. Open PRs | See which PRs are open for you to review and to merge on the [Pull Request screen](https://chatgpt.com/using-hivel/pull-request). | | **Weekly Check-In** | 1. [Cycle Time](https://chatgpt.com/metrics-and-definitions/speed/cycle-time) | Check the [Process Screen](https://chatgpt.com/using-hivel/process) to analyze whether long coding or review phases are contributing to missed deadlines. | | | 2. Coding Focus Time | On the [Activity Screen](https://chatgpt.com/using-hivel/activity), ensure your coding focus time is maximized. | | | 3. [Deployment Frequency](https://chatgpt.com/metrics-and-definitions/speed/deployment-frequency) | Check [Cockpit](https://chatgpt.com/c/broken-reference) 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** | 1. [Change Failure Rate](https://chatgpt.com/metrics-and-definitions/quality/change-failure-rate) | Track failures in the [PR Screen](https://chatgpt.com/using-hivel/pull-request) 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. | | | 2. [PR Review Time](https://chatgpt.com/metrics-and-definitions/speed/review-time) | On the [Pull Request Screen](https://chatgpt.com/using-hivel/pull-request), 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** | 1. Code Churn | Check the [Coding Screen](https://chatgpt.com/using-hivel/coding) to see how much time you're spending on [new work](https://chatgpt.com/metrics-and-definitions/throughput/new-work) versus [rework](https://chatgpt.com/metrics-and-definitions/quality/rework) and [maintenance](https://chatgpt.com/metrics-and-definitions/quality/maintenance).Aim to write well-tested code that minimizes rework, and advocate for regular refactoring if maintenance is high. | | | 2. [Meetings](https://chatgpt.com/using-hivel/cockpit-pro/meetings-breakdown) | On [Custom Dashboards](https://chatgpt.com/c/broken-reference), see how long you spent in meetings vs. doing deep work. | | | 3. [Throughput](https://chatgpt.com/metrics-and-definitions/throughput) | On the [Cockpit](https://chatgpt.com/c/broken-reference), analyze your trends for Commits, PRs Opened, and PRs merged. | | | 4. Overall Activity | On [Dev360](https://chatgpt.com/using-hivel/dev360), see what type of work you spent the most time on, and whether you had consistent activity trends. | | **Quarterly Review** | 1. Team Performance Alignment | Use the [Dev360](https://chatgpt.com/using-hivel/dev360) and [Cockpit](https://chatgpt.com/c/broken-reference) to compare your performance metrics ([cycle time](https://chatgpt.com/metrics-and-definitions/speed/cycle-time), [review time](https://chatgpt.com/metrics-and-definitions/speed/review-time), [rework %](https://chatgpt.com/metrics-and-definitions/quality/rework)) to team averages.Propose improvements and celebrate progress as necessary. | | | 2. Long-term trends | Review your personal trends across multiple sprints using the [Custom Dashboards](https://chatgpt.com/c/broken-reference) and [Goals Screen](https://chatgpt.com/goals). | | {% endtab %} | | | | {% endtabs %} | | |