TMMi: the five maturity levels and what an assessment involves

What TMMi is

TMMi is a reference model for test process improvement maintained by the TMMi Foundation. It is staged: an organization is at a level, and the level is earned by satisfying every process area at that level and all the levels below. The structure mirrors CMMI, with maturity levels, process areas, specific goals, specific practices and generic goals, and it is designed to be used alongside CMMI where a development organization already has one. The original magazine site that this domain once hosted carried a TMMi workshop announcement and a paper on the model; this guide is, as far as we can tell, the current explanation of the model that those readers were looking for.

The value of the model is not the certificate. It is the process area list, which is a checklist of what a mature test organization does that an immature one does not, and the assessment, which tells you honestly where you stand.

The five maturity levels

1. Level 1, Initial. Testing is chaotic and undefined. It is debugging done after coding, with no plan, no separation from development, and success depending on individuals.
2. Level 2, Managed. Testing is a managed process, separate from debugging. There is a test policy and strategy, plans are written, progress is monitored, tests are designed from a test basis, and environments are managed.
3. Level 3, Defined. Testing is an organization-wide, standard process integrated into the development lifecycle. There is a test organization, a training program, non-functional testing and peer reviews.
4. Level 4, Measured. Testing is measured and product quality is evaluated with data. Test measurement, product quality evaluation and advanced reviews are institutionalized.
5. Level 5, Optimization. The process improves itself. Defect prevention, statistical quality control and test process optimization run continuously.

Process areas at each level

How a formal assessment runs

A formal TMMi assessment is carried out under the TMMi Assessment Method Application Requirements, known as TAMAR, by a lead assessor accredited by the TMMi Foundation. The sponsor agrees the scope: which business units, which projects, which target level. The team then collects evidence in three ways: documents (policies, strategies, plans, reports, review records), interviews with testers, test managers, developers and project managers, and observation of the process in use. Each specific and generic practice in every process area within scope is rated on the degree to which it is implemented and institutionalized, typically on a four-point scale from not achieved to fully achieved.

A process area is satisfied when all its goals are satisfied; a level is awarded only when every process area at that level and below is satisfied. The output is a findings report with strengths, weaknesses and the rated level, and, in a formal assessment, a certificate that is valid for a fixed period. Informal assessments follow the same structure without the accreditation and certificate; they are the right starting point because they are cheaper and the findings are what you actually need. A formal assessment of a mid-sized organization takes two to four weeks of assessor time and involves 15 to 30 interviews.

What moving to level 3 changes day to day

Level 2 can be achieved project by project; level 3 requires the organization to own the process. In practice a tester notices these changes. There is a standard test process with tailoring guidelines, so a new project starts from a template rather than a blank page. There is a test organization with a manager who is not the project manager, so testers are not reassigned to development when the schedule slips. Training is planned; a tester joining a team is expected to learn the techniques in the techniques hub and the organization pays for it. Non-functional testing is in every plan, not bolted on when a customer complains about response times. And requirements and designs are peer reviewed before code is written, which is where a large share of defects is found once level 3 is reached.

The cost is real. Reaching level 3 from level 1 typically takes 18 to 36 months, a full-time process improvement role, and sponsorship from someone who controls budgets. The benefit shows up in the numbers that a level 4 organization will later measure: fewer escaped defects, shorter test cycles, and estimates that hold.

TMMi and CMMI

CMMI covers the whole of development and treats verification and validation as two process areas among many. TMMi takes the same staged structure and expands testing into sixteen areas across four levels above Initial. An organization at CMMI level 3 is not automatically at TMMi level 3; the models are complementary and the TMMi Foundation positions TMMi as the detailed testing counterpart that CMMI lacks. Where both are in use, the level 2 and 3 generic practices align, so evidence collected for one supports the other. Where only TMMi is in use, it stands alone; no CMMI rating is needed.

The relation to the fundamental test process is direct: level 2 is essentially the point at which every activity of that process exists and is managed. The levels above make the process organizational, measured, and self-improving. The ROI of testing argument is often what unlocks the sponsorship a level 3 program needs.

This guide is part of the test management hub. It is best read alongside software test process and ROI of testing, which cover the neighbouring questions.