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

The specific practice "Establish the Organization’s Test Process Database" is found within the Test Lifecycle and Integration process area, which is part of TMMi Level 3. This process area aims to establish standardized test processes across the organization, including maintaining a test process database that holds process-related information and data for reuse and continuous improvement.

TMMi References:

The Test Lifecycle and Integration process area is responsible for establishing and maintaining organizational test process assets, including the test process database​​.

In the scenario described, where an organisation suffers from poor test estimations despite many practices being in place, the process area that requires attention is Test Planning. Specifically, SG 3 (Establish Test Estimates) focuses on developing well-founded estimates for testing effort and cost. This includes creating a top-level work breakdown structure, defining the test lifecycle, and determining estimates for the test effort and costs associated with different test activities. By addressing these practices, the organisation can improve its ability to generate accurate test estimations, leading to better project planning and resource allocation.

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​​.

Planning poker is an Agile technique commonly used to estimate effort, and it can be adapted for use in the Test Planning process area to help estimate test efforts (SG3: Establish Test Estimates). This collaborative technique brings stakeholders together to estimate the effort required for tasks by assigning numerical values in a consensus-driven manner. It is particularly effective in Agile environments where estimation is iterative and frequently updated based on evolving project needs​.

The TMMi model is designed to be versatile and applicable across all test levels (including static and dynamic testing) and all types of development methodologies, such as waterfall, Agile, and DevOps. It provides comprehensive coverage of the testing process, ensuring that all critical aspects of testing—such as lifecycle processes, techniques, infrastructure, and organization—are addressed.

TMMi is not limited to specific development methods or organizational sizes; it is lifecycle-independent and can be used effectively with various development approaches, making it widely applicable in both small and large organizations.

TMMi References:

TMMi covers all test levels, including both static testing (such as reviews) and dynamic testing at multiple stages, and is applicable across different software development lifecycles​​.

For a formal TMMi assessment, both staff interviews and document study are required to collect sufficient evidence. The assessment must adhere to the TMMi Assessment Method Accreditation Requirements (TAMAR), which state that formal assessments require the corroboration of interview data with documentary evidence (artifacts). These can include documents, templates, or screenshots, ensuring that the evaluation is robust, repeatable, and auditable​​.

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 process area Advanced Reviews belongs to TMMi Level 4 (Measured). At this maturity level, the focus is on quantitatively measuring and managing product quality, and advanced review techniques are employed to integrate peer reviews (static testing) with dynamic testing. These advanced reviews play a key role in ensuring that product quality is assessed early in the lifecycle and that testing is driven by measurable goals.

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​​.

When implementing the Test Policy and Strategy process area in TMMi, one of the specific goals you would be targeting is to Establish Test Performance Indicators. These indicators are essential for measuring the effectiveness of testing processes and for assessing whether the organization's testing goals, as defined by the test policy, are being met.

Other goals, such as performing product risk assessments or establishing a test organization, are related to different process areas in the TMMi model.

TMMi References:

The Test Policy and Strategy process area in TMMi includes the specific goal of establishing Test Performance Indicators to measure and track testing performance​​.

In the Test Design and Execution process area of TMMi Level 2, there are four specific goals. The relevant goals for this question are SG 2 (Perform Test Implementation) and SG 3 (Perform Test Execution):

SG 2 Perform Test Implementation includes practices such as developing and prioritising test procedures and creating specific test data. Therefore, the specific practice that aligns with this goal is "Create specific test data" (III).

SG 3 Perform Test Execution involves executing the tests and logging the outcomes. One of the specific practices here is "Write test log" (II), which documents the execution data in a structured manner.

Thus, the correct pair is SG 2 with III (Create specific test data) and SG 3 with II (Write test log)​​.

To improve the management and control of test environments, one of the specific practices under SG 3 (Manage and Control Test Environments) of the Test Environment process area is to coordinate the availability and usage of test environments. This involves managing reservations, scheduling, and ensuring the efficient use of test environments across different projects. This practice is essential for ensuring that the test environments are available when needed, reducing delays, and improving the overall efficiency of the testing process.

The TMMi process area Test Planning is indeed supported by several CMMI process areas, including Project Planning, Requirements Management, and Risk Management. These CMMI areas provide foundational support for ensuring that the test planning process incorporates adequate project management, requirement traceability, and risk identification, all of which are critical for effective testing.

Specific Goal 2 of the CMMI Validation process area relates to validation activities, not peer reviews, and therefore does not support the TMMi Peer Reviews process area.

Causal Analysis and Resolution is linked to Defect Prevention in TMMi, not Quality Control.

Performance Management does not directly support the Non-Functional Testing process area in TMMi.

TMMi References:

The TMMi Test Planning process area is supported by relevant CMMI process areas, such as Project Planning, which helps in aligning project goals with test planning activities​​.

This statement is FALSE because in Agile environments, a centralized process improvement project may not align with the decentralized, self-organizing nature of Agile teams. Agile emphasizes local, team-driven improvements rather than a top-down, centralized approach. Continuous, local improvements within Agile teams are more suitable than attempting to manage improvements across the organization in a centralized manner, which is more characteristic of traditional environments.

TMMi References:

In Agile contexts, improvement actions are typically implemented locally within teams rather than through a centralized project, aligning with Agile's principles of team autonomy​​.

In the Acting phase of the IDEAL improvement model, the focus is on implementing the changes that were identified and planned in the earlier phases. The two main activities in this phase are Create Solution and Implement Solution. This phase generally consumes the most effort, as creating and deploying solutions to improve the processes are resource-intensive activities. These activities align with option D, making it the correct answer .

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.

This statement is FALSE because TMMi is flexible and does not require the imposition of a predefined set of practices in Agile organizations. Instead, it encourages the adaptation of practices to fit the Agile context. TMMi allows for alternative practices that achieve the same goals as the expected practices, making it possible to integrate testing improvements in a way that aligns with Agile principles. The focus is on continuous improvement, not compliance with rigid practices.

TMMi References:

TMMi emphasizes flexibility in adapting practices, particularly in Agile environments where imposed processes would contradict Agile values of adaptability and continuous improvement​​.

During the Diagnosing phase of a test improvement cycle, in addition to conducting an assessment to determine the current maturity status, the activity of developing recommendations is also performed. These recommendations provide guidance on what actions should be taken to achieve the desired improvements. The assessment helps establish the organisation's current state, and the recommendations serve as a roadmap for moving forward.

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.

A specific practice is an expected component of the TMMi model. Expected components describe what an organisation will typically implement to achieve required components, such as specific and generic goals. Specific practices are activities that are crucial for achieving the specific goals of a process area, and they are evaluated during assessments to determine whether the goals have been met.

Peer Reviews is NOT a TMMi Level 2 process area. Peer Reviews is a process area at TMMi Level 3. At Level 3, organizations formalize their testing processes, including peer reviews, which involve static testing activities like inspections and walkthroughs to identify defects early.

Test Policy and Strategy, Test Monitoring and Control, and Test Environment are all process areas at TMMi Level 2.

TMMi References:

Peer Reviews are introduced at TMMi Level 3, whereas Test Policy and Strategy, Test Monitoring and Control, and Test Environment are process areas at Level 2​​.

In an Agile context, testing is often a shared responsibility among team members. This means that improvement ideas related to testing can come from any team member, not just dedicated testers. Agile encourages cross-functional collaboration, and because of the continuous feedback loops, all team members contribute to the refinement of both development and testing processes. This distributed responsibility fosters a more dynamic environment for test process improvements, where insights are drawn from diverse team roles.

Required components describe what an organization must comply with to satisfy a process area in the TMMi model. These components include specific goals and generic goals, and they form the basis for determining whether a process area has been successfully implemented during assessments. Expected components provide guidance on how to achieve the required goals, but they are not mandatory.

TMMi References:

TMMi defines required components as those that organizations must achieve to satisfy a process area​​.

The three TMMi Level 5 process areas are as follows:

Defect Prevention (A): The key specific goal here is to determine common causes of defects. This process involves analysing defect patterns and establishing actions to prevent similar defects in the future.

Quality Control (B): This area focuses on evaluating new testing technologies to determine their impact on the testing process. Statistical methods help predict product quality, and these evaluations drive improvements in the test process.

Test Process Optimization (C): The goal here is to establish a statistically controlled test process, where baselines are set, and improvements are implemented in an orderly manner​​​.

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​​.

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.

Expected components in the TMMi model guide organisations on how to implement improvements or conduct assessments. These components, such as Specific Practices and Generic Practices, are necessary for satisfying goals. Expected components must be implemented, either as described or through acceptable alternatives, for an organisation to achieve compliance with the model and reach maturity in test processes.

The debugging-oriented phase of the evolutionary testing model aligns closely with TMMi Level 1 (Initial). At TMMi Level 1, testing is often chaotic and is not formally separated from debugging. The primary focus is on finding and fixing bugs, which reflects the characteristics of the debugging-oriented phase described in the Gelperin and Hetzel evolutionary testing model. Testing at this level lacks structure and is mainly an ad hoc activity aimed at removing defects from the software.

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.

One of the key differences between informal and formal assessments is that informal assessments are not as rigorous. Informal assessments are more flexible, quicker, and less costly; however, they do not provide the same level of detail or accuracy as formal assessments. The statement that "informal assessments provide a result just as accurate as with a formal assessment" is therefore false. Formal assessments involve multiple types of evidence and a more thorough evaluation, while informal assessments typically rely on fewer types of evidence (often only interviews)​​.