TMMi-P_Syll2020 Sample Questions Answers

To improve the quality of test cases and reduce defects in production, addressing the practice of "Identify and Prioritize Test Conditions" under Specific Goal 1 (SG 1) of the Test Design and Execution process area is essential. This specific practice involves identifying conditions based on an analysis of the test items and prioritising them based on risk and other factors. By improving the identification and prioritisation of test conditions, organisations can ensure that they focus on the most critical aspects of the system, thereby increasing the effectiveness of their testing efforts and reducing defects in production.

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.

The specific goals of theAdvanced Reviewsprocess area include:

Coordinate the peer review approach with the dynamic test approach: Ensuring that static testing, such as peer reviews, is aligned with the dynamic testing approach to optimize testing efforts.

Adjust the test approach based on review results early in the life cycle: This goal aims to improve the test approach by using early feedback from reviews to make adjustments that can enhance testing later in the lifecycle.

The other options (2, 4, and 5) refer to different process areas or goals. For example,Perform peer reviewsis part of thePeer Reviewsprocess area at TMMi Level 3, not Advanced Reviews.

TMMi References:

TheAdvanced Reviewsprocess area at TMMi Level 4 focuses on aligning peer reviews with the dynamic test approach and adjusting the test approach based on review results​​.

Planning pokeris an Agile technique commonly used to estimate effort, and it can be adapted for use in theTest Planningprocess 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​.

CMMI version 2 recognises the importance of testing in software development and includes two dedicated practice areas:VerificationandValidation. These areas specifically addressthe processes required to ensure that a system or component meets its specified requirements and that the final product is fit for its intended use. While CMMI does not provide a testing-specific maturity model, these practice areas contribute to the overall quality management framework, and organisations adopting CMMI can leverage these processes to improve their testing practices. The TMMi framework complements CMMI by providing more detailed guidelines for testing.

The specific practice "Define a coordinated approach that coordinates both static and dynamic testing" is part of theAdvanced Reviewsprocess 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​​​.

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

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.

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

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​

TheAdvanced Reviewsprocess area, which is part ofTMMi Level 4, is concerned with measuring product quality early in the lifecycle. It aims to enhance thetest strategyandtest approachby aligningstatic testing(reviews and inspections) withdynamic 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 Reviewsat TMMi Level 4 focuses on integrating static and dynamic testing approaches to optimize test strategy and product quality evaluation​​.

In an Agile context, some practices from TMMi levels 4 and 5 might be considered less relevant or adjusted to fit the Agile methodology. Specifically, at TMMi level 5, testing with statistical methods may indeed be less relevant. In Agile projects, operational profiles or usage models, which are essential to perform statistically valid testing, are often not utilised. Agile methodologies focus more on incremental development and continuous feedback loops, which do not typically rely on statistical sampling methods. Therefore, the statement that "Agile projects normally do not use operational profiles or usage models of a product on which to base statistically valid inferences to help create a representative sample of tests, thus the TMMi level 5 specific goal 'Testing is performed using Statistical Methods' is considered not relevant in an Agile context" is true​.

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

This statement is false because the CMMI does not have defined levels specifically for testing maturity. The CMMI model is more general and focuseson 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.

This statement is related to adefined process(Generic Goal 3), not amanaged process(Generic Goal 2). A managed process (GG2) refers to processes that are planned, executed inaccordance 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.

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.

Aspecific practiceis 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.

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.

In the TMMi framework, aSpecific Goalis unique to a particular process area and represents the essential outcomes that must be achieved for that process area. In contrast, aGeneric Goalapplies across multiple process areas and ensures that the processes are institutionalised, managed, and aligned with broader organisational objectives. Generic Goals help maintain consistency and effectiveness of processes across the organisation, while Specific Goals focus on the particular needs of an individual process area.

The specific goals of theTest Process Optimizationprocess area atTMMi Level 5include:

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 asTest Measurementor earlier maturity levels.

TMMi References:

The goals forTest Process OptimizationatTMMi Level 5focus on selecting and deploying process improvements and evaluating new technologies​​.

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.

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

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.

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

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

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

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.

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 isPlanning, Preparation, Interview, Reportingwhich matchesoption B (2, 3, 1, 4).