Most of us have this question that why is it that one process or procedure can’t be implemented in all the projects with similar flavor! Why is that you’ll talk new, tailored processes for every project?
CMMI, is smart enough to recognize that one size does NOT fit all. Organizations which are tempted into the “one true process” quickly realize that actually “one size fits no one”. Even if the you create “one true process” by carefully looking at projects in progress at the time, no two projects can ever be the same and hence no Single process really fit new projects as they come along.
In fact CMMi is smart enough to make sure and embodies ideas to stop organizations falling into the “one true process” trap.
This is how we have been doing this at Tekriti. We first as part one of this entire exercise are trying to build a “set of standard processes” – enough processes to support the different types of projects that the organization has to deliver. We can think of these types of projects as forming families – for each distinct family there is a distinct standard process.
Then since CMMi allows us, we will go further and tailor the selected processes to better fit the needs of each specific project. Tailoring can only occur within permitted guidelines – to ensure that the performance of different projects remains comparable. In particular, the quality of the work products produced will be comparable across projects.
CMMi is so very beautiful in terms of giving us further allowance for very unusual projects. Recognizing that every organizations evolve continuously and will have to tackle new and unique challenges, projects are permitted to seek exceptions to the standard processes and tailoring guidelines. But there is a condition, your project has to have a reasonable case for its exceptional behavior and describes how it will perform its work to ensure that the organization’s policies will not be violated.
If your organization is attempting “one true process” well, then from CMMi side you’re not fulfilling its requirements – they cannot achieve maturity level 3.
The “one true process” becomes a straight jacket that is almost impossible to change.
Now you may ask question that isn’t it easier to change one process than to keep several processes current? For to be kept up to date, that’s certainly true. But consider the problems from the other side. Different projects have different needs and it is though always good to have one process which fits all, BUT the problem comes when these projects requires contradictory changes – one project needs more agility, the other more formality…
Now, which changes are we going to incorporate into the process? If we incorporate more formality, the agile project is disadvantaged. If we go for more agility, the formal project is disadvantaged.
And then, very quickly the strains on the process and the demands to change the process become so great, the “one true process” becomes an unsustainable position. Then comes the problem, which you never have solution for!
So One size NEVER fits all! And this is something you’ll will learn as and when we will come and talk to you all, and make you understand about the processes…and make you realize that your project needs are different from someone else’s, and hence a different process!
- CMMi – A crash course – Introduction to Dev 1.3 (seeingfuture.wordpress.com)
- CMMi – Maturity Levels – Initial – Managed – Defined (seeingfuture.wordpress.com)
- CMMi Process areas and mapping with Maturity levels (seeingfuture.wordpress.com)
- CMMi – Capability Model (seeingfuture.wordpress.com)