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

In the Learning phase of the IDEAL model, one of the critical activities is "Analyse and Validate". This involves reviewing the entire improvement process to determine whether the intended goals were achieved and identifying what worked well and what could be improved. The objective is to learn from the experience to enhance future improvement initiatives and continually refine the ability to implement change​​.

The specific practice "Define a coordinated approach that coordinates both static and dynamic testing" is part of the Advanced Reviews process area at TMMi Level 4. The goal of this process area is to integrate static and dynamic testing, particularly through peer reviews, which helps optimise both defect detection and product quality management throughout the lifecycle​​​.

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

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

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

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.

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

The statement that Specific Goal 1 of the Test Measurement (4.1) process area covers the communication of test measurement results after analysis is FALSE. Specific Goal 1 focuses on aligning test measurement and analysis activities, which involves setting measurement objectives, specifying the measures to be taken, and establishing procedures for data collection, storage, and analysis. However, the communication of results comes under Specific Goal 2, which deals with the analysis and reporting of test measurement results.

TMMi References:

Test Measurement at TMMi Level 4 includes defining measures, data collection, and storage as part of aligning test measurement and analysis activities, while communicating results is part of a different goal​​.

In the Acting phase of the IDEAL model, the focus is on the implementation of the proposed solutions. Activities such as refining the solution and implementing the solution are key components of this phase. These actions are based on the plan developed in the earlier phases, and they are designed to apply the solutions to achieve the desired improvements. Specifically:

Refine solutions (i) refers to improving or adjusting the solution based on feedback from pilots or initial tests.

Implement Solution (iii) refers to the full implementation of the refined solution across the test process or organisation​​.

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

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

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.

Defect Prevention is a TMMi Level 5 process area. This process area focuses on identifying the root causes of defects and implementing preventive measures to avoid their recurrence. At TMMi Level 5, the goal is to optimize processes and move from defect detection to defect prevention.

Advanced Reviews and Test Measurement are Level 4 process areas, while Organizational Innovation and Deployment is part of CMMI, not TMMi.

TMMi References:

Defect Prevention is a key process area in TMMi Level 5, focusing on continuous process improvement and defect avoidance​​.

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.

In the scenario described, testing is performed ad hoc by business analysts who do not have defined test roles or a structured career path within the organisation. The process area that needs attention here is Test Organization (TMMi Level 3). This process area is crucial for establishing a structured test group with dedicated roles and responsibilities for testing, rather than relying on business analysts for testing as a secondary task.

The Test Organization process area focuses on establishing a formalised test organisation within the company, defining test functions and responsibilities, and promoting testing as a recognised profession with defined career paths. This would address the shortcomings of the current setup by creating a dedicated, skilled testing team, thus improving the consistency and quality of testing activities within the bank​​.

At TMMi Level 5, the Quality Control process area becomes relevant as it focuses on statistically managing and controlling the test process. Since the organisation is already at TMMi Level 4, moving to Level 5 involves ensuring that the test process is fully predictable, measured, and statistically controlled. Quality Control is a key process area in achieving TMMi Level 5 compliance, alongside other areas such as Defect Prevention and Test Process Optimization.

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 for more rigorous and thorough documentation is not in 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​.

As part of the Product Quality Evaluation process area (4.2), the specific goal "Project Goals for Product Quality and their Priorities are Established" includes the practice of identifying product quality needs. This involves understanding and defining what quality means for the product, determining quality characteristics (such as reliability, usability, etc.), and establishing priorities for these characteristics based on project goals.

Other practices such as establishing test process measures and measuring product quality quantitatively come later in the lifecycle or are part of other specific goals.

TMMi References:

In Product Quality Evaluation at TMMi Level 4, identifying product quality needs is critical for setting up measurable and prioritized goals for product quality​​.

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

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.

This statement is FALSE because TMMi does not focus only on higher test levels like system and acceptance testing. In fact, TMMi covers all 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 both systems and software engineering. Furthermore, TMMi addresses the four cornerstones of structured testing: lifecycle, techniques, infrastructure, and organization. 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 covers all test levels including 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​.

In a staged model like TMMi, an organisation follows a predefined improvement path that includes a set of process areas organised by maturity levels. Each level builds upon the previous one, and the organisation progresses in a step-by-step manner through these maturity levels to improve its processes. The staged model is well-structured and prescriptive, offering a clear improvement roadmap for the organisation.

The communication skills of testers is least likely to be improved using the TMMi model. While TMMi focuses on improving structured test processes, including static testing (such as reviews), unit testing, integration testing, and the management of test environments, it does not explicitly address the soft skills, such as communication, that testers may need to effectively interact with stakeholders. These skills are typically developed through other training or team-building initiatives, not through process improvements outlined by TMMi.

The assessment described, where only interviews are used to collect evidence, aligns with an informal TMMi assessment. Informal assessments are more flexible and do not require documentary evidence to corroborate interview data. They provide an indicative view of the organisation’s maturity but do not result in a formal maturity rating or certification​​.

Both Test Organization and Test Training Program are process areas associated with TMMi Level 3 (Defined). At this level, the organisation establishes a formal test organisation and ensures that there is a dedicated test training program. This helps to institutionalise testing as a profession and ensures the systematic development of skills needed for testing activities across the organisation.

The specific practice "Maintain horizontal traceability with requirements" is part of the Test Design and Execution process area in TMMi. This process area ensures that there is traceability between test conditions, test cases, and requirements to ensure comprehensive test coverage. Horizontal traceability guarantees that test cases can be traced back to the specific requirements they are intended to verify, which is critical for managing and ensuring the quality of the testing process.

TMMi References:

The Test Design and Execution process area includes practices that ensure test artifacts are traceable to requirements, supporting effective test coverage​​.

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

This statement is related to a defined process (Generic Goal 3), not a managed process (Generic Goal 2). A managed process (GG2) refers to processes that are planned, executed in accordance with policy, involve relevant stakeholders, are monitored and controlled, and are reviewed for adherence. Tailoring from the organisation's set of standard processes applies to a defined process, which is established under GG3.

The absence of a master test plan spanning multiple test levels points to a weakness in the Test Lifecycle and Integration process area, which is a TMMi Level 3 process area. This process area focuses on ensuring that testing is integrated throughout the development lifecycle and includes the development of comprehensive test plans (including master test plans) that cover multiple test levels and align with the overall testing strategy.

TMMi References:

The Test Lifecycle and Integration process area at TMMi Level 3 addresses the need for comprehensive and integrated test planning across all test levels​​.

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.