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.
In an earlier posting I highlighted the clarification of the high maturity process areas in this new CMMI version. This time I’m going into changes in the model architecture, which is about how to deploy the CMMI by “tailoring” it toward your needs.
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.
SPIder, the Dutch Software Process Improvement Network organises a session about software reliability on november 2. Three speakers will give their views on reliability, and discuss with the attendees what can be done to develop reliable software.
Looking at business results, how important do you consider the capability of your workforce? The knowledge and skills of your professionals, and their motivation and drive? My opinion is that it is of huge importance when you want to reach business goals.
A topic that has been fascinating me for a long time is how people take decisions? I have seen many problems with decisions, but there are ways to improve decisions.
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.
Looking at business results, how important do you consider your workforce? The knowledge and skills of your professionals, and their motivation and drive? My opinion is that it is of huge importance when you want to reach your business goals.