For theTest Policy and Strategyprocess area, with a40% achievement, the appropriate compliance rating is"Partly achieved". According to TMMi, a process area is rated as "partly achieved" when a portion of the practices has been implemented, but significant improvements are still needed​​​.

A typical business reason for starting a test improvement program is to achievehigher productivity. Test process improvements can lead to better efficiency in test execution, reduction of defects, and optimised resource usage, all of which contribute to the overall productivity of the organisation. By improving testing processes, organisations can reduce time-to-market and minimise costs associated with fixing defects post-production, which in turn boosts productivity.

In an Agile context, theSCRUM teammodel is a typical format for a test organisation. Testing is integrated into the cross-functional SCRUM team, with testers working alongside developers and product owners throughout the sprint. This ensures that testing is a continuous activity, rather than a separate phase. The test organisation in Agile environments focuses on collaboration and team-based activities, rather than a separate or independent test group​​.

This statement isFALSEbecause TMMi doesnotfocus only on higher test levels like system and acceptance testing. In fact, TMMi coversall test levels, including lower levels like unit and integration testing, as well as static testing (e.g., reviews and inspections).

TMMi is designed to address testing at all levels of the software lifecycle and goes beyond dynamic testing (e.g., system and acceptance) to include static testing techniques as well. The model is comprehensive and is intended to support testing in bothsystems and software engineering. Furthermore, TMMi addresses the fourcornerstonesof structured testing:lifecycle,techniques,infrastructure, andorganization. These are essential to ensure a thorough and structured approach to improving test processes and aligning them with business goals.

TMMi References:

TMMi documentation clearly indicates that it coversall test levelsincluding static testing (such as peer reviews) and dynamic testing across different stages of development​​.

It is lifecycle-independent and can support different models, such as Agile, DevOps, and traditional V-models​.

The description provided, "Testing is a thoroughly defined, well-founded, and measurable process. Testing is perceived as evaluation; it consists of all lifecycle activities concerned with checking products and related work products," corresponds to TMMi Level 4, which is labelled "Measured." At this level, testing processes are quantitatively measured, and there is a strong focus on evaluating product and process quality using quantitative metrics. Testing is integrated throughout the lifecycle and becomes a predictable, measurable process that supports organisational goals.

A. Required component (II): Must be achieved. These are specific and generic goals that are mandatory for reaching a particular maturity level.

B. Expected component (III): Will typically be implemented. Expected components include specific and generic practices, which provide guidance on how to achieve required goals.

C. Informative component (I): Supports the understanding. Informative components provide details that help organisations understand and implement the required and expected components effectively, such as sub-practices and example work products.

In an Agile context, the emphasis is typically placed on lightweight, flexible documentation. Test documentation should be "just enough" to support the test process, and excessive documentation may be seen as unnecessary overhead. Therefore, calling formore rigorous and thorough documentationisnotin line with Agile principles. Instead, Agile favours working software and collaboration over comprehensive documentation, supported by mentoring and just-in-time guidance rather than formalised documentation​.