Pass the iSQI TMMi certification TMMi-P_Syll2.1 Questions and answers with CertsForce

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

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.

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.

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.

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 process areas Test Organization and Test Life Cycle and Integration at TMMi Level 3 most strongly build on the practices and experiences of Test Planning from TMMi Level 2. Test Organization focuses on institutionalising the testing roles and responsibilities across the lifecycle, while Test Life Cycle and Integration ensures that testing is integrated throughout the development lifecycle, improving coordination and planning of test activities across different phases of the project.

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

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

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.