Draft:Test Maturity Model integration

  • Comment: I am concerned about the independence of the sourcing here. TMMi is a commercial product under trademark. Most of the article's content, in word count, has come from user(s) with apparent links to TMMi, the fact that TMMi is used in 70 countries is sourced to the boss of TMMi, who appears in 6 of the 17 sources. Some of the sources appear to be independent academics, albeit without declarations of interest, but these support statements like the links to CMMI and SPICE, which are fairly straightforward points. ChrysGalley (talk) 19:37, 2 December 2025 (UTC)
  • Comment: Way to many primary sources. Stuartyeates (talk) 23:01, 19 July 2025 (UTC)


Test Maturity Model integration (TMMi) is a structured framework designed to help organizations evaluate and improve the maturity of their software testing processes.[1] Developed and maintained by the TMMi Foundation,[2] it provides comprehensive guidance, best practices, and assessment criteria focused exclusively on testing activities.[3] TMMi defines five maturity levels (1 to 5): Initial, Managed, Defined, Measured and Optimization.[1] TMMi addresses all test levels, from static to dynamic, including component, integration, system, and acceptance tests.

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.[4] The framework adheres to current testing standards and incorporates terminology established by the International Software Testing Qualifications Board (ISTQB). TMMi is a registered trademark[5] of TMMi Foundation Limited.

TMMi Maturity Levels

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.[6]

Agile and DevOps

The framework has also proven to be adaptable to Agile and DevOps contexts.[7] TMMi does not prescribe rigid methods but instead provides a reference for identifying improvements.[8] Within Agile projects, TMMi practices are achieved through alternative approaches,[9] while in DevOps environments the model ensures that essential testing activities are not neglected in delivery cycles.[10] Official case studies document its successful application in these settings.[11]

References

  1. ^ a b "What is TMMI (Test Maturity Model Integration) in Software Testing?". Testbytes Softwares. Retrieved 2025-09-26.
  2. ^ "TMMI FOUNDATION LIMITED overview - Find and update company information - GOV.UK". find-and-update.company-information.service.gov.uk. Retrieved 2026-01-09.
  3. ^ Afzal, Wasif; Alone, Snehal; Glocksien, Kerstin; Torkar, Richard (2016-01-01). "Software test process improvement approaches: A systematic literature review and an industrial case study". Journal of Systems and Software. 111: 1–33. doi:10.1016/j.jss.2015.08.048. ISSN 0164-1212.
  4. ^ BRIS, PETR (2015-12-01). "SOFTWARE QUALITY CONTROL WITH THE USAGE OF IDEAL AND TMMI MODELS".
  5. ^ "Trademark Search". tmsearch.uspto.gov. Retrieved 2025-07-18.
  6. ^ Prastiti, Rizdiani (2023-01-01). Evaluation of Maturity Level and Recommendations for Improvement of Software Testing Process Based on Test Maturity Model Integration (TMMi): A Case Study. Jurnal Komtika (Komputasi dan Informatika).
  7. ^ Unudulmaz, Ahmet; Kalıpsız, Oya (2020-04-17). "TMMI Integration with Agile and Test Process". Proceedings of the Evaluation and Assessment in Software Engineering. EASE '20. New York, NY, USA: Association for Computing Machinery. pp. 375–378. doi:10.1145/3383219.3386124. ISBN 978-1-4503-7731-7.
  8. ^ Camargo, Kamilla Gomes; Ferrari, Fabiano Cutigi; Fabbri, Sandra Camargo Pinto Ferraz (October 2013). "Identifying a Subset of TMMi Practices to Establish a Streamlined Software Testing Process". 2013 27th Brazilian Symposium on Software Engineering. pp. 137–146. doi:10.1109/SBES.2013.6. ISBN 978-1-4799-3244-3.
  9. ^ Nikolova, Teodora (January 2022). "Exploratory Testing in the Context of TMMi in the Agile World". Retrieved 2026-01-09.
  10. ^ "Is TMMi Relevant in DevOps to Improve the Testing Process?". EuroSTAR Conference. Retrieved 2026-01-09.
  11. ^ Camargo, Kamilla G.; Ferrari, Fabiano C.; Fabbri, Sandra CPF (2015). "Characterising the state of the practice in software testing through a TMMi-based process". Journal of Software Engineering Research and Development. 3 7. doi:10.1186/s40411-015-0019-9.

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.