TMMi-P_Syll2.1 TMMi Test Maturity Model Integration Professional (TMMi-P) Questions and Answers

The Learning Phase in the IDEAL improvement framework is the final phase in the cycle and plays a crucial role in ensuring continuous improvement. Contrary to the belief that it is less important because most work has been done in previous phases, this phase is critical for learning from the experience gained during the improvement program. The Learning Phase ensures that the organisation refines its ability to implement change effectively.

The key activities in this phase are:

Analyze and Validate: This involves reviewing what has been achieved, whether the goals have been met, and identifying lessons learned. It focuses on what worked well and what could be done better.

Propose Future Actions: Based on the analysis, recommendations are made to improve future programs. These proposals are often forwarded to management for consideration.

Thus, the Learning Phase is essential for organisational growth as it solidifies the learning from past improvements and applies it to future cycles, fostering continuous refinement of processes.

" Provide Necessary Test Training " is part of the Test Training Program process area, not the Test Organization process area. Test Organization focuses on establishing a structured group responsible for testing, defining roles, career paths, and implementing process improvements. Therefore, providing test training is not a specific goal of Test Organization but rather falls under the Test Training Program process area.

The Diagnosing phase in the IDEAL test improvement cycle is focused on understanding the current state of the organization ' s testing processes and identifying the areas for improvement. One of the key activities during this phase is Develop Recommendations , which involves analysing the current process against the goals and proposing areas where improvements can be made to achieve the desired state. Other activities in this phase include characterizing the current and desired states .

At TMMi Level 4, the scope includes process areas like Test Process Optimization , Product Quality Evaluation , and Advanced Reviews . However, Test Lifecycle and Integration is part of TMMi Level 3 and focuses on aligning test processes with development processes, not on Level 4. Therefore, it is not within the scope of a test improvement program aimed at achieving TMMi Level 4​​.

Each statement about TMMi level 2 in an Agile context requires careful consideration within the framework:

(a) : False. While Agile projects indeed use metrics like Velocity, TMMi requires tracking end-results such as escaped defects. Both team performance and outcomes, including defect-related metrics, are significant. Test performance indicators at TMMi level 2 in an Agile context should not solely focus on team performance metrics .

(b) : True. The product risk assessment process in Agile projects typically adopts a more lightweight approach compared to traditional sequential lifecycle models. Agile teams often conduct risk assessments in a more collaborative and iterative manner .

(c) : False. In Agile, monitoring and controlling processes are still critical to ensure goals and quality targets are met, even if the methodology allows for flexibility and adaptation .

(d) : False. Traceability is still relevant in Agile, although it may be implemented differently. Agile methodologies such as Scrum do not eliminate the need for traceability between requirements, test conditions, and tests, which is an essential part of TMMi process areas .

(e) : True. Agile allows for flexibility in defining the test environment closer to the execution phase, enabling changes that reflect evolving requirements and design decisions .

Thus, the correct combination is A : Statements (a) and (e) are true, while statements (b), (c), and (d) are false​ .

The generic practice " Establish a defined process " addresses the need to tailor a managed process from the organization’s set of standard processes. This practice is part of Generic Goal 3 (GG 3) , which aims to ensure that processes are standardized and defined across the organization. By tailoring processes based on established guidelines, organizations can create specific implementations that fit their projects while maintaining consistency and control across the organization.

TMMi References :

In TMMi, establishing a defined process involves tailoring standard processes to suit specific project needs, ensuring the institutionalization of best practices across projects​​.

The Testing quadrants model is an Agile practice that helps establish a test strategy, as it provides a framework for categorising different types of tests (e.g., business-facing or technology-facing) and helps in balancing test activities. Within the TMMi Level 2 process area for Test Policy and Strategy, testing quadrants offer an Agile way to define and implement a test strategy that ensures comprehensive testing across various levels and types of testing activities.

The TMMi framework is applicable to all levels of testing, including static testing (such as reviews) and dynamic testing, regardless of the phase of the software development lifecycle. TMMi encompasses structured testing activities across various test levels such as component testing, integration testing, system testing, and user acceptance testing, along with both static and dynamic techniques. Therefore, all levels of testing can be improved using the TMMi model.

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.

Test Design and Execution is a key process area at TMMi Level 2, not Level 3. However, other process areas at TMMi Level 3 include Non-functional Testing, Peer Reviews, and Test Lifecycle and Integration. Test Design and Execution plays a foundational role in laying down the practices for creating and executing test cases, especially at earlier maturity levels. By TMMi Level 3, processes become more sophisticated with a broader range of testing techniques and integration into the overall lifecycle.

The specific practice " Testers review test basis documents " belongs to the Peer Reviews process area. At TMMi Level 3, the Peer Reviews process area involves static testing activities where testers and other stakeholders review key work products, such as requirements and design documents, to identify defects early in the lifecycle. By involving testers early through these reviews, organisations can enhance testability and improve overall quality.

A direct benefit of a test improvement program is higher productivity . When test processes are streamlined, better test planning, design, and execution can lead to reduced testing times, fewer defects, and quicker turnaround of quality products. This has a direct impact on organisational efficiency, allowing for more effective use of resources and time.

Agile organisations often focus on rapid iterations and minimal documentation, which can lead to the omission or underuse of structured testing practices. TMMi serves as a valuable guide for Agile teams by highlighting critical testing practices that might be overlooked, ensuring that essential quality processes such as risk analysis, peer reviews, and test planning are not neglected​​​.

This reminder ensures that teams maintain a disciplined approach to testing while still benefiting from Agile flexibility.

At TMMi Level 5, the process areas Defect Prevention , Quality Control , and Test Process Optimization work together to support continuous process improvement. Specifically:

Defect Prevention focuses on identifying and analysing common causes of defects and proposing corrective actions to prevent them from recurring. This includes submitting test improvement proposals, which help Test Process Optimization fine-tune the testing process through these insights​​.

While Quality Control supports Defect Prevention through statistical methods and analysis, the correct relationship between Defect Prevention and Test Process Optimization involves submitting test improvement proposals to optimise the process.

The TMMi process areas complement the CMMI process areas for Verification and Validation by providing more detailed guidance specific to testing. While CMMI defines these areas at a high level, TMMi elaborates on how to establish and maintain a defined testing process that includes both verification and validation activities. The relationship between the two models is complementary rather than hierarchical, meaning that improving testing processes using TMMi can lead to fulfilling CMMI requirements for Verification and Validation.

The correct order of TMMi maturity levels from low to high is:

Managed (Level 2): Testing becomes a managed and separate process from debugging, with formal strategies and plans.

Defined (Level 3): Testing is fully integrated into the development lifecycle, with standardized processes across projects.

Measured (Level 4): Testing processes are measured quantitatively, and product quality is evaluated with formal metrics.

This sequence reflects the increasing maturity and sophistication of an organization ' s testing processes as they progress through the levels.

TMMi References :

The TMMi maturity levels follow the order of Managed (Level 2) , Defined (Level 3) , and Measured (Level 4) ​​.

For the Test Policy and Strategy process area, with a 40% 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​​​.

The process area Non-functional Testing at TMMi Level 3 focuses on performing a structured test execution process for non-functional attributes of the system. The specific goals for this process area include:

Perform a Non-functional Product Risk Assessment

Perform Non-functional Test Analysis and Design

Perform Non-functional Test Implementation

The creation of a specific non-functional test plan is not explicitly listed as a goal within this process area, although defining a non-functional test approach is addressed. Hence, " Establish a Non-functional Test Plan " (B) is not a specific goal of the Non-functional Testing process area​​.

This statement is false because the CMMI does not have defined levels specifically for testing maturity. The CMMI model is more general and focuses on overall process improvement across various disciplines, including but not limited to testing. CMMI includes practices like verification and validation but does not specifically address a structured path to testing maturity, unlike TMMi, which defines specific levels for testing process maturity. Therefore, statement D is incorrect.

Regular code reviews and architectural reviews are part of the Advanced Reviews process area, which belongs to TMMi Level 4 . This process area emphasizes conducting static reviews (e.g., code and design reviews) early in the lifecycle to measure product quality and adjust the testing strategy based on the insights gained from these reviews.

TMMi References :

The Advanced Reviews process area in TMMi Level 4 aims to ensure that static testing activities such as code and architectural reviews are used to measure product quality early in the lifecycle​​.

The specific practice " Define product risk categories and parameters " is part of the Test Policy and Strategy process area in TMMi. This practice involves identifying and categorizing the product risks to guide testing efforts and establish a clear understanding of potential product issues. Product risk categories help in determining the focus areas for testing, ensuring that testing is prioritized based on business and technical risks.

TMMi References :

The practice of defining product risk categories is directly linked to the Test Policy and Strategy process area at TMMi Level 2 , where risk-based testing approaches are established​​.

The Advanced Reviews process area, which is part of TMMi Level 4 , is concerned with measuring product quality early in the lifecycle. It aims to enhance the test strategy and test approach by aligning static testing (reviews and inspections) with dynamic testing (execution of test cases). The results and data from static testing are used to optimize the dynamic testing approach, making the overall testing process more efficient and effective.

TMMi References :

Advanced Reviews at TMMi Level 4 focuses on integrating static and dynamic testing approaches to optimize test strategy and product quality evaluation​​.

Informal assessments, as described in the TMMi framework, are often quicker and cheaper as they do not require the extensive corroboration of evidence that formal assessments do. One key characteristic of informal assessments is that they may rely solely on interviews, without using other forms of corroboration such as documentation reviews or observations. These informal assessments provide an indicative view of the organization ' s maturity level but do not result in formal certification​

The Acting phase of a test improvement cycle focuses on executing the planned improvements. Key activities during this phase include creating solutions to address identified problems, planning actions to implement those solutions, and piloting solutions before full-scale deployment. These steps ensure that the improvements are well-defined, tested in a controlled environment, and refined before being fully implemented across the organisation.

With a 40% achievement in the Test Planning process area, the rating would be " Partly achieved. " According to TMMi, a process area is rated " Partly achieved " when the percentage of achievement is between 15% and 50%. This indicates that some practices have been implemented, but significant improvement is still required to meet the full requirements of the process area.

Sprint retrospectives are held at the end of every sprint (not every 2-3 iterations) to evaluate the team ' s performance and identify opportunities for improvement. Retrospectives are a core Agile practice, but they are not considered peer reviews, which typically involve reviewing work products such as code or design documents. Peer reviews focus on product quality, while retrospectives focus more on team performance and process improvements.

The generic assessment process in TMMi follows a structured sequence. The correct order for the assessment phases is:

Planning phase : This involves setting the scope, goals, and strategy for the assessment. It includes assembling the assessment team, setting timelines, and defining objectives.

Preparation phase : In this phase, the necessary preparation for the assessment is done, including gathering initial information, documents, and materials. The assessment team familiarizes itself with the organization’s processes.

Interview phase : This phase includes conducting interviews with key stakeholders and collecting direct evidence about the current processes.

Reporting phase : This is the final phase where the results of the assessment are compiled into a report, including findings, recommendations, and a roadmap for improvements.

Hence, the correct sequence is Planning, Preparation, Interview, Reporting which matches option B (2, 3, 1, 4) .

A test policy is a high-level document that outlines the objectives, goals, and strategic views regarding testing. It serves to align testing activities with the organisation ' s business objectives and quality goals. One of the critical elements in a test policy is defining the quality levels to be achieved , which ensures that testing aligns with the expectations for product quality, both functional and non-functional. Other aspects, such as risk categories, test types, and regression testing approaches, are typically defined in more detailed test strategies or plans, not in the high-level policy.

This statement is not true regarding a staged model. In a staged model , such as TMMi, organisations must follow a pre-defined path through maturity levels, and the process areas are organised in a fixed order that must be achieved sequentially. Each maturity level forms the foundation for the next, meaning that an organisation cannot achieve process areas at different capability levels independently, as is possible in a continuous model like CMMI. The staged model is designed to ensure that each process area is fully implemented and institutionalised before progressing to the next maturity level.

The specific goals of the Test Process Optimization process area at TMMi Level 5 include:

Select test process improvements .

Evaluate new testing technologies to determine their impact on the testing process .

Deploy test process improvements .

However, " Determine, plan and implement test process improvements " (2) and " Monitor product quality against plan and expectations " (5) are not part of the Test Process Optimization goals. Instead, these activities belong to other process areas, such as Test Measurement or earlier maturity levels.

TMMi References :

The goals for Test Process Optimization at TMMi Level 5 focus on selecting and deploying process improvements and evaluating new technologies​​.