This is the first of  a few guests posts from Version One.

Staying competitive in today’s economy means companies must deliver the right products to market faster and with higher quality than ever before. Adopting agile development methods is a significant way organizations are doing this. Making the switch to test-first programming and agile testing challenges traditional notions of software engineering best practices.

 

Myth 1: Everyone on an agile team tests therefore dedicated testing resources aren’t needed.

Fact: Teams interested in delivering a quality product realize that the same product knowledge, preparation, discipline and skills used in traditional QA should be leveraged when transitioning to agile.

Myth 2: Testers are second class citizens on an agile team.

Fact: Testers are valuable members of an agile team and often add a unique perspective in terms of identifying potential roadblocks and dependencies early in the process.

 

Myth 3: Important testing activities that aren’t product-related won’t get done.

Fact: Additional testing activities, such as performance and regression testing, are addressed through test-oriented stories, which are estimated, planned and tracked just like product-related stories.

Learn more about Test-First programming, and how to transition from traditional testing to agile testing.

Share →

One Response to Top 3 Myths of Agile Testing

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>