Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Assessing maturity

9 min

Listen to this lesson

0:00 / 8:21

This is the capstone of the TCoE track. The earlier courses built the business case, the operating model, the standards, the tooling, the data and environment services, the metrics and the partner model. This one asks where the TCoE stands now, where AI belongs in it, and what the next 24 months should deliver. It starts with an honest assessment, because a roadmap built on a flattering self-image fails at its first checkpoint.

Two ways to assess

ISTQB's Advanced Test Management syllabus (CTAL-TM v3.0) describes two complementary approaches to test process improvement. A model-based assessment compares your practices with a reference model and shows gaps against good practice. An analytical assessment starts from your own data, such as root causes of escaped defects and the KPIs from sap-tcoe-406, and shows the gaps that actually hurt you. Use both: the model tells you what you are missing, the data tells you what to fix first.

The TMMi model

The Test Maturity Model integration (TMMi), maintained by the TMMi Foundation, is the most widely used model for test process maturity. It is staged: level 1 is initial and ad hoc, and each higher level adds process areas that must all be in place, together with those of the levels below, before the level is achieved. The process areas below are those of TMMi release 1.3, which most assessments and training still use.

LevelNameProcess areas (release 1.3)
1InitialNone: testing is ad hoc and depends on individuals
2ManagedTest Policy and Strategy; Test Planning; Test Monitoring and Control; Test Design and Execution; Test Environment
3DefinedTest Organization; Test Training Program; Test Lifecycle and Integration; Non-functional Testing; Peer Reviews
4MeasuredTest Measurement; Product Quality Evaluation; Advanced Reviews
5OptimizationDefect Prevention; Quality Control; Test Process Optimization

TMMi maturity levels and process areas. A level is achieved only when all its process areas, and those below, are satisfied.

TMMi is changing. The TMMi Foundation published the TMMi Framework Model v2.0 in June 2026. According to the Foundation and its exam partners, it integrates Agile and DevOps practices, adds guidance on where AI and automation support each process area using a people, process and technology view, replaces the separate generic goals and practices with a new level 2 process area, Implementation and Habit, renames a level 3 process area to Test Process and Integration, and is about 30% shorter. The Foundation states that assessments and certifications based on release 1.3 will not be available after August 1, 2027. Plan any formal assessment after that date on v2.0. Requirements for informal and formal assessments are set out in the TMMi Assessment Method Application Requirements (TAMAR), currently v1.3.

TMMi is not the only option. CTAL-TM also describes TPI NEXT, which rates 16 key areas, such as test strategy, metrics, tools and test environment, at four maturity levels and is not staged in the same way. Pick one model and stay with it for the roadmap's life, so progress is comparable.

Running an evidence-based assessment

An informal assessment in seven steps. The analytical view keeps the findings tied to Contoso's real problems.
The Sign-Off Table · thesignofftable.com/academy/sap-tcoe-408

Evidence means artifacts and records, not opinions: the test policy and strategy, test plans in SAP Cloud ALM, the readiness notes from sap-tcoe-405, KPI cards and council minutes, training records, review records. Interviews confirm how practices are really used, for example by asking a project test lead how the TCoE was involved in the Explore phase. Assessors rate how fully each practice and goal is implemented, from not achieved to fully achieved, and a process area is satisfied only when its goals are.

Contoso at the end of year 1

Process areaLevelRatingMain evidence or gap
Test Policy and Strategy2LargelyCharter and policy exist; projects still use two strategy templates
Test Planning2FullyRelease and project test plans in SAP Cloud ALM
Test Monitoring and Control2LargelyKPIs and council in place since month 9
Test Design and Execution2LargelyRisk-ranked pack; procure to pay coverage only 60%
Test Environment2PartiallyData recipes only for two value streams; masking still partly manual
Test Organization3LargelyTCoE, business test network and partner model working
Test Training Program3PartiallyOnboarding exists; no role-based curriculum
Test Lifecycle and Integration3PartiallyProjects involve the TCoE late, after Explore
Non-functional Testing3Not achievedOnly weekend performance checks; no security test standard
Peer Reviews3PartiallyTest cases reviewed; specs rarely
Test Measurement4PartiallyKPI cards defined; history since month 9

Contoso's informal self-assessment against TMMi release 1.3 at the end of the TCoE's first year. Ratings are illustrative course data.

Read the result carefully. Because Test Environment is only partially achieved, Contoso is formally still at TMMi level 1, even though most level 2 work is strong and parts of level 3 are under way. That is a common pattern and a useful message for the sponsor: one weak area, test data and environments, holds back the formal rating and, more importantly, limits the value of automation. The analytical view agrees: the most serious escapes in year 1 clustered in procure to pay, where coverage and data recipes were weakest.

High impact, high effortNon-functional testing standard; plan it in year 2
High impact, low effortTest Environment: extend recipes and automate masking first
Low impact, high effortPeer reviews of all functional specs; defer and sample
Low impact, low effortOne strategy template for all projects; quick win
Prioritizing Contoso's gaps. The roadmap starts top right, where impact is high and effort is low.
The Sign-Off Table · thesignofftable.com/academy/sap-tcoe-408

What would you do?

Grace suggests the TCoE announce that it is "TMMi level 2" because most level 2 process areas are largely achieved. What should Priya say?

Key points
  • Combine a model-based assessment with an analytical one based on escapes and KPIs.
  • TMMi is staged: every process area at a level, and below it, must be satisfied before the level is achieved.
  • TMMi v2.0 (June 2026) adds Agile, DevOps and AI guidance; release 1.3 assessments end after August 1, 2027.
  • Rate with evidence, not opinions, and rank gaps by impact and effort; Contoso's first gap is Test Environment.

Check your understanding · not graded

Lesson check

  1. 1. Why is Contoso formally at TMMi level 1 despite strong level 2 work?

  2. 2. What does an analytical assessment add to a model-based one?

  3. 3. Which new level 2 process area does TMMi v2.0 introduce?

  4. 4. Why should Contoso plan any formal TMMi assessment on v2.0?