This second posting on "What Drives Quality" investigates factors that drive the quality of requirements. Understanding what drives quality enables you to take action before problems actually occur, thus saving time and money.
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?
Communication is an important factor in improvement programs. Communication using visual management pictures the goals and approach. It motivates people to commit to change, by showing expected benefits and early results. But wrong or too much communication can also frustrate people, getting them to resist changing.
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.
Veel IT organisaties zijn in verandering. Daarbij verandert vaak de manier waarop de werkzaamheden ingericht zijn, en de aansturing en rapportage. Voorbeelden daarvan zijn "Het Nieuwe Werken", Scrum en Agile werkwijzen, tijdelijke samenwerkingsvormen zoals teams en steeds korter durende projecten. In hoeverre zijn de "traditionele" kwaliteitsmethodieken, gebaseerd op ISO, INK, TQM en CMMI nog steeds bruikbaar?
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 october 2010, version 1.3 of the Capability Maturity Model Integration (CMMI) has been released by the Software Engineering Institute. I’ve published several articles on the benefits of CMMI V1.3. This is (for now) the last article, which sums it all up.
There are 3 CMMI V1.3 models released: CMMI for Acquisition (ACQ), CMMI for Services (SVC), and CMMI for Development (DEV). The CMMI V1.3 makes it easier to combine process areas from different models, thus supporting continuous improvement that delivers quicker business results.
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.
CMMI Roadmaps are a goal-driven approach to selecting and deploying relevant process areas from the CMMI. Their aim is to deploy the CMMI effective, and quickly get business result. Let’s see how the CMMI Roadmaps can be used with the CMMI V1.3.