Top 3 Misconceptions About the Test Maturity Model Integration

PatThe Test Maturity Model Integration (TMMi®) is a quality model framework focused strictly on testing. TMMi addresses the Testing Lifecycle from policy, planning and environments at lower levels of maturity to defect prevention, software quality evaluations and test process optimization at higher levels of maturity. I’ve covered it in more detail in a previous blog post.

As with any quality model, there tends to be a lot of misconceptions and questions of value - and the TMMi is no exception. Here, I dispel the top three myths about the TMMi.

Major Misconception #1: TMMi will not work with the existing process frameworks we already use in-house!

Answer: False. Think of the TMMi as an extension to the existing quality model frameworks in-house. Remember, most quality models deal with the entire lifecycle. That typically covers planning, requirements, design, and then test. TMMi takes the test phase of your lifecycle and adds the level of rigor required to ensure quality prevention, not quality detection.

Major Misconception #2: TMMi will only work in a waterfall environment.

Answer: Really? How many organizations these days strictly do waterfall. Okay, some, but not many. Most organizations do some form of Agile these days - even if it is a hybrid version. Agile teams do testing too. Think about the following: you'd have a policy around performing testing, you'd have project plans (albeit they may be called something else or included in a backlog or release plans), you'd execute test, you'd monitor the results, you'd conduct peer reviews, you'd conduct non-functional test. Do these things seem reasonable? Do they sound like things that may be included in the sprint tasks or in the definition of done? TMMi works in more than just a waterfall environment.

Major Misconception #3: The TMMi model will add way too much time and effort to an already stretched budget and schedule.

Answer: Like most models, it isn't the framework that is bad, it's the implementation. You can take any framework and load it up with excessive process. Think of model implementation as a plate of nachos. The framework is the chips, it's simple and serves as the foundation. It's up to you how heavy you make the toppings (implementation). The purpose of the TMMi framework is to give you structure that provides value and aids in producing a quality product through the prevention of defects - not trying to find the defects under layers of development after it's too late.

Hopefully these myth busters give you a better understanding of and appreciation for the TMMi model.

Learn more about the value of the TMMi model, and our partnership with TMMi service provider Experimentus, in this Q&A with Martin Adcock, Managing Director of Experimentus.

Questions? Other myths you’d like to have addressed? Just let me know in the comments!

Pat Eglin
Consultant, CMMI Instructor, TMMi Service Provider

Written by Default at 08:00
Tags :
Categories :


kkdslfhhvz said...
May 2, 2020 04:10


"It's frustrating that there are so many failed software projects when I know from personal experience that it's possible to do so much better - and we can help." 
- Mike Harris, DCG Owner

Subscribe to Our Newsletter
Join over 30,000 other subscribers. Subscribe to our newsletter today!