Agile en Kwaliteit
Agile en Kwaliteit, twee van mijn favoriete onderwerpen gecombineerd in 1 event: Een open space op 11 juli, georganiseerd door Agile Overheid. Ik ben erbij!
Voorkomen van software fouten is beter dan genezen!
Het spreekwoord "voorkomen is beter dan genezen" geld ook voor software. Veel software fouten zijn niet nodig; veel problemen kunnen voorkomen worden. Een techniek die helpt om te leren van fouten, en ze te voorkomen, is Root Cause Analysis.
What Drives Quality: Requirements
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.
What Drives Quality?
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?
Measuring and Controlling Product Quality
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?
Business benefits of reviews
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.
Improving Code Quality with Pair Programming
The quality of software is often still insufficient. Pair programming is a proven technique that prevents defects from entering the code.
Root Cause Analysis: Practical Tools
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.
CMMI V1.3, wat brengt het?
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.
CMMI V1.3: The CMMI Process and Measurement roadmaps
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 V1.3: The CMMI Product and Product Integration roadmaps
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.
Doctor, what’s wrong with my software?
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.