CTEL-TM-OTM — Operational Test Management

CTEL-TM-OTM — Operational Test Management glossary

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

#

4L's(4l's, liked learned lacked longed for): A retrospective format focusing on Liked, Learned, Lacked, and Longed for aspects.
4L's Retrospective Format(4l's, liked, learned, lacked, longed for, 4l's retrospective format, 4l's format, liked, learned, lacked, and longed for): A retrospective format that asks participants to share what they Liked, Learned, Lacked, and Longed For.
4L's Retrospective Technique(4l's, 4 l's, liked learned lacked longed for): A retrospective method using Liked, Learned, Lacked, Longed for to uncover root causes.
5 Whys(5 whys): A root cause analysis technique that iteratively asks "why" to uncover underlying issues.
5 Whys Retrospective Technique(5 whys, five whys): A retrospective method that repeatedly asks 'why' to identify root causes of issues.
5 Whys Technique(5 whys, 5 whys technique): A root cause analysis method that iteratively asks 'why' to drill down from a symptom to its underlying cause.

A

Acceptance Criteria(acceptance criteria): Explicit conditions in a test service contract that test deliverables must meet to be accepted.
Acceptance Criteria for Test Deliverables(acceptance criteria): Clear criteria in SLAs to define when deliverables are accepted.
Accountability in Retrospective Actions(accountability): The requirement that each action item has a named lead with authority and resources to complete it.
Action Item Ownership(single owner): The practice of assigning a single accountable person for each retrospective action item.
Action Item Prioritization(prioritization): The selection of the top 2-3 most impactful actions from a single retrospective to avoid overloading the team.
Action Item Tracking System(tracking system): A persistent tool, such as a project management system, used to monitor retrospective action items.
Action Items(action items, action item): Specific, measurable improvements with assigned owners and deadlines from a retrospective.
Action Items Tracking(action items tracking): The process of recording, assigning owners and deadlines, and reviewing progress of improvement tasks from retrospectives.
Action item(action item, action items): A concrete task with an owner and deadline resulting from a retrospective.
Analogy-Based Estimation(analogy): An estimation technique that uses historical data from similar projects to estimate resources.

B

Blame-Free Environment(blame-free environment, blame-free, blame-free retrospective, blame-free culture): A principle ensuring retrospectives focus on process improvement, not individual performance.
Blame-Free Retrospective(blame-free event, blame-free retrospective): A retrospective focused on process improvement, not individual performance.

C

Change Control Process(change control process): Formal process for evaluating and approving scope changes to manage impact on schedule, cost, and quality.
Change management(change management, change management clauses): A contractual clause defining procedures for handling changes in scope, requirements, or schedules.
Cognitive Biases in Risk Identification(cognitive biases): Mental biases such as optimism bias and confirmation bias that can lead to overlooking significant risks.
Communication Plan(communication plan): A plan defining what information is shared with stakeholders, how often, and through which channels.
Communication Protocol(communication protocol): Specifications for frequency, format, escalation paths, and tools for collaboration to ensure consistent information sharing.
Communication platform(common communication platform): A common tool or system used for sharing information and status updates between organizations.
Communication protocols(communication protocols): Defined frequency, format, escalation paths, and tools for collaboration in testing engagements.
Conflict Resolution(conflict resolution): Negotiation with project managers and stakeholders to resolve competing demands for resources.
Conflict Resolution in Resource Management(resource conflicts, conflict resolution): The process of resolving resource conflicts through negotiation with project managers and stakeholders.
Conflict mediation(conflict resolution, conflict mediation): The act of resolving disputes by focusing on contract terms and project goals.
Contingency Planning(contingency plans, contingency planning): Proactive identification of resource risks and preparation of backup plans to prevent shortages.
Continuous Improvement Culture(improvement culture, culture of continuous improvement): An organizational culture that values ongoing process enhancements through consistent practice and visible results.
Continuous Improvement Cycle(improvement cycle, continuous improvement cycle, ongoing cycle of improvement): A recurring activity that uses retrospective outcomes as primary input to enhance processes.
Continuous Risk Monitoring(continuous monitoring, monitor mitigation actions, continuous risk monitoring): The ongoing process of tracking risks and adjusting mitigation plans throughout the project lifecycle.
Contract Amendment: A formal change to the contract, documented to avoid reliance on verbal agreements.
Contract review(contracts reviewed by legal and procurement, contract review): The process of examining contracts by legal and procurement teams to ensure enforceability and completeness.
Corrective Actions(corrective actions): Provisions in a test service contract to address underperformance or non-compliance.
Crisis Management(crisis management): The process of identifying, assessing, and responding to events that could have a severe negative impact on the project.
Crisis Response Plan(crisis response plan): A plan that identifies potential crisis scenarios, roles, communication channels, and escalation paths.
Cultural Differences in Communication(cultural differences): Variations in communication styles and norms between organizations that can affect collaboration and require proactive management.
Cultural adaptation in testing communication(cultural and language differences, handling cultural differences): Adapting communication styles to address cultural, language, and time zone differences with global third parties.

D

Dashboard Audience Tailoring(audience tailoring): The practice of customizing dashboards (e.g., summaries for executives, drill-downs for test managers) to meet stakeholder needs.
Dashboard Design Principles(dashboard design principles): Key principles for effective dashboards including relevant KPIs, data accuracy, and update frequency.
Data-Driven Retrospective(data-driven retrospective): A retrospective using metrics like defect density, test coverage, or cycle time.
Delphi Technique(delphi technique): A structured method to avoid groupthink by gathering expert input anonymously and iteratively.

E

Earned Value Management(earned value management, evm): A technique to monitor test progress and cost performance by comparing planned vs actual work.
Effort Variance(effort variance): A metric comparing planned hours to actual hours to detect deviations in resource consumption.
Escalation Path(escalation paths): A defined route for escalating issues during outsourced testing.
Escalation Paths(escalation paths): Defined communication channels for reporting issues in a test service contract.
Expert Judgment(expert judgment): A common technique for resource estimation that relies on the experience of experts.

F

Facilitation Techniques(facilitation technique, timeboxing, round-robin, check-in): Methods like timeboxing and round-robin to ensure balanced participation.
Failure Mode and Effects Analysis (FMEA)(fmea, failure mode and effects analysis): A technique adapted to identify potential failure points in test processes and testware.
Fishbone Diagram(fishbone diagram, ishikawa diagram): A visual root cause analysis tool that categorizes potential causes of a problem.
Fixed-Price Contract(fixed-price): A contract where the price is agreed upon upfront regardless of effort.
Formal Change Control Process(formal change control process): A process to evaluate the impact of scope creep on schedule and budget in testing.
Formal review and acceptance process(formal review and acceptance process): A structured process including peer reviews, test result audits, and sign-off procedures for third-party deliverables.

G

Governance Dashboard(governance dashboard): A visual display consolidating test metrics from multiple levels to present a single source of truth for project health.
Governance Dashboards(governance dashboards, governance dashboard, dashboards): Real-time reporting tools that display key performance indicators related to testing progress and quality status.
Governance Framework(governance framework): A structure for decision-making and oversight that test service contracts must align with.
Governance Mechanism(steering committees, performance dashboards): A mechanism such as steering committees or performance dashboards to maintain oversight.

I

ISTQB Glossary(istqb glossary definitions): The official set of definitions for terms used in ISTQB exams.
Improvement Backlog(improvement backlog): A dedicated backlog for retrospective actions, treated with the same priority as other work items.
Improvement culture(improvement culture, culture of improvement): An environment where continuous improvement is valued and consistently practiced.
Integration of Actions into Workflow(workflow integration): The practice of adding retrospective actions to the team's regular backlog and monitoring progress routinely.
Integration of External Teams(integration of external teams): The alignment of an external organization's processes, tools, data, and handover points with the internal test strategy.
Integration of third-party processes and tools(integrating third-party processes and tools, test process integration): Aligning external tools, processes, and reporting formats with an organization's existing test process.
Interplay of Project and Product Risks(interplay of project and product risks): The relationship where a project risk (e.g., schedule delay) may increase a product risk (e.g., insufficient testing).
Iterative Risk Identification(iterative risk identification): The ongoing activity of reassessing risks throughout the project lifecycle, not a one-time event.

J

Joint kick-off meeting(joint kick-off meetings): A meeting held at the start of a project to align both parties on test objectives and acceptance criteria.

K

Key Performance Indicators(kpis): Metrics such as test execution progress, defect density, and risk status tailored to stakeholders.
Key Performance Indicators (KPIs)(key performance indicators, kpis, kpi): Quantifiable measures used to evaluate the success of testing in meeting defined business objectives.
Key performance indicator(kpi, key performance indicators): A measurable value used to evaluate the success of a project or service against objectives.
Knowledge Transfer Clause: A contract clause to mitigate disruption from vendor staff turnover.
Knowledge transfer(knowledge transfer): The process of transferring domain knowledge and skills from third-party to internal teams at engagement end.

L

Level Test Plan(level test plan): A document detailing execution for specific test levels, distinct from the master test plan.
Liaison role(central communication hub, liaison role): Central communication hub for coordinating multiple third parties in testing projects.

M

Managing Stakeholder Expectations(managing stakeholder expectations, stakeholder expectation management): The practice of setting realistic expectations through clear communication of test scope, schedule, risks, and dependencies.
Master Test Plan(master test plan): A governance document that links testing to business objectives.
Milestone Progress(milestone progress): A metric displayed on governance dashboards tracking progress toward key project milestones.

O

Operational vendor management(operational vendor management): The management of third-party relationships covering contracts, communication, integration, and quality verification.
Organizational Resilience(organizational resilience): The goal of building the ability to handle crises through continuous improvement.
Outcome-Based Contract(outcome-based): A contract where payment is tied to achieving specified outcomes.

P

Parametric Model(parametric models, parametric model): An estimation technique that uses parameters such as hours per test case to calculate resource needs.
Pilot phase(pilot phase): A trial phase to test integration of third-party processes before full-scale rollout.
Power-Interest Grid(power-interest grid): A tool to categorize stakeholders based on their level of influence and interest for prioritizing engagement.
Process Improvement Focus(process improvement): The emphasis on improving processes and systems rather than assigning blame to individuals.
Process alignment(aligning processes, process alignment): The activity of aligning external organization's processes with internal test strategy through explicit agreement and training.
Product Risk(product risk): A risk related to the quality of the product, such as potential defects or failures in the software.
Project Risk(project risk): A risk related to the management and control of the project, such as resource availability or schedule constraints.
Project Risk Management(project risk management): A continuous activity throughout the project that includes risk assessment and contingency planning.
Proportionality of mitigation(proportionality, cost-effectiveness): The principle that the cost and effort of mitigation should be appropriate to the potential impact of the risk.

Q

Quality Audit: A review of vendor's processes and outputs to detect deviations early.
Quality Verification(quality verification): The process of independently checking third-party work against agreed acceptance criteria.
Quality verification and acceptance(quality verification and acceptance): A process to verify third-party deliverables against agreed acceptance criteria through reviews and audits.
Quality verification mechanism(quality verification, quality verification mechanisms, peer reviews, audits): A method such as peer reviews and audits used to maintain consistency in testing outputs.

R

Resource Allocation(resource allocation): The assignment of resources to tasks based on skills, availability, and critical path needs.
Resource Conflict Resolution(resource conflicts): Negotiation with project managers and stakeholders to resolve competing demands for shared resources.
Resource Estimation(resource estimation): The process of defining types and quantities of resources needed based on test plan and risk analysis.
Resource Leveling(resource leveling): A technique to schedule work and allocate people to avoid overloading or underutilizing resources.
Resource Monitoring(resource monitoring): Continuous tracking of actual resource consumption using metrics like planned vs. actual hours.
Resource Plan(resource plan): An output of resource estimation that lists each resource category, its quantity, and the time period it is needed.
Resource Pool Approach(resource pool approach): A shared pool of resources used across multiple projects to improve utilization with careful governance.
Resource Utilization(resource utilization): A metric displayed on governance dashboards showing how test resources are being used.
Resource Utilization Rate(resource utilization rates): A metric measuring the percentage of available resources being used.
Resource pool(resource pools): A collection of computing resources that are dynamically allocated to meet workload demands.
Retrospective(retrospective, retrospectives): A blame-free structured meeting to reflect on a process or iteration and identify improvements.
Retrospective Action Review Loop(review loop): The practice of reviewing previous action items at the start of each retrospective to close the improvement cycle.
Retrospective Facilitation(facilitation): The skill of guiding a retrospective to ensure structured, productive outcomes with actionable improvements.
Retrospective Follow-up(follow-up): The practice of tracking and evaluating action items from retrospectives to ensure continuous improvement.
Retrospective Format(retrospective formats, start-stop-continue, sailboat metaphor, 4l's): A structured approach for conducting a retrospective, such as Start-Stop-Continue.
Retrospective Maturity Model(retrospective maturity model): A framework to assess and evolve the effectiveness of retrospective practices over time.
Retrospective Outcome Documentation(capturing outcomes): The process of capturing specific, measurable, time-bound action items from a retrospective session.
Retrospectives(retrospectives): A systematic method for continuous improvement where teams reflect on past work to identify improvements.
Risk Analysis(risk analysis): An evaluation that identifies higher-risk areas, which require more skilled testers, additional tools, or more time.
Risk Identification(risk identification): The process of finding, recognizing, and describing risks that might affect the achievement of objectives.
Risk Management in Resource Management(resource risks, contingency plans): Proactive identification of resource risks and establishment of contingency plans to prevent shortages.
Risk Mitigation(risk mitigation): The process of identifying, evaluating, selecting, and implementing actions to reduce risk to an acceptable level.
Risk Mitigation Strategies(risk mitigation strategies): Actions tailored to risk type: project management actions for project risks, technical testing actions for product risks.
Risk Register(risk register): A document that records identified risks, response strategies, actions, owners, and timelines.
Risk Response Strategies(response strategies, mitigation options, risk response strategies): Options for addressing a risk: avoid, transfer, mitigate, or accept, each with specific actions.
Risk Status(risk status): A metric displayed on governance dashboards indicating the current risk exposure of the project.
Risk Workshops(risk workshops): Structured facilitation sessions where cross-functional teams collaboratively identify risks using techniques like SWOT analysis or Delphi.
Risk management process(risk management process steps): A sequence of steps including risk identification, analysis, prioritization, mitigation planning, and monitoring.
Risk-Based Testing (RBT)(risk-based testing, rbt): A technique that prioritizes test efforts based on the likelihood and impact of product failures.
Risk-based Testing(risk-based testing): A testing approach that prioritizes test activities based on the risk of failure and impact of defects.
Root Cause Analysis(root cause analysis, root cause analysis techniques, 5 whys, fishbone diagrams, root cause, root causes, 5 whys root cause analysis, 5 whys technique): A systematic technique to identify the fundamental source of a problem or defect.
Root Cause Analysis in Retrospectives(root cause analysis): A technique to identify underlying causes of issues rather than focusing on symptoms during retrospectives.

S

SWOT Analysis(swot analysis): A technique that examines strengths, weaknesses, opportunities, and threats to identify risks in a structured manner.
Safe Environment for Retrospectives(safe environment): Psychological safety established in retrospectives that encourages honest feedback without fear of blame.
Safe environment(safe environment, safe environment for retrospectives): A psychological space where team members feel comfortable giving honest feedback without blame.
Sailboat Metaphor(sailboat metaphor): A retrospective format using a sailboat analogy to discuss wind (enablers) and anchors (obstacles).
Sailboat Retrospective(sailboat retrospective, sailboat retrospective format, sailboat): A retrospective format using a sailboat metaphor to identify what propels the team forward and what holds it back.
Scope Change Negotiation(negotiating scope changes): The negotiation of trade-offs with stakeholders when scope changes impact test schedule or resources.
Scope Creep(scope creep): A risk where project scope expands beyond original contract terms, affecting budgets and timelines.
Scope Management(test scope management): Controlling changes to the agreed test scope through a formal change control process.
Secondary Risks(secondary risks): New risks that arise as a direct result of implementing a risk mitigation action.
Service Level Agreement (SLA)(sla, service level agreement, slas): Measurable quality and timeliness metrics included in a test service contract to verify provider performance.
Service level agreement(service level agreement, sla, service-level agreements, service-level agreement): A contract specifying deliverables, acceptance criteria, timelines, communication protocols, and quality standards.
Service-Level Agreement in Testing(service-level agreement, sla): A contractual document specifying expected service levels, including response times, quality metrics, and escalation paths for testing services.
Service-level agreements in testing(slas, service-level agreements): Contractual agreements specifying communication expectations for testing services.
Shared Environment Scheduling(shared environment scheduling): The proactive coordination of test environment usage across organizations to prevent resource conflicts.
Single point of contact(spoc, single point of contact (spoc), single point of contact): A designated individual within each organization for communication and issue resolution.
Stakeholder Analysis(identifying and analyzing stakeholders, analyzing stakeholders, stakeholder analysis): The process of identifying stakeholders and assessing their influence, interest, and expectations.
Stakeholder Communication in Testing(test status reporting, communicating test results): The reporting of test status, risks, and issues in a way that stakeholders understand their implications for project decisions.
Stakeholder Identification(identifying stakeholders): The process of finding all individuals or groups affected by testing activities.
Stakeholder Management(effective stakeholder management): Ongoing activities to secure resources, gain support, and mitigate conflicts with individuals or groups affected by testing.
Stakeholder Register(stakeholder register): A document that records stakeholder contact information, roles, expectations, and communication preferences.
Start-Stop-Continue(start-stop-continue, start-stop-continue retrospective): A retrospective format where participants identify actions to start, stop, and continue.
Structured Risk Identification Techniques(structured risk identification techniques): Systematic and repeatable methods for identifying risks beyond simple brainstorming, such as checklists and workshops.
Syllabus learning objective(syllabus learning objectives, learning objectives): A specific statement of what a candidate should know or be able to do after study.

T

Termination Clauses(termination clauses): Contract provisions that allow termination under specified conditions such as breach or non-performance.
Test Activity Dependencies(dependencies between test activities, test activity dependencies): The dependencies between test activities and other project tasks that affect scheduling.
Test Activity Dependency(test activity dependencies): A relationship where one test activity must be completed before another can begin, such as waiting for a vendor build.
Test Cost Management(cost management in testing, test cost management): The process of tracking actual expenditure against the test budget and reporting variances.
Test Environment Scheduling(test environment scheduling): The proactive scheduling of shared test environments to avoid resource conflicts.
Test Governance(governance): Oversight mechanisms ensuring testing meets business objectives, including governance checkpoints and reporting.
Test Management as a Sub-Project(test manager's role in planning, scheduling, and controlling testing): The practice of planning, scheduling, and controlling testing activities as a separate sub-project within the overall project.
Test Manager Mediator Role(mediator role): The role of the test manager in resolving conflicts by focusing on contract terms and project goals.
Test Manager Project Management Role(test manager's project management role): The responsibility of the test manager to plan, schedule, and control testing activities as a sub-project.
Test Manager Responsibility for Stakeholder Understanding(test manager responsible for ensuring stakeholders understand test results): The test manager's duty to ensure stakeholders comprehend test results and their implications for project decisions.
Test Plan Alignment(test plan alignment with project schedule, test plan alignment, test plan alignment with project plan): The integration of the test plan into the project plan and synchronization of test milestones.
Test Process Model(test process model, v-model, agile): A model such as V-model or agile that defines how an external test provider integrates with internal teams.
Test Project(testing sub-project): The testing sub-project that the test manager oversees within the broader project context.
Test Resource Management(resource management in testing): The management of people, tools, and environments needed for testing activities.
Test Scope Management(scope management in testing): The process of controlling changes to test scope and managing stakeholder expectations.
Test Service Contract(contract, test service contract): A legally binding agreement defining scope, deliverables, SLAs, and governance for outsourced testing services.
Test Stakeholder Communication(stakeholder communication in testing, stakeholder communication): The communication of test status, risks, and issues to project stakeholders.
Test environment integration(integration of test environments, test environment integration): The alignment of external organizations' test environments, tools, and data with internal test strategy.
Third-Party Relationship Management in Testing(third-party relationship management): The management of contracts, SLAs, and quality verification for external vendors or service providers involved in testing.
Third-party relationship management(third-party relationship management): Management of relationships with external organizations that provide testing services or products.
Time-and-Materials Contract(time-and-materials): A contract where payment is based on actual time and materials used.
Timeline-based Retrospective(timeline-based retrospective, timeline): A retrospective format that arranges events chronologically to identify patterns and insights.
Traceability of Retrospective Outcomes(traceability): Documentation that supports linking retrospective actions to improvement goals for later review.
Traffic-light Indicators(traffic-light indicators): Color-coded statuses (red/amber/green) used on dashboards to highlight deviations from the plan.

U

Utilization Rate(utilization rate, utilization rates): A metric that tracks the percentage of time testers spend on testing versus other tasks.