A customer is a customer?
Software development teams use the word “customer” a lot. But there are different kinds of customers. Being aware which kind of customer you are talking about can help you to deliver better results to your customers.
Software development teams use the word “customer” a lot. But there are different kinds of customers. Being aware which kind of customer you are talking about can help you to deliver better results to your customers.
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.
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.