CT-ATLaS — Agile Test Leadership at Scale

CT-ATLaS — Agile Test Leadership at Scale glossary

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

#

5 Whys technique(5 whys, 5 whys technique, the 5 whys technique): A root cause analysis technique that iteratively asks 'why' until the root cause becomes a process or policy issue.

A

Act Phase(act phase, act): The PDCA phase where decisions are made to standardize, adjust, or abandon the improvement based on results.
Aggregated 5 Whys(aggregated five whys, aggregated 5 whys): A technique that collects multiple 5 Whys from different teams and looks for common root causes.
Agile Test Leadership(agile test leadership, agile test leader): The role responsible for shaping organizational test strategy and fostering a quality assistance culture.
Agile test leader(agile test leader): A role responsible for shaping test strategy, coaching teams, and driving continuous improvement across the organization.
Alignment with business strategy(alignment with business strategy): The principle that the organizational test strategy must align with business and technology strategies.

B

Balancing Loop(balancing loop, balancing (b)): A feedback loop in a CLD that counteracts change to maintain stability, marked with a B.
Blame Culture(blame culture): A dysfunctional organizational culture that focuses on individual performance rather than process and system improvements.

C

CLD Boundary(boundary of the diagram): The scope of a causal loop diagram that determines which variables are included or excluded.
CLD Variable(variable, variables): An element in a causal loop diagram connected by arrows representing causal relationships.
Causal Link Polarity(polarity, plus sign, minus sign): A plus or minus sign on an arrow in a CLD indicating the direction of causal influence.
Causal Loop Diagram(cld, causal loop diagram (cld), causal loop diagram, clds): A technique that maps reinforcing and balancing feedback loops to understand systemic root causes.
Causal Loop Diagrams(causal loop diagrams): A system thinking tool that maps feedback loops to enable improvement.
Check Phase(check phase, check): The PDCA phase where data is analyzed to evaluate whether the change achieved the desired improvement.
Co-creation of test strategy(co-creation, co-created with stakeholders): Involving stakeholders from business, development, and operations in creating the test strategy.
Coaching and Facilitation(coaching and facilitation): Skill of enabling teams to own quality through coaching on testing practices, facilitating retrospectives, and fostering psychological safety.
Communities of Practice(communities of practice): Groups that share knowledge and standardize practices while allowing teams to adapt to their context.
Community of Practice(community of practice, cop): A group that defines standards, shares examples, and coaches teams on problem-solving techniques.
Community of practice (CoP) for problem-solving(community of practice, cop): A group of practitioners who establish standards, share examples, and coach teams on problem-solving techniques.
Confirmation Bias(confirmation bias): The tendency to favor evidence that confirms existing beliefs, which can hinder honest evaluation in Check phase.
Consistent application of problem-solving techniques across teams(consistent application across teams): Alignment of core steps and terminology for a problem-solving technique across multiple teams.
Context Dependency of Test Statements(x is better than y depends on context): Principle that effectiveness of testing approaches depends on project context.
Continuous Improvement(continuous improvement): An ongoing effort to enhance quality and testing through iterative application of the PDCA cycle.
Continuous Improvement at Scale(continuous improvement at scale, continuous improvement): Application of improvement techniques like PDCA and root cause analysis across multiple teams.
Continuous testing(continuous testing): A DevOps practice that involves testing continuously throughout the development lifecycle.
Cross-team Retrospectives(cross-team retrospective): Facilitated sessions where test leaders drive improvements that have organization-wide impact based on RCA findings.
Cumulative Flow Diagram(cumulative flow diagram): A chart showing the number of work items in various states over time to reveal bottlenecks.
Customer-Centric Value Stream(customer-centric value stream): A value stream that starts and ends with the customer's need, ensuring all activities are evaluated against customer value.
Cycle Time(cycle time): The time from the start to the finish of a work item, measuring the duration of active work.

D

Dashboard(dashboards): A visual tool that shows metric trends, anomalies, and updates frequently.
Defect Escape Rate(defect escape rate): A metric tracking the proportion of defects found in production versus earlier testing phases.
Defect Trend Chart(defect trend chart): A chart that displays the trajectory of defect rates over time.
DevOps Integration(devops practices, devops integration): Ensuring testing is an integral part of the flow, enabling fast feedback and risk mitigation.
Development Value Stream(development value stream, development value streams): A type of value stream that encompasses the activities needed to create new products or features.
Do Phase(do phase, do): The PDCA phase where the planned improvement is implemented on a small scale as a pilot.

F

Feedback Loop(feedback loops, feedback loop): A mechanism that perpetuates or mitigates problems in complex systems, enabling fast risk mitigation.
Feedback Loops(feedback loop, reinforcing feedback loop, balancing feedback loop): Reinforcing and balancing loops that perpetuate or mitigate problems in complex systems in scaled Agile.
Flow Metrics(flow metrics, cycle time, lead time, wip, work in progress): Quantitative measures such as cycle time, lead time, and process cycle efficiency that assess flow.
Functional testing(functional testing): A test type focused on verifying the correctness of functions against specifications.

I

ISTQB Testing Terminology Glossary(istqb testing terminology glossary, istqb glossary): The authoritative collection of standardized definitions for testing terms used across ISTQB syllabuses and exams.

L

Lead Time(lead time): The total time from the initiation to the completion of a work item, including waiting time before work begins.
Lean Value Stream Concept(value stream concept): A core Lean concept that uses value streams to visualize and optimize the flow of work from request to delivery.
Living test strategy(living strategy, adaptive strategy): A test strategy that must be continuously adapted based on feedback and changing business needs.

M

Mean Time to Detect(mean time to detect, mttd): The average time taken to identify a defect after its introduction into the system.
Metrics Interpretation(metrics interpretation): A core skill of quality assistance involving using data like defect escape rate and cycle time to inform improvement actions.

N

Non-Value-Added Activity(non-value-added activities): An activity that consumes resources but does not add value from the customer's perspective, considered waste.

O

Operational Value Stream(operational value stream, operational value streams): A type of value stream comprising the primary activities that directly deliver value to the customer.
Order of Activities in a Test Process(order of activities): Sequence of steps in a test process such as planning, analysis, design, implementation, execution, closure.
Organizational Influence(organizational influence): Driving adoption of quality practices across teams without formal authority by building trust, using data, and navigating organizational politics.
Organizational Test Strategy(organizational test strategy, test strategy): A high-level plan that aligns testing with business goals and integrates with DevOps practices to enable fast feedback.
Outcome-based metrics(outcome-based metrics, outcome-based measurement): Metrics focused on customer satisfaction and time-to-value rather than the number of test cases executed.

P

PDCA(pdca, plan-do-check-act): A continuous improvement cycle of Plan-Do-Check-Act used to enhance quality and flow.
PDCA cycle(pdca cycle, pdca, plan-do-check-act, plan-do-check-act cycle): A four-step iterative method used for continuous improvement.
Pass Rate(pass rate): A metric that measures the percentage of tests or tasks that result in a successful outcome.
Performance testing(performance testing): A test type focused on evaluating speed, responsiveness, and stability under load.
Plan Phase(plan phase, plan): The PDCA phase where a quality or testing problem is identified and a measurable improvement goal is defined.
Priority(priority): The order in which a defect should be addressed based on business urgency.
Process Cycle Efficiency(process cycle efficiency, pce): The ratio of value-added time to total cycle time, indicating the amount of waste in a process.
Psychological safety(psychological safety): A blame-free environment essential for honest participation in root cause analysis and continuous improvement.

Q

Quality Assistance(quality assistance): A shift from test management to coaching teams on quality practices and promoting shared responsibility for quality.
Quality Metrics(quality metrics): Visible measures at the organizational level used to drive improvements and ensure alignment with goals.

R

Radiator(radiators): A physical or digital display that broadcasts key metrics for team visibility.
Reinforcing Loop(reinforcing loop, reinforcing (r)): A feedback loop in a CLD that amplifies change, marked with an R.
Risk Analysis Facilitation(risk analysis facilitation): A core skill of quality assistance involving helping teams identify and prioritize quality risks.
Risk-based test selection(selecting test types based on risk): The practice of choosing test types based on the risks and quality goals of each iteration.
Root Cause Analysis(root cause analysis, 5 whys, fishbone diagrams, rca): A technique to identify underlying causes of issues and systemic problems at the organizational level.
Root Cause Analysis at Scale(rca at scale, scaled root cause analysis): A technique that shifts focus from local defects to systemic patterns across teams in scaled Agile environments.
Root cause analysis (RCA)(root cause analysis, rca): A systematic approach to identify the underlying causes of a problem or event.

S

Security testing(security testing): A test type focused on identifying vulnerabilities and ensuring data protection.
Severity(severity): A measure of the impact or criticality of a defect on the system.
Severity vs. Priority(severity vs. priority): Attributes of a defect where severity indicates impact, priority indicates urgency.
Shared Responsibility for Quality(shared responsibility for quality): A culture where all team members own quality, enabled by coaching and supportive practices.
Shared quality ownership(shared quality ownership): A model where all team members are responsible for quality while test leaders own the quality process and metrics.
Shift Left(shift left, shift-left testing): The practice of moving testing activities earlier in the development lifecycle to catch defects early.
Shift from Quality Control to Quality Assistance(shift from quality control to quality assistance): A mindset evolution from defect detection after the fact to defect prevention through coaching and collaboration.
System Archetypes(system archetype, system archetypes): Recurring patterns such as 'Fixes that Fail' or 'Shifting the Burden' that explain persistent systemic issues.
Systemic Root Cause(systemic root cause): A root cause that, if removed, would prevent recurrence of a problem across multiple teams in the organization.
Systems Thinking(systems thinking, systems thinking approach): Understanding how quality decisions in one team affect the entire value stream to identify bottlenecks, feedback loops, and unintended consequences.

T

Technical Coaching(technical coaching): A core skill of quality assistance involving helping developers write testable code and design effective unit tests.
Test Automation Framework(test automation framework): A set of guidelines and tools used to automate test execution, often piloted in the Do phase.
Test Automation Guidance(test automation guidance): A core skill of quality assistance involving advising on tool selection and framework design for test automation.
Test Debt(test debt): Accumulated testing inefficiencies that slow down future delivery, like brittle automated test suites.
Test Leader as Coach and Facilitator(test leaders as coaches and facilitators): An evolved role where test leaders act as coaches and facilitators rather than gatekeepers, helping teams understand quality risks and choose testing techniques.
Test Level(test level, test levels): A specific stage in the software development lifecycle where testing is performed (e.g., unit, integration).
Test Level vs. Test Type(test level vs. test type): Distinct categories: test level refers to scope, test type refers to objective.
Test Manager vs. Test Management Role(test manager vs. test management role): Distinct roles: test manager oversees testing, test management role includes broader responsibilities.
Test Pass Rate(pass rate): The percentage of tests that pass, used as a quality indicator.
Test Type(test type): A classification of testing based on the objective or attribute being tested (e.g., functional, performance).
Testing Waste(testing waste, quality waste): Activities in testing that do not add customer value, such as excessive defect detection and rework.

U

Usability testing(usability testing): A test type focused on assessing ease of use and user satisfaction.

V

Validation(validation): Confirmation that the product meets the needs and expectations of stakeholders.
Validation vs. Verification(validation vs. verification): Software testing concepts: verification checks correct construction, validation checks correct product.
Value Stream(value stream, value streams): The end-to-end set of actions, both value-adding and non-value-adding, needed to deliver a product or service from concept to customer.
Value Stream Analysis vs Process Mapping(value stream analysis vs process mapping): A distinction where value streams focus on end-to-end customer value delivery, not internal processes.
Value Stream Mapping(value stream mapping, vsm): A Lean technique used to visualize and analyze the flow of work and information through the value stream, highlighting areas for improvement.
Value stream analysis(value stream analysis): The process of analyzing the value stream to identify bottlenecks and improve flow.
Value-Added Activity(value-added activities): An activity that directly contributes to delivering value to the customer from the end-to-end process.
Value-Driven Prioritization(value-driven prioritization): Aligning testing efforts with business value by understanding value streams, using flow efficiency metrics, and making trade-offs between coverage and speed.
Value-driven organization(value-driven organization): An organization that organizes work around value streams rather than functional silos.
Value-driven testing(value-driven testing): A testing approach focusing on flow efficiency, waste reduction, and practices like continuous testing and shift-left.
Vanity Metrics(vanity metrics): Metrics that appear positive but do not drive improvement or actionable decisions.
Verification(verification): Evaluation of whether a product or component meets specified requirements.

W

Waste(waste, defects, overproduction, waiting, unnecessary motion): Activities that do not add value and are targeted for elimination in Lean, such as defects, overproduction, waiting, and unnecessary motion.
Waste elimination(reducing waste, waste elimination): The removal of activities that do not contribute to quality or customer value, such as unnecessary documentation or redundant testing.
Waste in Software Development(waste, software development waste): Non-value-adding activities in software development, including partially done work, extra features, rework, handoffs, delays, and defects.
Work in Progress(work in progress, wip): The number of work items that have been started but not yet completed; high WIP increases cycle time.