Readers will come away from this book understanding
* How to get testers engaged in agile development
* Where testers and QA managers fit on an agile team
* What to look for when hiring an agile tester
* How to transition from a traditional cycle to agile development
* How to complete testing activities in short iterations
* How to use tests to successfully guide development
* How to overcome barriers to test automation
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Jon Strayer wrote:Why would I want to read your book?
Here's one of our "user stories", contributed by Robin Dymond and included in our preface:
"As a QA professional, I can understand the main difference between traditional QA professionals and agile team members with a QA background, so that I can begin internalizing my new responsibilities and deliver value to the customer sooner and with less difficulty".
That's one main audience of the book. It's also for developers who wonder who should be doing what testing, development managers wondering how to engage testers, teams worried that they can't get their testing finished by the end of each iteration, teams who wonder when they can do their non-functional testing in an agile project, and more.
As I described in another post here, you will also benefit from reading about the experiences of numerous other agile practitioners and their teams, the agile testing issues they faced, and how they addressed them.
Co-author, with Janet Gregory: Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009) http://lisacrispin.com