What makes a useful maturity model




















View 2 excerpts, cites background. Highly Influential. View 6 excerpts, references background. View 14 excerpts, references background and methods. Practitioners and academics have developed numerous maturity models for many domains in order to measure competency.

These initiatives have often been influenced by the Capability Maturity Model. View 1 excerpt, references background. Capability Maturity Model for Software. Organizations increasingly recognize the need to adopt a process orientation as a means of approaching challenges such as globalization, Enterprise Systems implementations or alternative improvement … Expand. Maturity Models in IS Research.

View 9 excerpts, references background. Maturity models are popular instruments used, e. Their application … Expand. View 5 excerpts, references background. Check Google Scholar. In German libraries KVK. I need help. More details.

Extent: bytes. Saved in favorites. Similar items by subject. Similar items by person. A service of the. Sitemap Contact us Imprint Privacy. Modell Prozesskette Gestaltung. Sometimes even a crude model can help you figure out what the next step is to take, but if your needed mix of capabilities varies too much in different contexts, then this form of simplification isn't likely to be worthwhile.

A maturity model may have only a single dimension, or may have multiple dimensions. In this way you might be level 2 in 19th century cocktails but level 3 in tiki drinks. Adding dimensions makes the model more nuanced, but also makes it more complex - and much of the value of a model comes from simplification, even if it's a bit of an over-simplification. As well as using a maturity model for prioritizing learning, it can also be helpful in the investment decisions involved.

Such estimates are, of course, as crude as the model, and like any estimation you should only use it when you have a clear PurposeOfEstimation. Timing estimates can also be helpful in dealing with impatience, particularly with level changes that take many months.

The model can help structure such generalizations by being applied to past work "we've done 7 level shifts and they took months". Most people I know in the software world treat maturity models with an inherent feeling of disdain, most of which you can understand by looking at the Capability Maturity Model CMM - the best known maturity model in the software world. The disdain for the CMM sprung from two main roots. The first problem was the CMM was very much associated with a document-heavy, plan-driven culture which was very much in opposition to the agile software community.

But the more serious problem with the CMM was the corruption of its core value by certification. Software development companies realized that they could gain a competitive advantage by having themselves certified at a higher level than their competitors - this led to a whole world of often-bogus certification levels, levels that lacked a CertificationCompetenceCorrelation.



0コメント

  • 1000 / 1000