One of the differences between a traditional software development lifecycle and an Agile lifecycle is not just how developers, business people and testers collaborate, but when they collaborate. In traditional environments, testing typically comes after the coding is complete, when the code is thrown over that notorious, hypothetical “wall.” In Agile environments, testers get involved early in the project and stay involved throughout the lifecycle.
But what can they do before the code is written? I spoke with Peter Varhol of Seapine Software at the recent Agile Development Practices West conference. In the following video clip, Varhol identifies four areas in which testers can work as a key player on an Agile team throughout the development cycle.