Skip to main content
XenonStack

Enterprise Data Management

XenonStack Insights Scrum Testing Methodology: Roles, Quadrants and DoD

and | Published | Updated

Scrum Testing Methodology: stack from Scrum events and testing quadrants to Definition of Done and a verified Increment

Key takeaway

  • How testing works in Scrum: events, who tests, the four agile testing quadrants, a Definition of Done checklist, challenges and the role of AI agents.

What is Scrum testing methodology?

Scrum testing is not a separate method. It is the practice of building quality checks into every Sprint so that each Increment is verified before it is called done. The 2020 Scrum Guide defines Scrum as a framework and does not use the words "tester" or "testing" at all. It makes the Developers accountable for creating a usable Increment each Sprint, and it asks the team to meet a shared Definition of Done. Testing in Scrum is how a team earns that definition.

For a CTO or head of engineering, the practical question is who tests what, and when. This guide answers it with the Scrum events, the four agile testing quadrants, a Definition of Done you can audit, and the limits of the approach. For the wider discipline, see shift-left testing and continuous testing.

How does testing fit into the Scrum events?

Scrum has five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. A Sprint is a fixed-length event of one month or less (2020 Scrum Guide). Testing is not a phase at the end of it. It runs through every event.

Two-column diagram mapping Scrum events (Planning, Daily Scrum, Review, Retrospective) to testing contributions (acceptance criteria, pipeline health, stakeholder feedback, practice changes)
Scrum eventTesting contributionDecision it supports
Sprint PlanningClarify acceptance criteria, size test effort, agree what "done" needs for each itemWhat can the team verify within this Sprint?
Daily Scrum (15 minutes, for the Developers)Surface blocked tests, failing builds and unverified workDoes the Sprint Goal still look achievable?
Sprint workWrite and run tests alongside the code; fix defects in the same SprintIs the Increment meeting the Definition of Done?
Sprint ReviewDemonstrate the verified Increment and collect stakeholder feedbackDoes it solve the right problem?
Sprint RetrospectiveReview escaped defects, flaky tests and automation gapsWhich testing practice do we change next Sprint?

The Scrum Guide gives Sprint Planning a maximum of eight hours for a one-month Sprint, and the Daily Scrum is 15 minutes. Both are timeboxes, so test planning has to be lightweight and continuous rather than a separate document-heavy activity.

Who is responsible for testing in a Scrum team?

Scrum has three accountabilities: Developers, the Product Owner and the Scrum Master. There is no separate tester accountability in the Scrum Guide. Developers are "the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint", and that includes verification. In practice many teams still have people who specialise in testing, but they work as part of the Developers, not as a downstream gate.

AccountabilityRole in qualityWatch out for
Developers (including testing specialists)Build, test and verify the Increment; keep the tests currentTreating testers as a separate hand-off stage
Product OwnerOrders the Product Backlog and clarifies what acceptable behaviour meansVague stories that cannot be tested
Scrum MasterHelps the team improve its practices and remove impedimentsReporting test counts instead of removing blockers

How do the agile testing quadrants map to Scrum?

The agile testing quadrants, described by Lisa Crispin and Janet Gregory in their work on agile testing, sort tests along two axes: technology-facing or business-facing, and whether they guide development or critique the product. The numbering is arbitrary. According to the authors, it does not imply an order, and teams use techniques from all four quadrants concurrently in small increments.

QuadrantFocusTypical testsWho usually leads
Q1Technology-facing, guides developmentUnit and component tests, connectivity checksDevelopers
Q2Business-facing, guides developmentStory tests written first, prototypes, simulations, UX checksProduct Owner with Developers
Q3Business-facing, critiques the productExploratory, usability and user acceptance testing, business-level workflowsTesting specialists, users and stakeholders
Q4Technology-facing, critiques the productPerformance, load and security testing, other quality attributesSpecialists with platform and security teams

Source: Janet Gregory, Chapter 8 on the agile testing quadrants (read 13 November 2026). Many teams automate Q1 and much of Q2, and keep Q3 largely human. For the related testing types, see system testing and user acceptance testing.

What should a Scrum Definition of Done include for testing?

The Definition of Done is the commitment attached to the Increment. The Scrum Guide calls it a formal description of the state of the Increment when it meets the quality measures required for the product. A testing-aware version is specific enough to check. A starting point to adapt:

  • Code reviewed and unit tests passing in the build pipeline.
  • Acceptance criteria for the story demonstrated and agreed with the Product Owner.
  • Regression suite green; no known defects left open without a decision.
  • Non-functional checks agreed for the story (performance, security) completed or explicitly deferred with a reason.
  • Test evidence recorded where audit or regulation requires it.

If a team cannot meet its Definition of Done, the Scrum Guide says the item returns to the Product Backlog rather than being released. That rule is what keeps the testing commitment honest.

What does an agile tester need to do differently?

Compared with a waterfall test phase, the work changes in four ways.

AreaTraditional test phaseScrum team
TimingAfter development is completeThroughout the Sprint, from refinement onward
AutomationOptional or lateNeeded from the start so regression does not grow each Sprint
CollaborationHand-offs and defect ticketsShared work with Developers and the Product Owner
FeedbackAt releaseAt each Sprint Review

Automation is the main skill shift. Unit and behaviour-driven frameworks such as JUnit and Cucumber let a team re-run regression every Sprint without growing the test effort. Start with unit testing and extend to API testing.

What are the common challenges and when does Scrum testing not fit?

ChallengeWhy it happensResponse
Short Sprints leave little time to testTesting is left to the last daysSlice stories smaller; test continuously; automate regression
Changing scope mid-SprintStakeholder requests arrive lateRoute changes through the Product Owner and the Product Backlog
Testing seen as a separate teamOld structures carried into ScrumMake verification a Developer-level commitment
Hard-to-test non-functional needsQ4 work needs environments and dataPlan the environment early; run Q4 checks in the pipeline
Heavily regulated release evidenceAudit needs documented proofRecord evidence as a by-product of the pipeline

Scrum is a weaker fit for work that cannot be split into small verifiable increments, such as a single hardware certification event or a fixed-scope migration with one cutover. In those cases a hybrid plan, with Scrum for the build and a staged test and release gate, can be more honest than forcing every check into a Sprint.

How are AI agents changing testing in Scrum teams?

AI agents can now draft test cases from user stories, propose regression selections and help triage failures. They change who does the repetitive work, not who is accountable. Under the Scrum Guide the Developers remain accountable for the Increment, so agent output should be reviewed, versioned and covered by the same Definition of Done. Governed context, meaning the policies, acceptance criteria and decision history an agent should use, matters more than the agent itself. Read agentic software testing for controls, and agentic workflows for patterns.

For teams building this capability, ElixirClaw is an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control. AgentQA is described on its site as automated quality assurance for AI, and ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents.

How should an enterprise adopt Scrum testing?

  1. Write a Definition of Done that includes testing and make it visible.
  2. Automate Q1 first, then the stable parts of Q2.
  3. Add exploratory and acceptance testing (Q3) to each Sprint Review cycle.
  4. Move Q4 checks into the delivery pipeline.
  5. Use the Retrospective to track escaped defects and flaky tests, then adjust.
  6. Introduce AI agents for drafting and triage only under human review.

For the continuous-delivery side, see continuous testing in DevOps.

To map one testing decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.

Frequently asked questions

Is Scrum testing a separate methodology?

No. Scrum is a framework, and the 2020 Scrum Guide does not mention testers or testing. Testing is part of how the Developers verify each Increment and meet the Definition of Done.

Does Scrum have a tester role?

No. Scrum has three accountabilities: Developers, Product Owner and Scrum Master. Testing specialists work as part of the Developers.

What are the agile testing quadrants?

A taxonomy by Crispin and Gregory that sorts tests as technology-facing or business-facing, and as guiding development or critiquing the product. The numbering implies no order.

How long is a Scrum Sprint, and what does that mean for testing?

A Sprint is one month or less according to the 2020 Scrum Guide. Testing and automation must therefore run inside the Sprint, not after it.

What if an item fails the Definition of Done?

It is not released or presented as done. The Scrum Guide says it returns to the Product Backlog for future consideration.

Can AI agents replace testers in Scrum?

They can draft tests and help triage failures, but the Developers stay accountable for the Increment, so agent output needs human review.

Table of Contents

navdeep-singh-gill

Navdeep Singh Gill

Global CEO and Founder of XenonStack

LinkedIn profile

Navdeep Singh Gill is serving as Chief Executive Officer and Product Architect at XenonStack. He holds expertise in building SaaS Platform for Decentralised Big Data management and Governance, AI Marketplace for Operationalising and Scaling. His incredible experience in AI Technologies and Big Data Engineering thrills him to write about different use cases and its approach to solutions.

Get the latest articles in your inbox

Subscribe Now

Interested in solving your challenges with the XenonStack team?
Get Started

Tell us about you and your priorities so we can prepare the right conversation. It takes about 2 minutes.

Please Select your Industry
Banking
Fintech
Payment Providers
Wealth Management
Discrete Manufacturing
Semiconductor
Machinery Manufacturing / Automation
Appliances / Electrical / Electronics
Elevator Manufacturing
Defense & Space Manufacturing
Computers & Electronics / Industrial Machinery
Motor Vehicle Manufacturing
Food and Beverages
Distillery & Wines
Beverages
Shipping
Logistics
Mobility (EV / Public Transport)
Energy & Utilities
Hospitality
Digital Gaming Platforms
SportsTech with AI
Public Safety - Explosives
Public Safety - Firefighting
Public Safety - Surveillance
Public Safety - Others
Media Platforms
City Operations
Airlines & Aviation
Defense Warfare & Drones
Robotics Engineering
Drones Manufacturing
AI Labs for Colleges
AI MSP / Quantum / AGI Institutes
Retail Apparel and Fashion

Continue