Over the last several years, a set of ideas and activities have been dumped into a big bucket called “Agile software development”. Agile development has hit mainstream recognition. Yet there is often uncertainty and turmoil around what “Agile development” means, in theory and in practice, and the confusion affects Agile projects and the people in them.
There have been some discussion points, such as Mike Cohn’s Agile Testing Pyramid and Marick, Crisipin and Gregory’s Agile Testing Quadrants, and many people have found them helpful. Yet James Bach and Michael Bolton, authors of Rapid Software Testing, still hear testers expressing a good deal of pain over the role of the tester and the structures of testing activity in Agile projects.