TMMi-P_Syll2020 Practice Exam Questions with Answers TMMi - Test Maturity Model Integration Professional Certification

TheDebugging-oriented phasefrom Gelperin and Hetzel's evolutionary testing model is associated withMaturity Level 1 "Initial"of TMMi. At this maturity level, testing is not yet a distinct and well-defined process but is often interleaved with debugging. Organizations at this level have chaotic and ad-hoc testing activities, with no separation between testing and debugging.

Maturity Level 1organizations lack formal processes, and testing is often reactive, performed alongside fixing bugs in the code. This is in line with the debugging-oriented phase, where testing and debugging are seen as part of the same activity.

TMMi References:

TheTMMi frameworkdraws directly from the evolutionary model of Gelperin and Hetzel, associating theDebugging-oriented phasewith Level 1, which describes a chaotic, unmanaged testing environment??.

At TMMi Level 4, the scope includes process areas likeTest Process Optimization,Product Quality Evaluation, andAdvanced Reviews. However,Test Lifecycle and Integrationis 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??.

This statement isFALSEbecause in Agile environments, acentralized process improvement projectmay 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??.

TheTesting quadrantsmodel 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.

CMMI and TMMi complement each other in many ways. While CMMI focuses on improving broader software development processes,TMMispecifically addresses testing. Implementing CMMI provides value to test organizationsby enabling a structured and continuous improvement approach that can incorporate TMMi as part of the overall process.

CMMI’s continuous representation allows organizations to implement specific process areas related to testing (like verification and validation) and integrate TMMi practices forcontinuous improvementin their testing processes. Organizations followingTMMimay also refer to CMMI practices for complementary process improvements in areas such as configuration management, planning, and performance measurement.

TMMi References:

TMMi outlines how CMMI’s process areas, such asVerification and Validation, provide critical value for testing organizations??.

CMMI’s structure supports continuous process improvement that aligns well with TMMi’s structured approach to test process maturity?.

At TMMi Level 3,Test Lifecycle and Integrationbuilds on the practices ofTest Planningintroduced at TMMi Level 2. This process area focuses on establishing a standardised test lifecycle, integrating the test process with the development lifecycle, and coordinating the testing effort across multiple levels. It also includes creating amaster test planthat builds upon the risk assessments, test estimates, and approaches defined at Level 2 during Test Planning.

By further refining these practices and introducing lifecycle integration,Test Lifecycle and Integrationensures that the testing processes are consistent, well-defined, and fully embedded into the overall project lifecycle??.

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 specific practice "Testers review test basis documents" belongs to thePeer Reviewsprocess 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.

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.

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 statement thatSpecific Goal 1of theTest Measurement (4.1)process area covers the communication of test measurement results after analysis isFALSE. Specific Goal 1 focuses on aligningtest 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 underSpecific Goal 2, which deals with the analysis and reporting of test measurement results.

TMMi References:

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

Peer ReviewsisNOTaTMMi Level 2process area. Peer Reviews is a process area atTMMi 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, andTest Environmentare all process areas atTMMi Level 2.

TMMi References:

Peer Reviews are introduced atTMMi Level 3, whereasTest Policy and Strategy,Test Monitoring and Control, andTest Environmentare process areas at Level 2??.

Test Process Optimizationis the TMMi Level 5 process area specifically aimed at identifying new testing technologies and transitioning them into the organisation. This process area focuses on continuously improving the test process by evaluating and adopting new tools, methods, and technologies that can enhance testing efficiency and effectiveness. Test Process Optimization encourages organisations to stay ahead of industry developments and integrate innovative testing practices.

In theLearning phaseof 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??.

Agile organisations often focus on rapid iterations and minimal documentation, which can lead to the omission or underuse of structured testing practices.TMMiserves as a valuable guide for Agile teams by highlightingcritical testing practicesthat 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.

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

The correct order of TMMi maturity levels fromlow to highis:

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 ofManaged (Level 2),Defined (Level 3), andMeasured (Level 4)??.

In theInitiating phaseof a test improvement cycle, one of the key activities is toCharter Infrastructure. This activity involves setting up the structure needed to support the improvement effort, such as establishing a project board and defining responsibilities. This phase focuses on creating the foundational support for the test improvement initiative.

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 Agile environments, TMMi is often used to complement the Agile methodology by providing structured guidance on critical testing practices that may be overlooked. While Agile focuses on flexibility and responsiveness, TMMi can remind organisations of essential practices that ensure thorough testing, such as formal reviews or defect management. The TMMi framework does not impose strict processes but offers structured support for critical test process improvements that align with Agile principles.

Defect Preventionis aTMMi Level 5process 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 ReviewsandTest Measurementare Level 4 process areas, whileOrganizational Innovation and Deploymentis part of CMMI, not TMMi.

TMMi References:

Defect Preventionis a key process area inTMMi Level 5, focusing on continuous process improvement and defect avoidance??.

During theDiagnosing phaseof 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.

TheDiagnosing phasein 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 isDevelop 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 .

A key business reason for initiating a test improvement programme is to improve product reliability, which is directly related to the quality of the final product delivered to customers. Enhancing reliability through systematic testing can lead to fewer defects, higher customer satisfaction, and reduced costs associated with fixing issues post-release. This is often a priority in organisations where product quality and reliability are critical success factors, such as in industries like healthcare, automotive, or aviation.

The TMMi framework recognises that a focus on improving product quality, including reliability, is one of the major drivers for test process improvements. Testing processes that evolve and improve reliability provide value by reducing the risk of defects and ensuring that the software meets the defined quality criteria.

As part of theProduct Quality Evaluationprocess area (4.2), the specific goal"Project Goals for Product Quality and their Priorities are Established"includes the practice ofidentifying 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 asestablishing test process measuresandmeasuring product quality quantitativelycome later in the lifecycle or are part of other specific goals.

TMMi References:

InProduct Quality EvaluationatTMMi Level 4, identifying product quality needs is critical for setting up measurable and prioritized goals for product quality??.

The process areaAdvanced Reviewsbelongs 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 statement thatall defects should be analyzedto prevent as many defects as possible isFALSE. In theDefect Preventionprocess area atTMMi Level 5, only asubset of defects—those that are recurring or considered to be of significant impact—are analyzed. Analyzing all defects would be inefficient and not always necessary. Instead, a targeted approach is used to identifycommon causesof defects and implement actions to prevent their recurrence.

TMMi References:

TheDefect Preventionprocess area is based on the analysis of a subset of defects to find and eliminate common causes??.

TheTMMi process area Test Planningis indeed supported by severalCMMI process areas, includingProject Planning,Requirements Management, andRisk 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 arearelates to validation activities, not peer reviews, and therefore does not support the TMMi Peer Reviews process area.

Causal Analysis and Resolutionis linked toDefect Preventionin TMMi, not Quality Control.

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

TMMi References:

TheTMMi Test Planningprocess area is supported by relevant CMMI process areas, such asProject Planning, which helps in aligning project goals with test planning activities??.