CTAL-TM — Advanced Test Manager (v3.0) glossary

162 terms the exam expects you to know, defined in plain language.

A

Action Item Tracking from Retrospectives(action items): The process of documenting and following up on improvement actions identified in retrospectives.
Active Listening(active listening): A communication skill involving full concentration on the speaker, understanding their message, thoughtful response, and retention of the discussion.
Agile Continuous Test Management(agile test management, continuous test management): A test management approach in Agile models where testing is continuous and integrated within each iteration, requiring adaptive planning.
Agile Test Reporting(agile project, daily stand-up dashboards): A reporting approach emphasizing daily stand-up dashboards and iteration-level summary reports.
Analogous Estimation(analogous estimation): An estimation technique based on historical data from similar items or projects.
Audience-Adapted Communication(adapting communication to the audience): The practice of tailoring message detail, terminology, and emphasis to the stakeholder's background and decision-making authority.

B

Balanced Scorecard Approach(balanced scorecard approach): A method for selecting a set of metrics covering quality, progress, risk, and satisfaction.
Baseline(baseline, baselines): A stable set of work products at a given point in time, such as after a test phase is completed.
Blameless Culture in Retrospectives(blameless culture): A safe, non-accusatory environment that encourages honest feedback and continuous learning.
Bottom-up Estimation(bottom-up estimation): A detailed estimation technique summing effort from individual task components.
Brainstorming(brainstorming): A collaborative technique to uncover risks by gathering cross-functional team ideas.
Building Bridges Between Teams(building bridges between teams): Efforts by the test manager to foster communication and cooperation between the test team and other groups.

C

Change Control(change control): A CM process that reviews, approves, and tracks modifications to test work products through defined change requests.
Checklists(checklists): A structured list of common risks based on past projects or standards to guide identification.
Communication Management for Test Managers(communication management): Establishing clear escalation paths and promoting open, transparent communication with stakeholders.
Configuration Audit(configuration audits): A verification that the actual state of test work products matches the documented state.
Configuration Management(configuration management, cm): A discipline applying technical and administrative direction to identify, control, record, and verify configuration items.
Configuration Management for Test Work Products(configuration management, cm): A discipline applying technical and administrative direction to identify, control, account for, and audit changes to test artifacts.
Conflict Management Techniques(managing conflict, conflict resolution techniques): Methods such as mediation, negotiation, and clear escalation paths used to resolve disputes and find win-win solutions.
Conflict Resolution in Testing Teams(conflict resolution): Constructive management of disagreements about quality, priorities, or resources within cross-functional teams.
Constructive Feedback(constructive feedback): Timely, specific, and respectful feedback given to encourage continuous improvement within the team.
Cost of Ownership(cost of ownership): The total cost of a test tool over its lifecycle, including license fees, training, maintenance, and productivity loss during transition.
Cross-Functional Collaboration in Testing(cross-functional collaboration): Cooperation between test teams and other groups to integrate testing throughout the software development lifecycle.

D

Defect Density(defect density): A metric measuring the number of defects per unit size of the software.
Defect Detection Percentage(defect detection percentage): A metric measuring the ratio of defects found during testing to total defects after release.
Difference Between Retrospective and Post-mortem(retrospective vs post-mortem): A retrospective is blameless and forward-looking, while a post-mortem often focuses on blame.
Difficult Conversations(difficult conversations): Conversations involving bad news or performance issues that require preparation, empathy, and a clear message.
Distractor Identification(distractor): Recognizing incorrect answer options in exam questions to avoid common misconceptions.
Distributed Team Challenges(distributed teams): Issues such as time zones, cultural differences, and communication barriers in managing geographically distributed teams.
Dynamic Risk Adjustment(dynamic approach): The ongoing process of adapting testing to address evolving risks throughout the project.

E

Entry Criteria(entry criteria): Measurable conditions that must be met before a test level can begin.
Estimates as Predictions(estimates are not commitments, estimates are predictions): The principle that estimates are not fixed commitments but predictions that should be updated as information changes.
Estimation Accuracy Improvement(historical data, improving estimation accuracy): The use of historical data and lessons learned to refine estimation models over time.
Estimation Depth(estimation depth): The granularity of effort estimation aligned with the risk level of a test item.
Exit Criteria(exit criteria): Measurable conditions that must be met to conclude a test level.
Expert Interviews(expert interviews): A technique leveraging experienced individuals to identify potential risks.
Expert Judgment(expert judgment): An estimation technique relying on experience of knowledgeable individuals.

F

Five Phases of Effective Retrospectives(five phases): A structured approach comprising set the stage, gather data, generate insights, decide what to do, and close.
Function Point Analysis(function point analysis, fpa): An estimation technique that estimates effort based on the functionality of the software.
Functional Configuration Audit(functional configuration audits, fca, functional configuration audit): A type of audit that checks whether a work product meets its functional requirements.

H

Historical Data Analysis(historical data analysis): Using data from similar past projects to identify recurring risk patterns.
Historical Data Analysis for Risk Identification(historical data analysis for risk identification): The proactive analysis of past project data to identify recurring risk patterns and inform test planning and estimation.
Historical Data in Estimation(historical data): Data from previous projects used to improve estimation accuracy and refine estimation models.

I

IEEE 829 Standard(ieee 829 standard): A standard template for test plan documentation, referenced in the ISTQB syllabus.
ISTQB Glossary(istqb glossary): Official source of definitions for terms like risk-based testing.
Identification of Test Work Products(identification): A CM activity that uniquely identifies each test work product using naming conventions, version numbers, and baseline labels.
Integrating Retrospectives into Test Process(regular activity): Making retrospectives a regular, ongoing activity rather than a one-time event for continuous improvement.
Iteration-Level Test Planning(iteration-level planning, iteration test planning): Test planning that occurs at the release and iteration levels in Agile models, with execution and monitoring in short cycles.

J

Joint Workshops for Testability(joint workshops): Collaborative sessions involving testers early in requirements and design to address testability concerns.
Just-in-time test documentation(just-in-time documentation): The practice of creating lightweight, minimal test documentation as needed, rather than exhaustive upfront documentation.

K

K-Levels(k-level, k-levels): Cognitive levels (K2, K3, K4) indicating the depth of learning objectives, requiring recall, application, or analysis.
Key Performance Indicators(kpis): Metrics like test case execution progress and defect discovery rate used for test monitoring.

L

Lessons Learned(lessons learned, retrospective): A retrospective meeting with stakeholders to identify successes and areas for improvement.
Lessons Learned Documentation: Recording insights from retrospectives to inform future test process improvements.
Lightweight Just-in-Time Documentation(lightweight documentation, just-in-time documentation): A documentation approach in iterative models where test documentation is lightweight and created just in time, not exhaustively upfront.

M

Metrics from Retrospectives: Quantitative data generated during retrospectives that feed into organizational process improvement.
Motivation Techniques(motivation techniques): Methods tailored to individual team members to foster motivation, as required by the ISTQB syllabus.

O

Optimism Bias(optimism bias): A cognitive bias where people tend to underestimate effort, especially for complex tasks.
Organizational Test Strategy(organizational strategy): A high-level document describing the testing approach applied across all projects within an organization.
Over-reliance on Automation(over-reliance on automation): A common pitfall where teams depend too heavily on automated testing at the expense of process improvement.

P

Phase-gate test management(phase-gate approach): A test management approach in sequential SDLC models with distinct phases and formal gates between them.
Phased Tool Implementation(phased approach, implementation phases): A step-by-step approach to tool deployment consisting of planning, installation, training, pilot, and rollout phases.
Physical Configuration Audit(physical configuration audits, pca, physical configuration audit): A type of audit that verifies a work product is complete and consistent.
Pilot Project for Tool Validation(pilot project): A small-scale trial deployment of a potential test tool to validate its suitability before full rollout.
Process Improvement(process improvement): The systematic use of lessons learned to enhance future testing processes.
Process Metrics(process metrics): Test metrics that measure characteristics of the test process, such as test execution rate and pass/fail ratio.
Product Metrics(product metrics): Test metrics that measure characteristics of the product, such as defect density and test coverage.
Product Risk(product risk, product risks): The risk that a software product may fail, analyzed by likelihood and impact.
Product Risks(product risks): Risks related to the product itself, such as complex functionality or new technology.
Project Risks(project risks): Risks related to project management, such as tight schedules or resource constraints.
Project Test Strategy(project strategy, project test strategy): A customized document derived from the organizational test strategy that defines testing for a specific project.
Psychological Safety in Retrospectives: The condition of feeling safe to share honest feedback without fear of negative consequences.

Q

Quality Attributes(quality attributes): Characteristics of software quality, such as reliability and usability, that stakeholders may prioritize in testing.

R

RACI Matrix(raci matrices): A responsibility assignment matrix that clarifies roles and responsibilities of stakeholders in testing activities.
Rationale Document(rationale document): An answer key document explaining why each correct answer is correct and why distractors are wrong.
Reporting Frequency(reporting frequency): The schedule at which test progress and results are communicated to stakeholders.
Requirements Coverage(requirements coverage): A metric showing the percentage of requirements covered by tests.
Residual Risk(residual risk, residual risks): The risk remaining after testing, which must be communicated and accepted by stakeholders.
Residual Risk Level(residual risk level): A metric representing the remaining risk after testing activities have been performed.
Retrospectives(retrospectives): Meetings held after a project to identify improvements for future projects.
Retrospectives in Test Process Improvement(retrospectives): A structured, blameless meeting that captures lessons learned to drive test process improvement.
Risk Analysis(risk analysis): The process of identifying and prioritizing risks to inform testing efforts.
Risk Assessment Update(risk assessment update): A report indicating which risks have been mitigated and which remain, with recommendations.
Risk Coverage(risk coverage): A metric indicating the extent to which identified risks are addressed by test activities.
Risk Identification(risk identification): The systematic process of discovering potential product and project risks.
Risk Level(risk level, risk level of each test item): A measure of likelihood and impact of failure for a product risk.
Risk Mitigation(risk mitigation): Actions taken to reduce the impact of identified risks on testing.
Risk Mitigation Through Testing(risk mitigation through testing): The process of reducing product risks by selecting test techniques and coverage levels based on risk level.
Risk Reassessment Frequency Variation by Development Model(risk reassessment frequency variation): The frequency of risk reassessment differs: continuous in Agile (e.g., every sprint) and periodic in sequential models (e.g., at phase gates).
Risk Register(risk register): A document that records all identified risks for later analysis and prioritization.
Risk Taxonomy(risk taxonomy): A classification system that groups risks into categories like functional, performance, and security.
Risk Tolerance(risk tolerance): The level of risk that a stakeholder is willing to accept in the testing process or product.
Risk analysis (likelihood and impact)(risk analysis, likelihood and impact): The evaluation of risks based on their probability of occurrence and severity of consequences.
Risk monitoring and control(risk monitoring and control): The ongoing process of tracking risk status and adjusting test activities as risks change.
Risk reassessment frequency alignment with development model(risk reassessment frequency alignment, alignment with development model): Matching the cadence of risk reassessment to the development model (periodic for sequential, continuous for Agile) to keep testing relevant.
Risk-Based Decision Making(risk-based decisions): A decision approach that prioritizes metrics and actions based on project risks.
Risk-Based Estimation Matrix(risk-based estimation matrix): A table linking each risk item to its risk level, test depth, and estimated effort.
Risk-Based Testing(risk-based testing, rbt): An approach to testing that reduces product risks and informs stakeholders about their status.
Risk-Based Testing (RBT)(risk-based testing, rbt): A testing approach that prioritizes test activities based on the level of product risk.
Risk-Based Testing Context(risk-based testing context): A testing approach where test efforts are prioritized based on risk levels.
Risk-Based Testing Frequency Variation(risk-based testing frequency): The difference in risk reassessment frequency: continuous in Agile and periodic in sequential models.
Risk-based test prioritization(risk-based test prioritization): The practice of ordering test execution to address the highest product risks first.
Risk-based testing in Agile(risk-based testing agile): A testing strategy where efforts are prioritized by risk, with continuous risk reassessment in Agile projects.

S

SMART Criteria(smart): A framework for selecting metrics that are Specific, Measurable, Achievable, Relevant, and Time-bound.
Sequential Test Management Phase-Gate Approach(phase-gate approach, phase-gate approach in sequential test management, phase-gate): A test management approach where test planning occurs early and test execution is concentrated in later phases, with strict phase gates.
Stakeholder Analysis(stakeholder analysis): A technique used to identify stakeholders and assess their influence, needs, and expectations on testing.
Stakeholder Engagement(stakeholder engagement): Involving stakeholders from various areas to capture a broad view of risks.
Stakeholder Expectations Management(managing expectations): The ongoing activity of aligning stakeholder expectations with project constraints through communication and feedback.
Stakeholder Information Needs(information needs, stakeholders and their information needs): The specific data and level of detail required by different project stakeholders.
Stakeholder Needs Analysis(analyzing stakeholder needs, needs analysis): The process of analyzing stakeholder requirements such as quality attributes, risk tolerance, and reporting frequency.
Stakeholder Sign-off(stakeholder sign-off): Formal approval from stakeholders that exit criteria are met and testing can close.
Stakeholder engagement for risk capture(stakeholder involvement in risk, broad risk capture): Involving stakeholders from diverse areas to obtain a broad perspective on potential risks during risk identification workshops.
Status Accounting(status accounting): A CM function that records and reports the history of changes, including what, who, when, and why.
Success Criteria(success criteria): Measurable conditions that define when testing is considered complete and successful, based on stakeholder expectations.

T

Technical Test Analyst(technical test analyst): Handles non-functional aspects like performance and security.
Test Activities Sequence(test activities sequence): The ordered steps from test planning to completion in the test process.
Test Approach(test approach, test strategy): The overall strategy for testing, including methods and techniques.
Test Automation for Regression Testing(test automation, regression test automation): The use of test automation to handle regression testing within Agile sprints, ensuring fast feedback.
Test Case Execution Status(test case execution status): A metric indicating whether a test case passed, failed, or was blocked.
Test Completion Report(test completion report): A document summarizing test results, exit criteria status, and remaining risks.
Test Control(test control): Taking corrective actions when deviations from the test plan are detected.
Test Deliverables(test deliverables): The artifacts produced during testing, such as reports and logs.
Test Environment(test environment): The hardware, software, and network setup required for executing tests.
Test Estimation Factors(factors influencing estimation, factors influencing test estimation): Factors affecting estimation accuracy including requirements quality, environment, tool support, team skills, and system complexity.
Test Estimation Techniques(test estimation techniques, metrics-based estimation, expert-based estimation): Methods such as metrics-based and expert-based estimation for predicting test effort.
Test KPIs(kpis, test case execution progress, defect discovery rate): Key performance indicators such as test case execution progress and defect discovery rate.
Test Leader(test leader): Coordinates daily testing activities and may perform hands-on testing.
Test Levels(test levels): Different stages of testing such as component, integration, system, and acceptance.
Test Lifecycle(test lifecycle): The sequence of phases from test planning to closure, during which stakeholder management is critical.
Test Management(test management): The planning, scheduling, estimation, execution, control, and closure of test activities, including stakeholder communication.
Test Manager(test manager): The person responsible for project management of testing activities and resources, and accountable for the test process.
Test Manager Facilitation of Retrospectives(facilitates the session): The role of the test manager in guiding the retrospective session to ensure participation and constructive discussion.
Test Manager Role Shift in Agile(test manager role, facilitator and coach, test manager role as facilitator, test manager facilitator): The change of the test manager's role from process enforcer in sequential models to facilitator and coach in Agile models.
Test Manager as Mediator(test manager as mediator): The role of the test manager in resolving conflicts about quality, priorities, or resource allocation constructively.
Test Metrics(test metrics): Quantitative measures used to monitor and control the test process.
Test Monitoring(test monitoring): Tracking actual progress against the plan using KPIs like execution progress and defect discovery rate.
Test Monitoring and Control(test monitoring and control): Tracking risk status and adjusting the test plan as new risks emerge or existing risks change.
Test Objectives(test objectives): Specific goals of testing that are influenced by stakeholder needs and documented in the test plan.
Test Plan(test plan): A key output of the test planning process that documents the project test strategy.
Test Planning(test planning): The activity of establishing or updating a test plan, as defined by the ISTQB glossary.
Test Planning Process(test planning process): The phase in test management where test objectives, success criteria, and stakeholder responsibilities are defined.
Test Planning for Risk Mitigation(test planning): Definition of risk mitigation strategy including test techniques, coverage criteria, and entry/exit conditions.
Test Process Needs-driven Tool Selection(needs-based tool selection): The principle that tool selection should be based on test process needs and the tool's ability to support those needs, not solely on features.
Test Report(test report): A document summarizing test activities and results as defined by the ISTQB glossary.
Test Reporting Framework(test reporting framework): A structure that defines what, when, and how to report test results, including metrics, frequency, audience, and format.
Test Stakeholder Identification(identifying test stakeholders): The process of identifying all individuals or groups with an interest in testing, often using stakeholder analysis or RACI matrices.
Test Strategy(test strategy): A plan defining test levels, test types, and the approach to risk-based testing.
Test Team(test team): A group of people responsible for testing activities, emphasizing independence and cross-functionality.
Test Techniques(test techniques, equivalence partitioning, boundary value analysis, decision table testing): Methods used to design test cases, such as equivalence partitioning, boundary value analysis, and decision table testing.
Test Types(test types): Categories of testing including functional, non-functional, structural, and change-related.
Test automation for regression(test automation regression): The use of automated tests to perform regression testing, critical in iterative models for speed and consistency.
Testware(testware): All test artifacts including test cases, scripts, data, and logs produced during testing.
Three-Point Estimation(three-point estimation): An estimation technique using optimistic, pessimistic, and most likely estimates to account for uncertainty.
Timeboxing in Retrospectives(timeboxed): Setting a fixed duration (e.g., 60-90 minutes) to maintain focus and avoid fatigue.
Tool Selection Criteria(tool selection criteria): Technical and organizational factors evaluated when choosing a test tool, including compatibility, scalability, cost, and alignment with process needs.
Top-down Estimation(top-down estimation, top-down percentage): A coarse estimation technique using historical averages or fixed percentages.

V

V-Model Test Level Correspondence(v-model test level alignment, v-model alignment): The principle in the V-model that each test level corresponds to a development phase, enabling early test design and defect prevention.
Vanity Metrics(vanity metrics): Metrics that look good but provide no actionable insight for decision-making.

W

Whole-Team Approach(whole-team approach): A quality philosophy where all team members share responsibility for quality, not just the test team.
Wideband Delphi(wideband delphi): A consensus-based estimation technique that leverages expert judgment to produce estimates.
Work Breakdown Structure(wbs): A technique that decomposes testing into smaller tasks to facilitate effort estimation.
Work Breakdown Structure (WBS)(wbs, work breakdown structure): A test estimation technique that decomposes testing into smaller tasks to estimate effort.