ThoughtWorks Agile Maturity Model

Agile Engineering

ThoughtWorks Agile Maturity Model

The ThoughtWorks Agile Maturity Model applied to building and releasing software. Five maturity levels for five categories.

Read more

Get PDF

Tags

Agile agile maturity assessment model Agile maturity model agile maturity model assessment agile maturity model thoughtworks agility maturity model DevOps devops business agility maturity model image Infographic Poster Scrum

Article

ThoughtWorks Agile Maturity Model

Level / Practice	Build management and continuous integration	Environments and deployment	Release management and compliance	Testing	Data management
Level 3 – Optimizing: Focus on process improvement	Regular meetings to discuss integration issues addressed by automation, faster feedback, and visibility.	Environments are effectively managed. Provisioning fully automated. Virtualization use if applicable.	Operations and development teams regularly collaborate to manage risk and reduce cycle times.	Rare production rollbacks. Defects are found and fixed immediately.	Release to release feedback of database performance and deployment process.
Level 2 – Quantitatively managed: Process measured and controlled	Build metrics are collected, visible, and acted on. Builds are not left broken.	Orchestrated deployment managed. Versions and rollback process are tested.	Environment and applications health monitored and proactively managed. Monitored cycle time.	Quality metrics and trends tracked. Non-functional requirements are defined and measured.	Database upgrades and rollbacks tested with each deployment. Database performance is monitored and optimized.
Level 1 – Consistent: Automated processes applied across the whole application lifecycle	Automatic build and test cycle every time a change is committed. Dependencies are managed. Re-use of scripts and tools.	Fully automated push-button deployment process. The same deployment process to all environments.	Change management and approval process defined and applied. Regulator and compliance conditions met.	Automated unit and acceptance tests. Testing is part of the development process.	Database changes are made automatically as part of the deployment process.
Level 0 – Repeatable: Process documented and partly automated	Regular automatic build and testing. Any build can be recreated from version control using an automated process.	Automated deployment for some environments. Creating new environments is inexpensive. All configurations are versioned.	Painful and infrequent, but reliable releases. Limited traceability from requirements to release.	Automated tests are written as part of the story development.	Changes in the database are made by automated scripts, versioned with the application.
Level -1 – Regressive: Processes unrepeatable. poorly controlled, and reactive	Manual processes for building software. No management of artifacts and reports.	Manual process for software deployment. Environment-specific binaries. Environments provisioned manually.	Infrequent and unreliable releases.	Manual testing after development.	Data migration unversioned and performed manually.

Resources

thoughtworks.com

Similar posters

RACE Prompt Framework

RACE Prompt Framework The RACE prompt framework is a structured approach for AI prompting that guides users through four essential steps: Role (defining who the AI should be), Action (specifying the task), Context (providing background), and Execute (setting clear expectations for delivery). This systematic method helps users craft more effective prompts by ensuring all crucial elements are included...

Eisenhower Matrix

Eisenhower Matrix The Eisenhower Matrix, also known as the Urgent-Important Matrix, is a tool for organizing tasks by their urgency and importance to improve productivity and decision-making. It divides tasks into four quadrants based on these criteria. Do Important and Urgent Tasks in this quadrant require immediate attention and are essential to your goals. These are often...

Maker's vs Manager's schedule

Maker's vs Manager's schedule The differences between a maker’s and a manager’s schedules stem from their respective workflows’ distinct nature. Makers rely on uninterrupted time blocks to tackle complex, creative problems requiring deep focus and sustained attention. Managers need flexibility to oversee multiple responsibilities, make decisions, and collaborate effectively across teams. As such, it is essential to thoughtfully assess...

Mission Statement

Mission Statement Long-term organization purpose, values and objectives. It should describe why it matters. This way it contributes to identity creation.

Value Stream Mapping

Value Stream Mapping The Value Stream Mapping is a Lean technique for managing flow and improving processes allowing to track the flow through a process.

Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively

Spotify Health Check

Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.

Maslow's Hierarchy Of Needs

Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.

RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.

CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.