Many methods for product quality improvement start by investigating the problems, and then working their way back to the point where the problem started. For instance audits and Root Cause Analysis work this way. But what if you could prevent problems from happening, by building an understanding what drives quality, thus enabling to take action before problems actually occur?
Detailed posts are available for “What Drives Quality”:
- Architecture and Design
- Reviews and Inspection
- Project Management
- Senior Management
- Operational Management
As an affiliate of the Software Engineering Institute (SEI) I investigated factors that influence the quality of software products. My aim was not to come up with a generalized set of quality factors, instead I focused on those factors that were considered important for the client that I was working with at that time. So the quality model that I developed was never intended to be generally applicable, though my expectations is that many of the factors in the model that drive quality could also be important for your organization (therefore I’m sharing it with you 🙂 ). The model contains both technical phases (e.g., requirements, design, coding, review and inspection, and testing) and management activities (e.g. senior management, operational management and project management).
The quality model was validated by reviews with people from the client organization, and with international experts in the area of quality. Finally, with the use of Bayesian Belief Network I have developed an approach to define business cases for quality improvement. This metric based quality improvement approach is usable for both high maturity organizations that already have data, but also for lower maturity organization that are starting to deploy measurements and want to make sure that their quality improvements are driven by business value.
There’s my book on what drives quality which helps you to prevent software problems from happening by building an shared understanding what drives software quality. It enables you to effectively take actions, saving time and money!
In future postings I will be covering all of the areas from the quality model. A first posting will be on the factors that drive requirements quality. It will for instance cover quality factors like “requirements commitment”, and “scope stability”. Stay tuned!
What Drives Quality: The Book
The book What Drives Quality helps you to prevent software problems from happening by building a shared understanding what drives software quality. It enables you to effectively take actions, saving time and money! This blog has been included this book.
(updated on Feb 15 2017: All detailed posts on what drives quality have been linked into this article)