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.
More and more organizations are adopting Agile ways of working. The descriptions of Agile methodologies give much guidance on how to manage on a team level. But there is limited information on changes needed at higher level in the organizations.
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.
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.
SPIder, The Dutch Software Process Improvement network organizes a conference on the 7th of december, on "Bigger products with smaller teams". If you manage software development, or work in process or quality improvement, this is the event for you!
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.