“Quality tends to fan out like waves”, noted Robert M. Pirsig. Good development processes have been proven to provide better quality products and happy workers tend to create happy customers. It’s easier to be happy in your work when there is a general consensus about how your work is evaluated.
There are a multitude of ways to measure quality and in general it is considered a difficult thing to do. Our experience in software development has shown, that a simultaneous assessment of both product and process will provide the best results. The calculations and related KPI’s do not have to be complex, but we need to understand why we are doing things the way we are doing and what are the characteristics of a product of good quality.
Based on our experience, we have created a Quality Index that is described in a recently released white paper. The Quality Index will help you track quality at any point of the software application delivery lifecycle and in production. This will allow you to:
- Forecast quality issues before they turn into blockers
- Communicate expectations to the teams clearly
- Compare the progress of different products in your portfolio
- Create a unified culture and a mutual language around quality within your organization
In any case, the ultimate measurement of quality is a happy customer (as well as your company making bigger bucks!). You can very well extend the use of this Quality Index to cover customer satisfaction or financial aspects to get an idea of how well tracking the index in-flight did impact the quality of the final product.
We would like to get your ideas about how this measurement method would work for your organization, or if you have some additional ideas that should be included in the Quality Index.
Please leave your comments below or email us at firstname.lastname@example.org to kick off the discussion!