clement13.net
Original photo: A testing laboratory
Description
A testing laboratory
Source
Daderot · original page
Licence
CC0 Public domain
Original photo, unretouched. The background is a version of it stylised by the site.

Testing — TMMi

How do you move from ad hoc, reactive testing to a defined, measured, then optimized test process?

≈ 2 min readReading
At a glance
  • 5 staged, cumulative levels.
  • 16 process areas (levels 2 to 5).
  • Measured with evidence, not impressions.
On this page
  1. Profile
  2. Why this matrix matters in my field
  3. The maturity scale
    1. Initial
    2. Managed
    3. Defined
    4. Measured
    5. Optimization
  4. The dimensions assessed
    1. Level 2 — Test Policy and Strategy
    2. Level 2 — Test Planning
    3. Level 2 — Test Monitoring and Control
    4. Level 2 — Test Design and Execution
    5. Level 2 — Test Environment
    6. Level 3 — Test Organization
    7. Level 3 — Test Training Program
    8. Level 3 — Test Lifecycle and Integration
    9. Level 3 — Non-functional Testing
    10. Level 3 — Peer Reviews
    11. Level 4 — Test Measurement
    12. Level 4 — Product Quality Evaluation
    13. Level 4 — Advanced Reviews
    14. Level 5 — Defect Prevention
    15. Level 5 — Quality Control
    16. Level 5 — Test Process Optimization
  5. How to use it
  6. Limitations and precautions
  7. Sources and verification

Profile#

Organization
TMMi Foundation
Model
TMMi — Test Maturity Model integration, designed as a complement to CMMI
Purpose
Assess and improve the test process
Scale
5 staged levels: Initial, Managed, Defined, Measured, Optimization
Dimensions
Process areas attached to each level (levels 2 to 5)
Access
Reference model published by the foundation; formal assessments by accredited assessors

Why this matrix matters in my field#

Testing standards (continuous testing, quality testing, automation) become an organizational matter as soon as several teams contribute. TMMi provides a clear trajectory: test policy and strategy, planning, design, environments, then organization, training, life cycle integration, measurement and defect prevention.

The maturity scale#

TMMi is a staged model: each level assumes that the process areas of the previous level are satisfied. Level 1 has no process areas.

  1. Initial#

    Testing is not planned and remains reactive, imperfectly separated from debugging. No process areas.

  2. Managed#

    Basic planning exists: policy and strategy, test plan, monitoring, design and execution, test environment.

  3. Defined#

    Test processes are standardized and integrated into the life cycle; test organization, training, non-functional testing, peer reviews.

  4. Measured#

    Testing is quantified: measurements, product quality evaluation, advanced reviews.

  5. Optimization#

    The process is continuously improved: defect prevention, quality control, test process optimization.

The dimensions assessed#

Sixteen process areas, distributed by level (original names in italics). To be checked against the model's reference version.

  • Level 2 — Test Policy and Strategy#

    Test Policy and Strategy

  • Level 2 — Test Planning#

    Test Planning

  • Level 2 — Test Monitoring and Control#

    Test Monitoring and Control

  • Level 2 — Test Design and Execution#

    Test Design and Execution

  • Level 2 — Test Environment#

    Test Environment

  • Level 3 — Test Organization#

    Test Organization

  • Level 3 — Test Training Program#

    Test Training Program

  • Level 3 — Test Lifecycle and Integration#

    Test Lifecycle and Integration

  • Level 3 — Non-functional Testing#

    Non-functional Testing

  • Level 3 — Peer Reviews#

    Peer Reviews

  • Level 4 — Test Measurement#

    Test Measurement

  • Level 4 — Product Quality Evaluation#

    Product Quality Evaluation

  • Level 4 — Advanced Reviews#

    Advanced Reviews

  • Level 5 — Defect Prevention#

    Defect Prevention

  • Level 5 — Quality Control#

    Quality Control

  • Level 5 — Test Process Optimization#

    Test Process Optimization

How to use it#

  1. Assess each process area of the target level (satisfied, partially, not).
  2. Do not skip levels: the areas of one level build on those of the previous one.
  3. Attach evidence to each area (plans, execution reports, indicators).
  4. Use the model as a roadmap, not as a certification in itself.

Limitations and precautions#

  • The level reached says nothing about the effectiveness of testing on a given product.
  • Automation is not a level: you can automate a poorly defined process.
  • The staged structure can seem rigid for agile teams; adapt it rather than applying it to the letter.

Sources and verification#