CMMI Misconceptions in the Agile the People
Many people unaccustomed agile have misconceptions concerning agile. A similar method, many of us within the agile community has misconceptions concerning CMMI. During this post if would like to focus on of those misconceptions.
The truth is that CMMI prescribes little or no. visits a high CMMI maturity lead appraiser and that they can say that CMMI is descriptive, not prescriptive.
For example, CMMI says that you simply ought to have requirements CMMI documents; however doesn't say something concerning what it would seem like. Ought to or not it's in-depth and in-detail? Ought to or not it's lightweight? The selection is yours. Will a product backlog satisfy this requirement? Sure! As long it meets the requirement of your project. You decide what's applicable for you. CMMI simply says that you simply ought to follow no matter you made the decision on.
One Method cannot Work for all Projects
A lot of individuals within the agile community have the misperception that CMMI mandates one method across all comes. This is often not true. Yes, CMMI Level three asks for a structure commonplace, however that doesn't mean one method for each project. The organization will have a multiple commonplace a process that may be applied to differing types comes. Therefore you'll be able to have an agile as a regular for sure sorts of comes, and kabana for alternative sorts of comes, and a conventional model for still alternative sorts of comes.
Furthermore, every method are often tailored for the precise project through trade pointers so every project finishes up with a definite method that's suited to the project context.
Also, the quality is predicted to ceaselessly evolve. Once you have a project that wants one thing totally different, that learning ought to return into the trade pointers so alternative comes within the organization will learn from it.
CMMI truly asks for little or no. Most agile comes generate a lot of a similar CMMI documentation that CMMI asks for. Wherever overhead comes in is throughout the appraisal method, wherever you would like to stay many indirect documentation like meeting minutes as proof for the appraisers. If you simply wish to enhance your method and don’t have a need to urge appraised, you'll be able to get obviate these documents and cut your overheads.
CMMI suggests waterfall / CMMI suggests that following plan rather than changing the plan
CMMI enables you to opt for any lifecycle model. You’ll be able to opt for an agile model if you would like to – it’s absolutely compatible with CMMI. You’re conjointly not occupied to the arrange. You’re in truth expected to vary the arrange once one thing basic changes.
CMMI Values Process over People
Valuing people may be a property of the organization culture. CMMI doesn’t tell you to not worth folks there's no conflict between CMMI and valuing folks.
