92 of 98 people found the following review helpful
Interesting, but a little bit too soft,
Verified Purchase(What's this?)
This review is from: Agile Testing: A Practical Guide for Testers and Agile Teams (Paperback)
I think this book is a little overhyped. Don't get me wrong. The book offers many interesting insights and experience reports about how testing can be organized by an agile team. However, in my opinion, much of them are "common sense" or were already explored in other sources (as some reviewers stated: "more about agile than agile testing"). For example, suggestions like "begin with the happy path", "put test stories on your backlog to make the test activities visible", "when working with legacy systems, create tests for the new features and, then, treat the old code in small steps" and "i (the tester) used to put candies on my table to attract programmers" are all interesting. But, at least for me, that wasn't *ONLY* what I was expecting for. Also, is that really new to someone that has experience with test or software? Another example of my expectations was about the beginning with test automation chapter. I really liked to be alerted to evaluate the ROI of what needs to be automated, but where are the details of inserting these activities in a team? What are the steps?
As a practical guide I was really expecting to see *DETAILED* examples of software testing in an agile context, distilled in steps or recommendations for its application in other contexts. I wouldn't be bothered if these examples weren't directly applicable to my context, but at least I would know how decisions were made and how they worked out. Overall, I was expecting much more technical content and even without all this the book managed to have 576 pages. Ok, again, maybe it was just my wrong expectations, but be advised to what you will get. If you are new to Agile you can read this book. Also, even if you are experienced, but want to refresh some good "common sense" practices it's a good read too. Otherwise, don't create many expectations as I did.
Sort: Oldest first | Newest first
Showing 1-3 of 3 posts in this discussion
Initial post: Sep 7, 2012 11:50:51 AM PDT
ravi tadwalkar says:
I don't agree with the reviewer. For really large waterfall-based enterprise product company, testing "departmental" teams go thru' a transition from having reactive departmental tester to proactive ATDD/BDD oriented embedded tester. I recommend chapter 5 of this book for road-shows with senior test management folks. I have always quoted this book over any other scrum book for test management folks.
Posted on Aug 1, 2013 10:41:37 AM PDT
Matt & Erin K. says:
Have you been able to find a good book that has the "details" you were looking for? I would be interested if you have.
Posted on Sep 21, 2013 3:43:31 PM PDT
Last edited by the author on Sep 21, 2013 3:48:28 PM PDT
John Clark says:
Yup, exactly what I was thinking. This book has been recommended to me by a fellow developer, which is working in a "Scrum company". It might be new stuff for devs, ITPLs, sophisticated testing personnel or in general "Management", but for a TM that started as TD/TA/TTA and before that worked as developer, it's not THE revelation/beacon. Nuff said, I am still looking for a good 'best practice' book on agile testing. But then, this might just be the iterative approach ;P
‹ Previous 1 Next ›