Eindelijk is het dan zover. Na allerlei onderzoeken en rapporten, lobbyen, en vele vergaderingen is er een beslissing genomen dat we gaan veranderen. Er is steun en draagvlak in de organisatie voor de verandering, er is budget en er zijn mensen vrijgemaakt voor een veranderproject. Goed nieuws! Maar hoe pak je dat nu aan?
"Verandering is de enige constante." "Onze organisatie verandert continu, maar lost dat alle problemen op?" "Er lopen zoveel veranderingen, ik mis het overzicht!" Herken je deze uitspraken? Dan weet je vast hoe belangrijk verandering binnen de organisatie is, maar ook hoe moeilijk het is om veranderingen te managen.
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.
The book "Adrenaline Junkies and Template Zombies, Understanding Patterns of project behavior" contains 86 patterns, written in an easy readable and recognizable style which make you think about how people behave in projects.
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!
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.