Impact — It is a way to measure the ‘bigness’ of code changes that are happening, in a way that goes beyond simplistic measurements like lines of code.
Throughput — Total amount of code of new, churn, help others and refactored code.
Productive Throughput — The proportion of code without churn.
Efficiency — Is the percentage of an engineer’s contributed code that’s productive, which generally involves balancing coding output against the code’s longevity. Efficiency is independent of the amount of code written.The higher the efficiency rate, the longer that code is providing business value. A high churn rate reduces it.
Technical Debt— Is the amount of refactoring code done by the developer.
Commits — The amount of commits done by the developer.
Days Active — The amount of days the the developer check in code.
Work Type — The highest types of work an engineer is focused on.
How do you calculate Risk?
Risk is a measure of how likely it is a particular commit will cause problems. Think of this as a pattern-matching engine, where Waydev is looking for anomalies that might cause problems.
Here are some of the questions we ask when looking at risk:
How big is this commit? Are the changes tightly grouped or spread throughout the code-base? How serious are the edits being made — are they trivial edits or deeper, more severe changes to existing code?
Risk helps teams put their attention where it’s most needed. This not only helps with quality control, but serves an incredible tool for building engineering talent: by concentrating review on outlier commits, engineers receive high-quality feedback and suggestions for improvement where it’s needed most.