Testers integrating with development team in the Agile lifecycle

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.

Download this free guide

A developer's guide to continuous testing

The pace of application development has been increasing rapidly. Continuous testing is the only way to avoid bottlenecks. Download this PDF to introduce continuous testing in your organization.

Start Download

• Corporate E-mail Address:

  You forgot to provide an Email Address.

  This email address doesn’t appear to be valid.

  This email address is already registered. Please login.

  You have exceeded the maximum character limit.

  Please provide a Corporate E-mail Address.

• • I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.

  Please check the box if you want to proceed.

• • I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.

  Please check the box if you want to proceed.

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent.

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.