1.1Why Agile Changed Everything for QA

The biggest shift Agile brought to QA was timing. In waterfall, testing happened after development was "done." Requirements were written, designs were approved, code was built, and then -- often weeks or months later -- the testing team received a finished product and began looking for defects. By that point, the cost of fixing any bug was enormous: the code was complete, the developers had moved on to other projects, and the architecture could not easily accommodate changes.

In Agile, testing is woven into every sprint, every story, every conversation. A QA engineer in an Agile team is not a gatekeeper who approves or rejects work at the end. They are a quality advocate who shapes how work is defined, built, and verified from the start.

This distinction matters. It is not just a change in process; it is a change in identity. The waterfall QA engineer asked: "Does this work correctly?" The Agile QA engineer asks: "How do we make sure this works correctly before we even start building it?"