Free TMMI-P_SYLL2-2 Practice Test Questions and Answers (2026)

In the TMMi (Test Maturity Model integration) framework, Test Organization is a Level 3 Process Area aimed at establishing an organized test infrastructure. It addresses organizational aspects necessary to build structured testing capabilities across an organization. Specifically, Test Organization contains specific goals to establish formal test functions for test specialists (SG 2) and to establish clear test career paths (SG 3). These goals address organizational roles, career development, skills, and responsibilities, ensuring that software testing is performed by designated, qualified professional testers. By defining test functions and structured career paths, organizations elevate test professionalism and address resource shortcomings, which directly aligns with the assessor's recommendation described in the scenario.

A. Test Training Program focuses on developing test skills through training plans and course execution, not defining career paths or organizational test functions.
B. Test Policy and Strategy defines overarching testing objectives and generic test strategies at Level 2, rather than operational test roles and career structures.
D. Test Planning addresses project-specific planning, risk assessment, and resource allocation for a project, not organizational career paths or defining test specialist functions.

TMMi Foundation. (2012). Test Maturity Model integration (TMMi) Guidelines for Test Process Improvement Release 1.2, Section 4.1 "PA 3.1 Test Organization", Specific Goals SG 2 & SG 3, pp. 101–115. Document Ref: TMMi.Model.V1.2.

TMMi Foundation. (2018). TMMi Professional Syllabus Release 2.1, Section 3.1 "TMMi Level 3: Defined", Learning Action 3.1.1, p. 22.

In the TMMi Framework, "Testers review test basis documents" is Specific Practice SP 2.2. It sits under Specific Goal SG 2, "Perform Peer Reviews", in the Level 3 (Defined) process area Peer Reviews (PA 3.5). Peer Reviews makes testers part of the static testing process. Testers review requirements and design documents early, which finds defects before they spread and checks that the documents can be tested. Other practices in this process area include: identifying work products for review defining peer review criteria conducting peer reviews analysing peer review data Early review of the test basis is a core part of TMMi's static testing practices. That is why this practice belongs to Peer Reviews rather than to the planning or dynamic test process areas.

A. Test Planning: This Level 2 process area covers product risk assessment, test approach, estimates and the test plan. It does not include reviewing test basis documents.
B. Test Design and Execution: This Level 2 process area covers test analysis, design, implementation, execution and incident management. It concerns dynamic testing, not static review of the test basis.
D. Advanced Reviews: This Level 4 process area builds on Peer Reviews. It aligns static and dynamic testing and measures product quality early. The basic tester review practice lives in Level 3.

TMMi Foundation, Test Maturity Model integration (TMMi) Framework, Release 1.0/1.2. Level 3 "Defined", Process Area 3.5 "Peer Reviews", SG 2 "Perform Peer Reviews", SP 2.2 "Testers review test basis documents". https://www.tmmi.org

TMMi Foundation, TMMi Framework, Level 4 "Measured", Process Area 4.3 "Advanced Reviews", Introduction and Scope sections. These distinguish it from Peer Reviews.

TMMi Foundation, TMMi Framework, Level 2 "Managed", PA 2.3 "Test Planning" and PA 2.4 "Test Design and Execution", Specific Goals and Practices tables.

van Veenendaal, E. & Wells, B., Test Maturity Model integration (TMMi): Guidelines for Test Process Improvement, UTN Publishers, 2012. Chapter on TMMi Level 3, "Peer Reviews".

iSQI / TMMi Foundation, TMMi Professional (TMMi-P) Syllabus. Section on TMMi structure, process areas and their specific goals and practices.

Note: Page numbers differ between framework releases, so I have given section and practice identifiers (PA 3.5, SG 2, SP 2.2) for checking.

In TMMi Maturity Level 4, Process Area 4.1 Test Measurement is divided into specific goals to align and execute measurement activities. Specific Goal 1, "Align Test Measurement and Analysis Activities", establishes the framework for measurement and contains four specific practices: SP 1.1 Establish test measurement objectives, SP 1.2 Specify test measures, SP 1.3 Specify data collection and storage procedures, and SP 1.4 Specify analysis procedures. Communicating test measurement results after analysis is addressed under Specific Goal 2, "Provide Measurement Results", specifically SP 2.4 "Communicate test measurement results". Therefore, statement C is false regarding SG 1, making it the correct option to select.

Option A is incorrect because establishing test measurement objectives is a true component of SG 1, specifically practice SP 1.1.
Option B is incorrect because specifying test measures is a true component of SG 1, specifically practice SP 1.2.
Option D is incorrect because specifying data collection, storage, and analysis procedures are true components of SG 1 (SP 1.3 and SP 1.4).

TMMi Foundation. TMMi Framework Version 1.2, Process Area PA 4.1 Test Measurement, SG 1 & SG 2, pages 166-173.

TMMi Foundation. TMMi Professional Syllabus Version 2.1, Module 5: Level 4 Measured, Section 5.1 Test Measurement, page 30.

In the Test Maturity Model integration (TMMi) framework, process areas are categorized into maturity levels ranging from Level 2 (Managed) to Level 5 (Optimization). TMMi Level 3, termed 'Defined', focuses on establishing organizational testing standards and integrating testing into the software development lifecycle. The process areas at TMMi Level 3 include Test Organization, Test Training Program, Test Lifecycle and Integration, Non-Functional Testing, and Advanced Reviews. Advanced Reviews expands upon basic peer reviews by integrating static testing practices fully into the test lifecycle and using formal review techniques across all early work products. Consequently, Advanced Reviews is a core process area belonging explicitly to TMMi Maturity Level 3.

Option A: TMMi Level 2 (Managed) comprises Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, and Test Environment, not Advanced Reviews.
Option C: TMMi Level 4 (Measured) consists of Test Measurement, Quality Evaluation, and Advanced Reviews is not included here; Level 4 addresses quantitative process management.
Option D: TMMi Level 5 (Optimization) focuses on Defect Prevention, Quality Control, and Test Process Optimization, representing continuous improvement rather than static review practices.

TMMi Foundation, "Test Maturity Model integration (TMMi) Framework Version 1.2", Section 2.3 "TMMi Maturity Levels", pp. 15–18.

TMMi Foundation, "TMMi Framework Version 1.2", Chapter 4.5 "PA 3.5 Advanced Reviews", pp. 115–125.

van Veenendaal, E. (2012), "The Testing Maturity Model integration", UTN Publishers, Chapter 5: Level 3 Process Areas, pp. 85–92.

In process improvement frameworks like TMMi and CMMI, architecture can be staged or continuous. A staged representation uses a predefined set of process areas organized into maturity levels (from Level 1 to Level 5) to establish a structured, proven path for test process improvement across an entire organization. Each maturity level builds a foundation for the next level. In contrast, a continuous representation allows organizations to selectively choose individual process areas or capability levels to align directly with specific business goals without adhering to a strict level order. Therefore, statement B accurately defines the fundamental nature and structure of a staged improvement model like TMMi.

A: Selecting individual process areas based on business objectives describes the continuous representation, whereas staged models require addressing process areas within predefined maturity levels. C: A staged representation explicitly defines a fixed set of maturity levels (Levels 1 through 5) through which an organization must sequentially progress. D: Staged representations are generally considered easier to follow and implement than continuous models because they provide a clear, predefined roadmap rather than open-ended flexibility.

TMMi Foundation, "TMMi Framework Document Version 1.3", Section 1.3 "Staged Architecture", pp. 11-12.

TMMi Foundation, "TMMi Professional Syllabus", Version 2.1, Section 1.1 "Context of Test Process Improvement", p. 11.

In an Agile environment, test process improvement aligns strictly with the Agile Manifesto value of preferring working software over comprehensive documentation. Test process improvers should promote lightweight, lean, and value-adding documentation rather than advocating for more rigorous, thorough, or heavy documentation. Unnecessary documentation overhead creates friction and slows down iteration cycles. The TMMi guidelines for Agile contexts specifically recommend streamlining artifacts—such as consolidating test policy, strategy, and high-level planning into concise single documents, providing active coaching and mentoring during deployment, and adapting TMMi assessments to focus more heavily on team interviews and live product demonstrations rather than static paper-based artifact reviews. Therefore, Option A represents an untrue statement.

Option B: This statement is true; TMMi in Agile permits consolidating policy, strategy, and plan into a concise combined document.
Option C: This statement is true; deployment of lightweight Agile test processes requires hands-on mentoring and coaching support.
Option D: This statement is true; TMMi assessors rely more on interviews and live evidence in Agile due to reduced formal documentation.

TMMi Foundation, "TMMi in an Agile Context," Guidelines Doc Ref: TMMi-Agile-V1.1, Section 4: Documenting and Assessing in Agile, pp. 15–22, 2017.

TMMi Foundation, "TMMi Professional Syllabus," Section 1.4: TMMi and Agile Context, Version 2.1, 2020.

In an Agile context, a "SCRUM team" (B) represents a typical format where cross-functional members collaborate on testing as part of the development process. This aligns with TMMi requirements for an agile test organization structure.

A. A Test Centre of Excellence often exists in more traditional environments, not specifically Agile.
C. Test guilds are informal and not a typical organisational structure under TMMi in Agile.
D. Test Process Group usually relates to traditional project management frameworks rather than Agile.

TMMi Foundation. (2018). TMMi Assessment Model, 1.0. (pp. 33-35)

Highsmith, J. (2009). Agile Project Management: Creating Innovative Products. (pp. 75-77).

Scrum Alliance. (2021). The Scrum Guide. (Section on Scrum Teams).

Cohn, M. (2004). User Stories Applied: For Agile Software Development. (Chapter on Agile Teams).

Fowler, M. (2004). The New Methodology. (pp. 15-16).

In the TMMi framework, specifically under the Test Planning process area at TMMi Level 2, Specific Goal 3 (SG 3) focuses on establishing test estimates. When applying TMMi in an Agile context, Planning Poker is a widely recognized collaborative, consensus-based Agile estimation technique used to estimate effort or relative size of user stories and associated testing tasks. By utilizing story points or ideal hours during Planning Poker sessions, Agile teams effectively fulfill the requirements of SG 3 to establish realistic test estimates based on shared understanding and historical velocity.

A. Risk poker is a technique used specifically for risk identification and prioritization, not for establishing effort or cost test estimates.
C. Iteration planning is a broader event/activity where tasks are scheduled for a sprint, rather than an estimation technique itself.
D. Exploratory testing is a dynamic test execution technique focused on simultaneous learning, test design, and test execution, not an estimation technique.

TMMi Foundation, TMMi Model Framework Release 1.2, Process Area 2.1 Test Planning, SG 3 "Establish Test Estimates", pp. 45-48.

TMMi Foundation, Guidelines for TMMi in an Agile Context, Section 3.2 "Test Planning in Agile", pp. 18-20.

ISQI, TMMi Professional Syllabus Version 2.1, Learning Objective TMMi-P_Syll2, Section 2.1.

The TMMi model and Agile development principles are complementary frameworks that together enhance software quality and test engineering efficiency. While Agile methodologies focus heavily on iterative delivery, collaboration, and rapid software evolution, they often leave formal testing processes implicit or inadequately detailed. Organizations utilizing TMMi benefit by applying the model as a comprehensive structural reference to identify and maintain critical testing practices—such as test policy definition, structured risk assessment, and non-functional testing alignment—that are easily overlooked or forgotten in fast-paced Agile environments. TMMi ensures that essential quality assurance practices are systematically sustained without undermining the flexibility, responsiveness, and team empowerment inherent to Agile software delivery workflows.

Option A: Agile emphasizes decentralized team-level retrospectives and self-organization rather than relying exclusively on a centralized organization-wide Test Process Group.
Option C: Agile values lean, lightweight processes and working software over overly detailed, heavy process definitions and extensive documentation.
Option D: TMMi integrates both team-level testing practices and organizational-level test governance; it does not advocate omitting organizational process areas.

TMMi Foundation, "TMMi in an Agile Context," Assessment and Practice Guidelines, Section 2: Combining TMMi and Agile, pp. 6–12, 2017.

TMMi Foundation, "TMMi Professional Syllabus," Section 1.4: TMMi and Agile, Version 2.1, pp. 14–16, 2020.

The TMMi Assessment Method Application Requirements (TAMAR) define two assessment types that differ in rigour, team leadership and data collection. An informal assessment can be led by an accredited TMMi assessor. Interviews are the minimum mandatory data-collection method, and document review is optional. Informal assessments are typically used for quick scans, gap analyses or monitoring improvement progress. They cannot produce a formal maturity rating. A formal assessment must be led by an accredited TMMi Lead Assessor. Evidence must be corroborated, so interviews must be supplemented by document study. Formal assessments can lead to official maturity ratings. The scenario combines an accredited assessor with interviews as the only evidence source. Both characteristics satisfy the informal requirements but not the formal ones.

B. Formal assessments require a Lead Assessor and corroborating documentary evidence. Interviews alone are insufficient under TAMAR.
C. Interview-only evidence collection does not meet formal assessment requirements, so the characteristics cannot apply to both types.
D. The characteristics fully comply with TAMAR's minimum requirements for an informal assessment.

TMMi Foundation, TMMi Assessment Method Application Requirements (TAMAR), Release 1.0/2.0. See the sections on assessment classes (formal vs. informal), assessment team requirements, and data collection requirements. https://www.tmmi.org

TMMi Foundation, TMMi Professional Syllabus (TMMi-P), Chapter 4 "TMMi Assessments," learning objectives on formal vs. informal assessments and TAMAR. https://www.tmmi.org

TMMi Foundation, Test Maturity Model integration (TMMi) Framework, Release 1.2/1.3. See the section "TMMi and Assessments" (overview chapter). https://www.tmmi.org

van Veenendaal, E. & Wells, B., Test Maturity Model integration (TMMi): Guidelines for Test Process Improvement, UTN Publishers, 2012, chapter on TMMi assessments (ISBN 978-94-90986-10-0).

Note: Section numbering varies between document releases. Verify exact page numbers against the release you are using.