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?
Wouldn’t it be nice if you could have more insight into the quality of a product, while it is developed, instead of afterwards? If you could measure the quality of your product, and take action when there is a risk that the quality would become lower than required by your customer?
Software reviews and inspections significantly improve the quality of products, and provide major savings in cost and time. Sound logical, but where is the data to prove it? I’ve made an overview of data that has been published on the business benefits of reviews.
The quality of software is often still insufficient. Pair programming is a proven technique that prevents defects from entering the code.
I have described a process and a checklist to help organizations that want to start with it, and I´m providing a report with an example in a handy booklet on RCA: Tools for Root Cause Analysis.
In november 2010 heeft het Software Engineering Institute (SEI) een nieuwe versie uitgebracht van het Capability Maturity Model Integration (CMMI): V1.3. Dit artikel geeft een overzicht van de wijzigingen, en gaat in op de waarde van deze nieuwe CMMI versie.
In two previous posting on the CMMI roadmaps for CMMI V1.3, I described how the project roadmap and the product and product integration roadmaps have been improved. This posting covers the last 2 roadmaps: process and measurements.
In a first posting on the CMMI roadmaps for CMMI V1.3, I described how the project roadmap has been improved to deliver an even better result. In this posting I’m covering the product and the product integration roadmap.
Delivering product with the right quality, on time, can be difficult. Testing decisions are crucial to reach this. Are there ways to improve your testing decision capabilities? Yes there are, and they have been used and have shown to be valuable.
It’s time for a 'next quote. This one's from Yogi Bera: “You can observe a lot by just watching”. I use this quote when I see things that are clearly happening, but go completely unnoticed by those involved, thereby missing chances to improve.
Root Cause Analysis (RCA) has been used by many to determine a fault’s first or “root” causes to improve processes. Given the current economic climate, the business case for RCA has become more more explicit then ever!
Many people think Quality Assurance (QA) is only testing. This surprises me, after working many years as Quality Manager to prevent defects and improve products.