Key takeaways
- Agile is a way of building software in small increments, with frequent feedback, instead of one big release at the end. Scrum is the most common Agile framework; Kanban is another.
- Scrum works in sprints (usually 2 weeks) with a fixed set of events: planning, daily stand-up, review and retrospective. The team has a Product Owner, a Scrum Master and the Developers, and testers belong to the Developers.
- In Agile, testing isn't a phase at the end. Testers work inside the team, every day, from refining the story to checking it's done.
Why this matters for your first job
Most job ads for testers mention Agile or Scrum, and interviewers often ask: "Have you worked in Scrum? What does a tester do in a sprint?"
You don't need years of experience to answer well. You need to understand the vocabulary and the tester's place in it. That's what this article gives you.
Agile in one minute
In 2001, a group of developers wrote the Manifesto for Agile Software Development. It values:
- individuals and interactions over processes and tools;
- working software over comprehensive documentation;
- customer collaboration over contract negotiation;
- responding to change over following a plan.
The idea: build a small piece, show it to real users, learn, adjust, repeat. Compare that to the Waterfall model, where testing came at the end of a long project, when changes were most expensive.
Scrum: the people
The Scrum Guide describes three accountabilities:
| Role | What they do | What it means for you as a tester |
|---|---|---|
| Product Owner (PO) | Decides what gets built and in what order; owns the backlog. | Your go-to person for "what should happen here?" and for bug priorities. |
| Scrum Master (SM) | Helps the team work well with Scrum and removes obstacles. | Raise blockers to them: no test environment, missing access. |
| Developers | Everyone who builds the product: programmers, testers, designers. | That's you. Quality is a shared team responsibility. |
Scrum: the things
- Product backlog: the ordered list of everything the product might need, owned by the PO.
- Sprint backlog: the items the team commits to for this sprint, plus the plan to deliver them.
- Increment: the working, tested result at the end of the sprint.
- User story: a small piece of value described from the user's view: "As a returning customer, I want to save my card, so that I can pay faster." It comes with acceptance criteria, the conditions it must meet.
- Story points: a relative estimate of effort and complexity (often 1, 2, 3, 5, 8, 13), not hours. Testers estimate too, since testing is part of the work.
- Definition of Done (DoD): the checklist every item must meet to be "done", for example "code reviewed, tests written and passing, tested on staging, no open major bugs".
Scrum: the events
- Sprint planning (start of the sprint): the team picks stories from the backlog and plans how to deliver them. Ask: "How will we test this? What test data or environment do we need?"
- Daily Scrum / stand-up (15 minutes, every day): what I did, what I'll do, what's blocking me. Keep it short: "Tested the saved-cards story, found two bugs, retesting the fix for the first one today."
- Backlog refinement (during the sprint): the team clarifies upcoming stories. This is where testers prevent bugs, by asking "What if...?" before any code is written.
- Sprint review (end of the sprint): the team shows the increment to stakeholders and gathers feedback.
- Sprint retrospective (end of the sprint): the team discusses how it worked and what to improve. Bring facts: "Three stories reached testing on the last day."
A tester's sprint, day by day
| When | What the tester does |
|---|---|
| Before the sprint | Reads upcoming stories, asks questions, helps sharpen acceptance criteria. |
| Sprint planning | Estimates testing effort; flags risky stories and missing test data. |
| Days 1–3 | Writes test ideas and cases while developers write code; prepares data and environments. |
| As soon as a story is ready | Tests it on the test environment, reports bugs, talks to the developer directly. |
| Throughout | Retests fixes, runs regression checks, updates or writes automated tests. |
| End of sprint | Confirms stories meet the Definition of Done; joins the review and retro. |
Kanban, briefly
Some teams use Kanban instead of sprints. Work flows continuously across a board with columns like To do → In progress → In test → Done, and each column has a limit on how many items it can hold.
For testers, the key rule is the same: an item isn't done until it's tested. If the "In test" column is always full, that's a signal the team should help with testing, not that testers should work faster.
A new tester joined a Scrum team that only called QA at the end of each story. Every sprint, stories reached testing on day 8 or 9 of 10, bugs were found too late, and half the stories rolled over to the next sprint.
The tester asked to join backlog refinement. For a story about a "Reorder" button, they asked: "What if a product from the old order is out of stock? Or its price changed?" Nobody had thought about it. The PO added two acceptance criteria on the spot.
Over the next few sprints, the team also agreed to finish and test stories one at a time instead of starting them all at once. Rollovers dropped noticeably, and the retro notes recorded fewer "found too late" bugs.
Lesson: in Agile, a tester's biggest impact often comes before testing starts: asking questions while the story is still cheap to change.
Want to go deeper?
The intermediate article on testing in Agile and Scrum covers the Agile testing quadrants, a strong Definition of Done, and the "mini-waterfall" trap that many teams fall into.
Do
In stand-up: "Yesterday I tested the saved-cards story and found a bug with expired cards, already logged. Today I'll retest it once the fix is on staging. I'm blocked on test data for business accounts and will sort it out with the PO after this."
Don't
In stand-up: "Still testing." Nobody learns what's done, what's at risk, or how to help.
Check yourself
It's day 9 of a 10-day sprint. A story reaches you for testing, and you find a major bug. The developer says it can't be fixed by tomorrow. What happens, and what could the team change for the next sprint?
Show answer
The story doesn't meet the Definition of Done, so it isn't counted as done in this sprint. The PO decides whether it returns to the backlog or continues next sprint. For the future, raise it in the retrospective: stories reaching testing on day 9 is the real problem. Fixes include smaller stories, testing earlier (even partial builds), and tester involvement in refinement.
