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?
Op dinsdag 21 juni organiseert SPIder een plenaire sessie met als thema Verandermanagement: Ben jij klaar voor organizational change? Een onderwerp wat mij nauw aan het hart ligt.
Procesverbetering wordt vaak toegepast om problemen in een organisatie structureel aan te pakken en blijvend op te lossen. Ik heb succesvolle (proces)verbetertrajecten begeleid, maar ook trajecten gezien waar door de verbeteraanpak de problemen initieel juist groter werden. Door alert te zijn op de signalen, en tijdig actie te ondernemen werd het verbetertraject daarna alsnog succesvol.
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.
Het Software Engineering Institute, beheerder van dit model, wil graag horen hoe ze het People-CMM verder kunnen verbeteren. De SPIder People-CMM werkgroep gaat een aantal wijzigingen indienen, en we geven je de kans om daaraan een bijdrage te leveren!
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.
Earlier I described how you improve the performance of IT organizations in an agile way. The Agile Journal published a compact version of agile process improvement.
Some companies say that “people are our most important resource”. I’d rather use the term “professionals”, since they are trained, have build up experience and are continuously developing themselves to deliver value for your customers. Question is: Are they empowered to do this in a efficient and effective way? The People-CMM can be used to develop a powerful professional workforce, supporting self-organizing agile teams.
Root Cause Analysis (RCA) has been used for many years to determine a fault’s first or “root” causes in order to identify process improvement opportunities. The CMMI V1.3 has increased the possible deployment of RCA.
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.