Engineering KPI's to Track

GitHub + Coda

Your Teams PRs

QA Review

Open Issues

Bug Resolution Time: This measures the average time it takes for the team to resolve issues from the moment they're reported. This KPI can help you understand the efficiency and effectiveness of your engineering team.

Open/Closed Issues: Track the number of open vs. closed issues over time. This KPI can give you insights into the current workload and the team's ability to resolve issues.

Code Commits: The number of code commits can show the activity level of your engineering team. However, this should be used with caution as more commits do not necessarily mean more progress.

Code Review Time: This is the average time it takes for code to be reviewed by peers. Faster code review times often lead to faster development cycles.

System Downtime: Measure the time when your system is not operational. This is critical for customer satisfaction and system reliability.

Feature Completion Rate: Track the percentage of planned features that have been successfully implemented. This KPI can help measure the team's productivity and effectiveness.

Test Coverage: This measures the percentage of your code covered by automated tests, which can indicate the robustness of your testing and the likely reliability of your platform.

Velocity: This Agile KPI measures the amount of work the team can handle during a single sprint and can be useful for predicting future project timelines.

Sprint Burndown: In Agile development, this measures the amount of work remaining in a sprint day-by-day, helping to identify if the team is on track to complete their commitments.

Technical Debt: While it can be difficult to quantify, tracking an estimate of your technical debt can help inform decisions about when to focus on code quality and refactoring versus new feature development.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.