Agile Maturity Model
Our advice is to use an empirical approach, by inspecting and adapting along the way.
Why a Maturity Model
We have created this Maturity Model so you can use it as a map.
It can guide you on your journey to become more Agile. Such a map can be useful, as long as you realize that:
- It is based on reccurring patterns we have observed, but is not created to be perfect
- It does not reflect the context of your company
- It is unaware of the history you bring along
- There are many paths towards maturity, so there is not such thing as a single path
The most important remark for using this Maturity Model is to get a good guide.
Without the right leadership to guide you, any map can be wrong.
But even with the right leadership a guide can get lost in a complex environment, without a map.
The Maturity Model
The Maturity Model describes how 4 typical roles in an Agile organization typical grow more mature. While the Scrum teams gain more maturity, the role of the traditional manager gradually changes into an Agile Leader.
Each of the question marks in the model represents a few characteristics of the role at the corresponding Maturity Level.
For a more details, you can read these blogs:
Free Downloadable PDF Versions
You can download the complete Agile Maturity Model (with all question marks filled in) here: