> For the complete documentation index, see [llms.txt](https://innowayit-1.gitbook.io/framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://innowayit-1.gitbook.io/framework/discovery/maturity-assessment.md).

# 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.

<table><thead><tr><th width="175">Maturity Level</th><th>People and Organization Dimension</th><th>Process Dimension</th><th>Technology Dimension</th></tr></thead><tbody><tr><td><strong>Level 1- Low (Ad-hoc)</strong></td><td>Reliance on undocumented  knowledge of a small team that cannot be replaced easily. Value of capability not fully understood.</td><td>Little Process Documentation, driven reactively, execution dependent on knowledge of small team,  lack of metrics, "basic operations" mode</td><td>Basic technology which does not meet business needs, standalone, not integrated, not scalable, unsupported lack of business rules, e.g., MS Office based tools</td></tr><tr><td><strong>Level 2 - Medium (Repeatable)</strong></td><td>Reliance on documented  knowledge of a small team that cannot be replaced easily.  Value of capability appreciated but not well documented.</td><td>Some process discipline, partially documented and controlled, some metrics</td><td>Basic technology  meet business needs, standalone, not integrated, scalability difficult, some business rules, but still reliance on  MS Office based tools</td></tr><tr><td><strong>Level 3 - Medium-High (Defined/Managed)</strong></td><td>Reliance on cross-trained staff, knowledge documented and repeatable. Team understands the value of their contribution towards organization objectives.</td><td>Most processes defined and documented, controlled, KPIs built into process, regularly reviewed</td><td>Robust technology in place, supported, not fully integrated, scalability possible, moderate level of business rules with minimum reliance on MS Office</td></tr><tr><td><strong>Level 4 - High (Optimized)</strong></td><td>Reliance on trained experts, strong  "expertise", team cognizant of its maturity level and continuous improvement model</td><td>Processes are documented, maintained, standardized, reviewed. Are fully controlled, repeatable, predictable, provide full visibility. Metrics monitored. </td><td>Robust, real-time, integrated, supported, scalability not an issue</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://innowayit-1.gitbook.io/framework/discovery/maturity-assessment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.