ThoughtWorks Agile Maturity Model

The ThoughtWorks Agile Maturity Model applied to building and releasing software. Five maturity levels for five categories.
Read more
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.

Similar posters

AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...
STEEPLED
STEEPLED STEEPLED - Social, Technological, Economical, Environmental, Political, Legal, Ethical and additional compared to STEEPLE is Demographic.
BLUF - Bottom Line Up Front
BLUF - Bottom Line Up Front BLUF is a framework for declaring the purpose of the message and the action required. It should provide the most important information.
Transactional Analysis
Transactional Analysis Transactional Analysis is a psychoanalytic theory and method of therapy. A personality is made up of three ego states: Parent, Adult, Child.
Conflict styles
Conflict styles There are different strategies for managing conflicts. Categorizing conflict styles enable learning and appropriate usage of these styles
WRAP Decision-Making
WRAP Decision-Making The WRAP model for decision-making helps us to be aware of and avoid decision-making biases like Outcome, Cognitive & Confirmation Bias.
MVP Types
MVP Types Minimum Viable Product (MVP) is a simple product with only a minimal set of features to enable testing with real users. That can be achieved using various types of MVPs.
Lean Startup
Lean Startup The Lean Startup is an approach for creating and sustaining a successful startup. Short business-hypothesis-driven development cycles.
SCARF
SCARF SCARF Model represents five areas influencing human behavior. The human brain wants to minimize danger or maximize reward which activate respective responses. It explains and helps to deal with human reactions, motivations, and interactions. Description Reward state activators Threat state activators Status Relative importance to others, personal worth Positive and mutual feedback, public acknowledgment Critique,...
Westrum Organizational Culture
Westrum Organizational Culture Westrum Organizational Culture The organizational culture predicts the information flow in an organization. Good information answers the questions that need to be answered in a timely manner and the receiver can effectively use it. Good information flow is critical to be safe and effective in high-tempo and high-consequence environments. Culture Pathological Bureaucratic Generative Description Fear...