One major change in CMMI V1.3 is the addition of agile. Let’s take a look at this, to see how the deploying the CMMI version 1.3 delivers value for Agile organizations and how we can combine agile and CMMI in process improvement.
When I started this website back in july, I mentioned that my main reason to start blogging was to share my experiences.
The CMMI V1.3 has been released just a couple of days ago. I know that many process improvement experts are looking for information, to find out what has changed. Below a first set of links to get you started.
Version 1.3 of the Capability Maturity Model Integration (CMMI) has been released by the SEI. The main changes mentioned in the SEI News are clarifications of the high maturity process areas, alignment of the representations (staged and continous) and the addition of modern engineering practices like agile.
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!
The customer is considered more and important for software development. Software teams have to delivers products and services that solve the needs of their customers. But understanding what a customer wants isn’t always that easy.
Last month I was reading the book The Gift of Time, a collection of stories from people who have used the work of Gerald “Jerry” M. Weinberg. It gives an impression how his ideas helped them, and how it enabled them to support people, and make a difference.
There is an interesting question posted on the P-CMM blogspot, whether the principles used by the guilds to learn new skills would still work in today's society? Yes they do!
Earlier I’ve shared my definition of a proces. Methods (like Scrum, Prince2, XP, etc) help professionals to discuss the way to do things, to become more effective.
In my work as a consultant, I often deal with “processes”. The people I talk with use different definitions of what a process is. That often hampers discussions about processes, and makes it very tedious to come to agreements about how improve processes.