Over the last several years, a set of ideas and activities have been dumped into a steamer trunk called Agile software development. Agile development has hit mainstream recognition, even though there is often uncertainty and turmoil around what “Agile development” means, in theory and in practice—and that uncertainty and turmoil affects Agile projects and the people in them. James Bach and Michael Bolton, authors of Rapid Software Testing, hear testers expressing a good deal of pain over the role of the tester and the structure of testing activity in Agile projects. There are 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. However, it’s time to build on what has gone before. In this presentation, Michael Bolton will offer a review and an update of the Agile Testing Quadrants as seen through the lens of Rapid Software Testing—an agile (but not necessarily Agile) approach. Michael will show how Agile development can—and should—be infused with testing that helps to identify and defend the value of the product while reducing the costs of development.
See more at: