Pass the iSQI TMMi TMMi-P_Syll2020 Questions and answers with ValidTests

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

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.

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

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.

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

The process areaNon-functional Testingat 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 specificnon-functional test planisnotexplicitly 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) isnota specific goal of the Non-functional Testing process area​​.

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

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 formore rigorous and thorough documentationisnotin 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​.

The specific goal "Coordinate the Peer Review Approach with the Dynamic Test Approach" belongs to the process areaAdvanced Reviewsat TMMi Level 4. This process area builds on the Peer Reviews process area introduced at TMMi Level 3 and aims to fully integrate static and dynamic testing processes. It ensures that peer reviews (static testing) are coordinated with the dynamic test approach, ensuring consistency between the two methods and optimising product quality measurement early in the lifecycle​​.

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