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?
Teams are more and more becoming the core of organizations. Whether project teams, agile teams or any other form of collaboration that is chosen in a company, the setting in which people collaborate is often teamwise. But establishing teams, and keeping them stable isn’t always that easy.
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.
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.
We all know how to play the Devil’s Advocate. By playing this role, we stimulate a discussion in which we challenge ideas, in order to improve it. But how do you get your ideas to start with? This is where the Angel’s Advocate comes in.
When I worked at Ericsson I used Scrum to manage Process Improvement projects, where it turned out to be a real enabler for Continuous Improvement.
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.
Business needs for process improvement projects are changing. Organizations expect faster results from their process improvement investments; they want their improvement to follow changing business needs and be more engrained in the organization.
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.