Weekly Team Insights
The Weekly Digest is sent every week to give you a quick snapshot of key engineering metrics - no need to log into the dashboard. It compares the current week with the previous week to help you spot trends and changes.
Trend Indicators
✅ Green tick: The metric has improved compared to last week
❗ Red exclamation: The metric has declined or needs attention
Sections
1. DORA Metrics 📊
These industry-standard metrics measure the speed and stability of your delivery pipeline. Refer to Dashboard > Metrics > DORA tab for more details.
Cycle Time: The Cycle Time is the average time duration that Pull Requests spend in different stages of the pipeline, including "Coding," "Pickup," "Review," and "Merge". Calculated based on the number of PRs merged in the mentioned date range.
Deployment Frequency: the average number of Pull Requests merged in the main/master/production branch per week.
Change Failure Rate: The percentage of changes that result in failure or errors in production, indicating how often changes affect the stability or functionality of the system negatively. The value comes based on the configurations done on the dashboard.
Mean Time to Restore (MTTR): the average time taken to resolve a production failure/incident and restore normal system functionality each week. The value comes based on the configurations done on the dashboard.
2. PR Flow 🚀
Focuses on the efficiency and quality of your Pull Request (PR) process based on PRs merged during the week. Refer to Dashboard > Metrics > Quality tab for more details.
Avg. PR Size: PR Size represents the average number of lines of code added, changed, or deleted across all the merged Pull Requests (PRs). For all the merged Pull Requests, Typo calculates the lines of code added, changed, or removed from each one of them. The average of these changes in each Pull Request over the selected time period represents PR Size
PRs Merged w/o Review: Pull Request merged without review refers to all those pull requests that are merged without the review being approved. For all the merged PRs, Typo considers the ones that do not have any ‘Approved’ status associated with them.In case of merged PRs having review comments but not the approval, such Pull Requests are also considered as merged without review.
Blocked PRs: The number of PRs currently stuck in “Awaiting Merge” or “Awaiting Review” status for more than 24 hours is considered as Blocked. Refer to Dashboard > Metrics > Quality tab for more details.
Review Time: he "Review" stage represents the average time taken to complete the code review of Pull Requests. For all merged PRs, Typo calculates the average time between the first review comment on a PR and its approval. In case a Pull Request does not have a review comment, the Review Time will be calculated from the time thatthe Pull Request was raised for review. If a Pull Request is merged without review approval, the Review Time will be set to ‘0’ for all such Pull Requests.
3. Code Health 🧭
Aggregated insights into the technical debt and security posture of all repositories.Refer to Dashboard > Code health > PR scan for more details
Performance / Security / Vulnerability: Counts of specific issues found in your code that could fall under these categories based on the predefined SAST rules that occurred on the PRs created in the mentioned date range.
Code Smell: Indicators of deeper problems in the code that may increase technical debt over time.
4. Sprint Progress 📈
Tracks how your active sprints are performing against their original goals. Refer to Dashboard > Sprint >
Overall Scope Creep: It shows work added to a sprint after it starts, increasing the planned scope.
Sprint Status: Displays if the current sprint is "On-Track" or at risk, including progress percentages and tenure.
Last updated