How to measure and set standards of performance and quality in Agile scrum team?

If you are already practicing agile, you might realised that the standard agile reports like burn-down, velocity are not enough to measure and set standards to actual team performance and quality.

Today We are going to talk about top 5 Engineering metrics and standards which will give you more visibility and maintainability on team performance.

# 1 :
Completion Rate : Completion rate is another form of velocity, where we track the percentage of completed story points against committed story points. This will help to measure the team’s commitment to deliver what they agreed. Keep the completion rate above 95% is Green (Excellent), above 85% is Amber (Good) and below is Red (Poor).

# 2 :
Sprint Bug Rate : Number of bugs produced by a story is giving you the density of bugs. Increased rate of bugs will add more risks on Completion Rate. This will help to measure the developer’s quality of development. Keep the Bug Rate below 1 is Green (Excellent), above 3 is Amber (Good) and above is Red (Poor).

# 3 :
Rework Rate : The story points get spilled over for next sprint is measured as rework. This will impact on project delivery. Keep the Rework Rate below 5% is Green (Excellent), below 10% is Amber (Good) and above is Red (Poor).

# 4 :
Bug Leakage : This is measured by number of bugs identified after the QA cycle at UAT or Staging or Production. This directly impacts the business and customer satisfaction. Keep the Bug Leakage below 3% is Green (Excellent), above 5% is Amber (Good) and above is Red (Poor).

# 5 :
Code Quality : This is similar as sonar code quality gate, where few metrics measured together to pass such as Code coverage, Code duplication, Security leakages, Code maintainability, etc. Keep all passed without issues is Green (Excellent), Failed with minor issues is Amber (Good) and Others are Red (Poor). This can be easily monitored by integrating Sonar cloud.