Draft:Test Maturity Model integration
 | Review waiting, please be patient.
This may take 2–3 weeks or more, since drafts are reviewed in no specific order. There are 695 pending submissions waiting for review.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Reviewer tools
|
| Submission declined on 9 July 2025 by Kovcszaln6 (talk). This submission reads more like an essay than an encyclopedia article. Submissions should summarise information in secondary, reliable sources and not contain opinions or original research. Please write about the topic from a neutral point of view in an encyclopedic manner.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
This draft has been resubmitted and is currently awaiting re-review. |  |
Comment: Please take a look at how other Wikipedia articles are written. Kovcszaln6 (talk) 15:12, 9 July 2025 (UTC)
Test Maturity Model integration (TMMi)
Test Maturity Model integration (TMMi) [1]is a structured framework designed to help organizations evaluate and improve the maturity of their software testing processes. Developed and maintained by the TMMi Foundation, it provides comprehensive guidance, best practices, and assessment criteria focused exclusively on testing activities. TMMi defines five maturity levels (1 to 5): Initial, Managed, Defined, Measured and Optimization. TMMi addresses all test levels, from static to dynamic, including component, integration, system, and acceptance tests. It covers the four key areas of structured testing: lifecycle, techniques, infrastructure and organization.
TMMi is designed to complement the broader Capability Maturity Model Integration (CMMI), offering dedicated support for software testing in a range of software development environments, including traditional, Agile, and DevOps. The framework adheres to current testing standards and incorporates terminology established by the International Software Testing Qualifications Board (ISTQB).
First released in 2010, the TMMi model is currently available as TMMi 1.3, which is compatible with the terminology of CMMI V2.
TMMi is a registered trademark[2] of TMMi Foundation Limited.
Overview
The TMMi (Test Maturity Model integration) framework is organized into five distinct maturity levels, each representing a stage in the progression of organizational test process capability. Each maturity level is associated with a set of process areas that organizations should address to achieve higher testing process maturity. The progression through these levels provides a structured path for continuous test process improvement.
Organizations may adopt TMMi by participating in training programs, such as the TMMi Professional certification, and by conducting assessments[3] to identify areas of strength and opportunities for improvement. The global adoption of the model across various industries demonstrates its impact on software quality and operational efficiency See [4] [5].
The TMMi Foundation manages the ongoing development of the framework and provides resources to facilitate its implementation[6][7]. By adhering to the TMMi model, organizations can systematically enhance their testing processes, resulting in improved software quality and more efficient development practices.
Background and History
Beginning in 2005, a collective of software testing professionals and organizations initiated the TMMi Foundation. The foundation was officially launched at the ICSTest-UK conference in 2005, during which a dedicated track focused on the original Test Maturity Model (TMM).
The TMMi model was first released in 2010. Currently (July 2025) available version is TMMi v1.3.
TMMi is intended as an objective, business-oriented model that recognizes testing as an integral component of software development. The framework is designed to introduce a systematic, staged approach for improving testing practices, offering detailed guidance on test processes, techniques, and management.
The TMMi model is freely available for download and use, serving as a public reference for organizations seeking to improve their software testing practices.
TMMi has since been translated into multiple languages and is utilized globally[4][5].
Topics
Key Components of TMMi
The model is composed of required, expected, and informative elements that guide organizations in assessing and improving their testing processes. These are the following:
- Maturity Levels: A progressive framework defining the test process maturity of an organization.
- Process Areas: Key focus areas for achieving maturity at different levels.
- Specific and Generic Goals: Mandatory targets an organization must achieve to satisfy a process area
- Specific and Generic Practices: Recommended activities to help organizations meet the associated goals
- Supporting Informative Components: Guidance materials such as sub-practices, examples, and references
TMMi Maturity Levels
The Test Maturity Model Integration (TMMi) outlines five levels of organizational testing maturity. At Level 1 (Initial), testing is informal and unstructured, typically limited to debugging and lacking defined processes. Level 2 (Managed) introduces basic test management practices, distinguishing testing from debugging and establishing repeatable processes. At Level 3 (Defined), testing is integrated early into the software development lifecycle, supported by standardized procedures, dedicated test organizations, and formal training. Level 4 (Measured) focuses on well-defined, quantifiable processes, comprehensive measurement programs, and coordinated static and dynamic testing. Peer reviews and inspections are systematically used for defect detection and quality management. Level 5 (Optimization) emphasizes continuous process improvement through quantitative analysis, innovation, defect prevention, quality control, and test process optimization. Each level builds on the previous, aiming to enhance efficiency, effectiveness, and product quality in testing.
TMMi Process Areas
Each maturity level, except for Level 1, consists of process areas that cluster related activities essential for advancing test maturity. Implementation guidance is provided through specific and generic practices, supporting organizations in systematically assessing, improving, and optimizing their testing processes as part of a broader approach to software quality assurance.
Level 2 Process Areas:
- Test Policy and Strategy
- Test Planning
- Test Monitoring and Control
- Test Design and Execution
- Test Environment
The Process Areas at TMMi Level 3 are:
- Test Organization
- Test Training Program
- Test Lifecycle and Integration
- Non-functional Testing
- Peer Reviews
Level 4 Process Areas:
- Test Measurement
- Product Quality Evaluation
- Advanced Reviews
The Process Areas at TMMi Level 5 are:
- Defect Prevention
- Quality Control
- Test Process Optimization
TMMi relationship with CMMI
TMMi v1.3 shares a common structure with CMMI v2. [8] The TMMi model has positioned itself as being complementary to CMMI [9]. While TMMi concentrates on testing processes, CMMI was conceived to help improve the entire software development process. Practice areas from CMMI are generally not repeated within TMMi model description, but they are often referenced. The world-wide surveys from 2021[4] and 2023[5] indicate that while initially positioned as a complementary model to CMMI, today TMMi is also widely used independently: around 40%. of its users do not use CMMI - taking the average of both user surveys.
TMMi in the Agile and DevOps environment
TMMi can be integrated with Agile and DevOps approaches, offering practical benefits when applied together. Rather than prescribing strict practices, TMMi serves as a flexible framework for identifying improvements in testing processes. In Agile environments, TMMi practices are often achieved through alternative, business-focused methods. The framework helps ensure important testing activities are maintained—especially those that might be overlooked in Agile or DevOps contexts—and provides guidance for risk reduction and process analysis. Official documents provide case studies on successful TMMi use in both Agile and DevOps settings.
Training
The TMMi Foundation oversees professional training and exams related to the TMMi model, accrediting a global network of training providers to ensure quality and consistency. The TMMi Professional qualification course, based on the official syllabus, is aimed at those involved in test process improvement. Certification is granted upon passing a multiple-choice exam. Following certification, individuals can pursue roles as TMMi Assessors, Lead Assessors, or Test Process Improvers.
Assessment
The TMMi assessment process allows organizations to obtain certification of their software testing maturity. Assessments, conducted by accredited Lead Assessors and Assessors, objectively evaluate test processes and recommend improvements. Certified organizations can demonstrate their capability and maturity to clients.
Organizations can arrange assessments through accredited service providers or independently accredited assessors. The TMMi Assessment Method Application Requirements (TAMAR) outlines the standards for assessments, with the TMMi Assessment Method (TAM) available for licensing.
Self-assessments are possible, though only those using accredited methods and assessors are officially recognized. Assessment results can be submitted to the TMMi Foundation and certified organizations are listed publicly. Surveys indicate many organizations use TMMi concepts without formal certification. As of July 2025, an estimated 9,000 organizations worldwide use TMMi. Ongoing analysis (see [10] ) explores integration with new CMMI appraisal methods.
TMMi in the World
TMMi is implemented globally, with Local Chapters supporting its adoption in over 70 countries as of early 2025. According to recent world-wide surveys and academic studies[11][12][13][14], TMMi has become a leading model for test process improvement, with an estimated 12,500 organizations using its concepts by July 2025. Over 440 companies have been officially assessed and certified to specific TMMi maturity levels.
TMMi's alignment with ISTQB terminology and several ISO standards contributes to its strength and global recognition. The model incorporates Agile and DevOps practices, and is designed for compatibility with other frameworks, including ISTQB and various ISO standards. Its application, benefits, and adoption worldwide have been documented in multiple scientific publications.
TMMi Foundation
The TMMi Foundation, established in 2005, oversees the development and maintenance of the TMMi model, which draws on earlier test maturity frameworks. The Foundation provides free access to the model, supports translations into multiple languages, and manages the training and accreditation of assessors and organizations. It lists recognized training providers and accredited service providers on its official website. Partnered with ISTQB, the Foundation ensures consistent terminology within the software testing community.
See also
Test Maturity Model - Software Testing
References
- ^ a b Erik van Veenendaal, ed. (2022). (TMMi®): Guidelines for Test Process Improvement" (PDF). TMMi (1.3 ed.). [1]
- ^ https://tmsearch.uspto.gov/
- ^ "Assessment Types". TMMi. Retrieved 2025-07-09.
- ^ a b c Word-wide user survey, 2020/ 2021. [2]
- ^ a b c World Wide User Survey, 2022/2023
- ^ Erik van Veenendaal and Brian Wells: Test Maturity Model integration TMMi (Guidelines for Test Process Improvement). 2012, UTN Publishers, Den Bosch, The Netherlands. https://www.tmmi.org/books/
- ^ Erik van Veenendaal and Jan Jaap Cannegieter: The Little TMMI, Objective-Driven Test Process Improvement. . 2011, UTN Publishers, Den Bosch, The Netherlands. https://www.tmmi.org/books/
- ^ Katalin, Balla (2024). "TMMi Structure - to Change or not to Change". TMMi.
- ^ "CMMI Institute - Home". cmmiinstitute.com. Retrieved 2025-06-24.
- ^ Katalin Balla, Jan Jaap Cannegieter and Erik van Veenendaal:The new MDD and TAMAR. White paper TMMi Foundation, April 2023. [3]
- ^ Erik Van Veenendaal: Test Maturity Model integration (TMMi): Test Maturity in the Financial Domain. In: American Journal of Computer Science and Technology. Issue: Volume 7, Issue 2, June 2024, Pages: 43-50. DOI: 10.11648/j.ajcst.20240702.13. [4]
- ^ Vahid Garousi, Michael Felderer, and Tuna Hacalo˘glu: What we know about software test maturity and test process improvement IEEE Software, January/ February 2018 (2018)
- ^ Erik van Veenendaal, Vahid Garousi and Michael Felderer: Motivations for and Benefits of Adopting the Test Maturity Model integration (TMMi) Software Quality – The Next Big Thing in Software Engineering and Quality, May 2022, Springer Publishing (2022)
- ^ Test Maturity Model integration (TMMi): Trends of Worldwide Test Maturity and Certifications (pre-print) - IEEE Software, March/April 2022, (Vahid Garousi and Erik van Veenendaal). [5]
External links
CMMI - Capability Maturity Model Integration
ISTQB® and TMMi® Renew Their Alliance Agreement to Advance Software Testing
- in-depth (not just passing mentions about the subject)
- reliable
- secondary
- independent of the subject
Make sure you add references that meet these criteria before resubmitting. Learn about mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.