Undoing Testing Methods in Agile Projects

[presentation]
by
Brian Marick, Testing Foundations
Summary: 

The period 2002-2004 was one of enormous progress in figuring out how testing fits in on agile projects. Test-driven design is more about designing and writing the code than about finding bugs. New testing tools such as xUnit and FIT came out and received a lot of use by early adopters. The hopeful notion that customers would write acceptance tests to find bugs was expanded, challenged, and deepened. With all that progress, it's hard to be dissatisfied with these methods in agile projects. But past ways of thinking are holding us back. To make further progress, we have to split our notion of testing into two parts: the task of after-the-fact product critique, and a role that has nothing at all to do with bugs and, really, little to do with the word "testing." Brian Marick, a founding member of the Agile Alliance, explains what that role presents and some ideas on how to fill it.

  • The evolving role of testing in agile development projects
  • Finding bugs is not enough to deliver the value customers need in agile projects
  • A new view for agile development processes

Upcoming Events

Apr 13
May 03
Jun 01
Jun 07