In Waterfall, testing is a distinct phase that happens after development is complete; in Agile, testing is a continuous activity interleaved with development throughout every short iteration. The difference changes when defects are found, how feedback flows, and how QA collaborates.
Waterfall runs sequential phases — requirements, design, build, then a big test phase — so testers receive a nearly-finished product and defects surface late, when they are expensive to fix and schedule pressure is highest. Agile breaks work into short iterations where each small increment is tested as it's built, so defects are found within days and feedback loops are tight. This reshapes QA practice: instead of a comprehensive test plan written upfront against fixed requirements, Agile QA works from evolving user stories and acceptance criteria, automates regression to keep pace with frequent change, and collaborates continuously with developers and the PO. Neither is universally 'better' — Waterfall can suit fixed-scope, heavily-regulated contexts — but Agile's early, continuous testing is why most modern software teams adopt it. Interviewers use this comparison to check that you understand testing timing and feedback, not just definitions.
A requirement misunderstanding about tax calculation would surface in Waterfall only during the test phase months later, forcing a costly late fix. In Agile, the same feature is tested in the sprint it's built, so the misunderstanding is caught within days when it's cheap to correct and the context is fresh.
| Aspect | Waterfall | Agile |
|---|---|---|
| Testing timing | Separate phase after build | Continuous each iteration |
| Defect discovery | Late (test phase) | Early (within the sprint) |
| Cost to fix a defect | High | Low |
| Requirements | Fixed, documented upfront | Evolving user stories |
| Response to change | Resisted / change-controlled | Expected and embraced |
| Feedback loop | Long | Short and frequent |
Scenario: An interviewer asks: 'We're moving from Waterfall to Agile. As a QA engineer, what changes for you day-to-day, and what new risks do you need to manage?' How do you answer?