One of the most important things in Software projects is measuring the quality of Software. Here are few metrics that we follow in our company and which plays an important role in measuring our software's quality.
Stories committed vs Stories delivered
The ability of teams to meet their commitments on schedule and with the highest standards. Failing to deliver at right time causes delays and rework.
Quality across sprints
QA doesn't have time and resources to test each and every build in sprint. So, one of the major metrics is automation within the sprint. The feature/story delivered in sprint should be automated in same sprint.
Defect Age (Bug cycle time)
It is known fact that the fixing code at one place affects other. Also, we have a famous saying that "A Stitch in-time saves nine". Fixing a bug in time saves many regression.
Defect Density
A straight forward metric to measure the defects that were introduced vs the new lines of code written. All kinds of defect metrics can be used to calculate defect rate of the product. A good defect
rate target should lead to a release-to-release reduction in the total number of defects.
Customer Satisfaction
It is a good practice to consider Customer's perspective. While fixing, there might be few defects which are not valid or major in our perspective like documentation and usability bugs. These increases customer problems.
Code Coverage
A good code coverage metrics is also a measure for the quality of the product.
Stories committed vs Stories delivered
The ability of teams to meet their commitments on schedule and with the highest standards. Failing to deliver at right time causes delays and rework.
Quality across sprints
QA doesn't have time and resources to test each and every build in sprint. So, one of the major metrics is automation within the sprint. The feature/story delivered in sprint should be automated in same sprint.
Defect Age (Bug cycle time)
It is known fact that the fixing code at one place affects other. Also, we have a famous saying that "A Stitch in-time saves nine". Fixing a bug in time saves many regression.
Defect Density
A straight forward metric to measure the defects that were introduced vs the new lines of code written. All kinds of defect metrics can be used to calculate defect rate of the product. A good defect
rate target should lead to a release-to-release reduction in the total number of defects.
Customer Satisfaction
It is a good practice to consider Customer's perspective. While fixing, there might be few defects which are not valid or major in our perspective like documentation and usability bugs. These increases customer problems.
Code Coverage
A good code coverage metrics is also a measure for the quality of the product.
No comments:
Post a Comment