Maturity Assessment
A team with a process and an application is better than only an application -- anonymous
A capability is considered mature when we balance people, process, and technology. Each of these resources alone cannot make a significant difference. The following tables provide a four-level maturity assessment.
Level 1- Low (Ad-hoc)
Reliance on undocumented knowledge of a small team that cannot be replaced easily. Value of capability not fully understood.
Little Process Documentation, driven reactively, execution dependent on knowledge of small team, lack of metrics, "basic operations" mode
Basic technology which does not meet business needs, standalone, not integrated, not scalable, unsupported lack of business rules, e.g., MS Office based tools
Level 2 - Medium (Repeatable)
Reliance on documented knowledge of a small team that cannot be replaced easily. Value of capability appreciated but not well documented.
Some process discipline, partially documented and controlled, some metrics
Basic technology meet business needs, standalone, not integrated, scalability difficult, some business rules, but still reliance on MS Office based tools
Level 3 - Medium-High (Defined/Managed)
Reliance on cross-trained staff, knowledge documented and repeatable. Team understands the value of their contribution towards organization objectives.
Most processes defined and documented, controlled, KPIs built into process, regularly reviewed
Robust technology in place, supported, not fully integrated, scalability possible, moderate level of business rules with minimum reliance on MS Office
Level 4 - High (Optimized)
Reliance on trained experts, strong "expertise", team cognizant of its maturity level and continuous improvement model
Processes are documented, maintained, standardized, reviewed. Are fully controlled, repeatable, predictable, provide full visibility. Metrics monitored.
Robust, real-time, integrated, supported, scalability not an issue
Last updated
Was this helpful?