My Background: I'm a QA Director for a video game company that has been working on agile based teams for about 6 years.
I'm about half way through the book so far, but it really wasn't what I was expecting. I was looking for reading material to help new testers understand agile testing and good practices. Instead, so far this book seems to be more about convincing the reader to use agile instead of waterfall, so I can't relate to the intended audience.
There are some good sections in the book that I've highlighted to bring back to my team, but also some things that seemed based on opinion based and that I disagreed with.
If you are working in a badly managed waterfall environment, I'd recommend this book to arm you with reasons to switch to an agile methodology like scrum or kanban.
Agile Testing: A Practical Guide for Testers and Agile Teams 1st Edition
by
Lisa Crispin
(Author),
Janet Gregory
(Author)
|
Lisa Crispin
(Author)
Find all the books, read about the author, and more.
See search results for this author
|
|
Janet Gregory
(Author)
Find all the books, read about the author, and more.
See search results for this author
|
ISBN-13:
978-0321534460
ISBN-10:
9780321534460
Why is ISBN important?
ISBN
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Use the Amazon App to scan ISBNs and compare prices.
Add to book club
Loading your book clubs
There was a problem loading your book clubs. Please try again.
Not in a club?
Learn more
Join or create book clubs
Choose books together
Track your books
Bring your club to Amazon Book Clubs, start a new book club and invite your friends to join, or find a club that’s right for you for free.
In Stock.
Ships from and sold by Amazon.com.
More Buying Choices
Nolyn: The Rise and Fall, Book 1
In the depths of an unforgiving jungle, a legend is about to be born. Listen now
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
-
Apple
-
Android
-
Windows Phone
-
Android
|
Download to your computer
|
Kindle Cloud Reader
|
Frequently bought together
Customers who viewed this item also viewed
Page 1 of 1 Start overPage 1 of 1
What other items do customers buy after viewing this item?
Page 1 of 1 Start overPage 1 of 1
Editorial Reviews
Review
“As Agile methods have entered the mainstream, we’ve learned a lot about how the testing discipline fits into Agile projects. Lisa and Janet give us a solid look at what to do, and what to avoid, in Agile testing.”
–Ron Jeffries, www.XProgramming.com
“An excellent introduction to agile and how it affects the software test community!”
–Gerard Meszaros, Agile Practice Lead and Chief Test Strategist at Solution Frameworks, Inc., an agile coaching and lean software development consultancy
“In sports and music, people know the importance of practicing technique until it becomes a part of the way they do things. This book is about some of the most fundamental techniques in software development–how to build quality into code–techniques that should become second nature to every development team. The book provides both broad and in-depth coverage of how to move testing to the front of the development process, along with a liberal sprinkling of real-life examples that bring the book to life.”
–Mary Poppendieck, Author of Lean Software Development and Implementing Lean Software Development
“Refreshingly pragmatic. Chock-full of wisdom. Absent of dogma. This book is a gamechanger. Every software professional should read it.”
–Uncle Bob Martin, Object Mentor, Inc.
“With Agile Testing, Lisa and Janet have used their holistic sensibility of testing to describe a culture shift for testers and teams willing to elevate their test effectiveness. The combination of real-life project experiences and specific techniques provide an excellent way to learn and adapt to continually changing project needs.”
–Adam Geras, M.Sc. Developer-Tester, Ideaca Knowledge Services
“On Agile projects, everyone seems to ask, ‘But, what about testing?’ Is it the development team’s responsibility entirely, the testing team, or a collaborative effort between developers and testers? Or, ‘How much testing should we automate?’ Lisa and Janet have written a book that finally answers these types of questions and more! Whether you’re a tester, developer, or manager, you’ll learn many great examples and stories from the real-world work experiences they’ve shared in this excellent book.”
–Paul Duvall, CTO of Stelligent and co-author of Continuous Integration: Improving Software Quality and Reducing Risk
“Finally a book for testers on Agile teams that acknowledges there is not just one right way! Agile Testing provides comprehensive coverage of the issues testers face when they move to Agile: from tools and metrics to roles and process. Illustrated with numerous stories and examples from many contributors, it gives a clear picture of what successful Agile testers are doing today.”
–Bret Pettichord, Chief Technical Officer of WatirCraft and Lead Developer of Watir
–Ron Jeffries, www.XProgramming.com
“An excellent introduction to agile and how it affects the software test community!”
–Gerard Meszaros, Agile Practice Lead and Chief Test Strategist at Solution Frameworks, Inc., an agile coaching and lean software development consultancy
“In sports and music, people know the importance of practicing technique until it becomes a part of the way they do things. This book is about some of the most fundamental techniques in software development–how to build quality into code–techniques that should become second nature to every development team. The book provides both broad and in-depth coverage of how to move testing to the front of the development process, along with a liberal sprinkling of real-life examples that bring the book to life.”
–Mary Poppendieck, Author of Lean Software Development and Implementing Lean Software Development
“Refreshingly pragmatic. Chock-full of wisdom. Absent of dogma. This book is a gamechanger. Every software professional should read it.”
–Uncle Bob Martin, Object Mentor, Inc.
“With Agile Testing, Lisa and Janet have used their holistic sensibility of testing to describe a culture shift for testers and teams willing to elevate their test effectiveness. The combination of real-life project experiences and specific techniques provide an excellent way to learn and adapt to continually changing project needs.”
–Adam Geras, M.Sc. Developer-Tester, Ideaca Knowledge Services
“On Agile projects, everyone seems to ask, ‘But, what about testing?’ Is it the development team’s responsibility entirely, the testing team, or a collaborative effort between developers and testers? Or, ‘How much testing should we automate?’ Lisa and Janet have written a book that finally answers these types of questions and more! Whether you’re a tester, developer, or manager, you’ll learn many great examples and stories from the real-world work experiences they’ve shared in this excellent book.”
–Paul Duvall, CTO of Stelligent and co-author of Continuous Integration: Improving Software Quality and Reducing Risk
“Finally a book for testers on Agile teams that acknowledges there is not just one right way! Agile Testing provides comprehensive coverage of the issues testers face when they move to Agile: from tools and metrics to roles and process. Illustrated with numerous stories and examples from many contributors, it gives a clear picture of what successful Agile testers are doing today.”
–Bret Pettichord, Chief Technical Officer of WatirCraft and Lead Developer of Watir
From the Back Cover
Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester’s function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an “agile tester?”
Two of the industry’s most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester’s role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors
of agile testing.
Readers will come away from this book understanding
Two of the industry’s most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester’s role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors
of agile testing.
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
About the Author
Lisa Crispin is dedicated to helping agile teams and testers discover good ways to deliver the best possible product. She specializes in showing testers and agile teams how testers can add value and how to guide development with business-facing tests. Since 2003, she’s been a tester on a Scrum/XP team at ePlan Services, Inc., and frequently leads tutorials and workshops on agile testing at conferences. Lisa regularly contributes articles about agile testing to publications such as Better Software magazine, I EEE Software, and Methods and Tools. Lisa also coauthored Testing Extreme Programming (Addison-Wesley, 2002) with Tip House.
Janet Gregory is the founder of DragonFire, Inc., an agile quality process consultancy and training firm. Her passion is helping teams build quality systems. Since 1998, she has worked as a coach and tester introducing agile practices into both large and small companies. Her focus is working with business users and testers to understand their role in agile projects. Janet is a frequent speaker at agile and testing software conferences, and she is a major contributor to the North American agile testing community.
Janet Gregory is the founder of DragonFire, Inc., an agile quality process consultancy and training firm. Her passion is helping teams build quality systems. Since 1998, she has worked as a coach and tester introducing agile practices into both large and small companies. Her focus is working with business users and testers to understand their role in agile projects. Janet is a frequent speaker at agile and testing software conferences, and she is a major contributor to the North American agile testing community.
Start reading Agile Testing on your Kindle in under a minute.
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product details
- ASIN : 0321534468
- Publisher : Addison-Wesley Professional; 1st edition (December 30, 2008)
- Language : English
- Paperback : 576 pages
- ISBN-10 : 9780321534460
- ISBN-13 : 978-0321534460
- Item Weight : 2.1 pounds
- Dimensions : 7 x 1.3 x 9.3 inches
-
Best Sellers Rank:
#426,985 in Books (See Top 100 in Books)
- #195 in Software Testing
- #366 in Software Design & Engineering
- #828 in Software Development (Books)
- Customer Reviews:
Customer reviews
4.4 out of 5 stars
4.4 out of 5
212 global ratings
How are ratings calculated?
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzes reviews to verify trustworthiness.
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Reviewed in the United States on February 21, 2015
Verified Purchase
43 people found this helpful
Report abuse
Reviewed in the United States on September 18, 2013
Verified Purchase
Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and Janet Gregory is an invaluable resource for testers who are or will be making the transition from traditional waterfall testing to testing in a Scrum, XP, or other agile development methodology. This book is comprehensive in its treatment of the subject. It contains a great set of chapters that describe a tester's role through the stages of an agile project, but it is more than a mere blueprint or paint-by-numbers account.
Before they get to that point, they help readers understand common organizational issues that hinder the transition to agile. They elaborate on the implications of the Agile Manifesto to how individuals, teams, and organizations operate. It is not ivory tower wisdom from above either, but it is rather hard fought, experienced based observations that will help novices avoid some of the potential growing pains. In addition, they give a solid taxonomy of test covering functional and non-functional. They address what types of testing to automate and when. Finally, they spend two chapters in detail on automation strategy and implementation. At regular intervals, readers see either "Lisa's Story" or "Janet's Story" that details with the concept being discussed. These either tell what worked well or how they overcame specific challenges.
I found Crispin and Gregory had a very accessible writing style, and they do a great job of getting their point across. If you are a traditional tester who is unsure or even afraid of moving into the agile world, this is the book that you need. They tackle the tough questions that most people have one by one with answers that can be put in practice. I plan to use the wisdom of this book in helping my testing organization make the transition. I highly recommend this book.
Overall: A
Before they get to that point, they help readers understand common organizational issues that hinder the transition to agile. They elaborate on the implications of the Agile Manifesto to how individuals, teams, and organizations operate. It is not ivory tower wisdom from above either, but it is rather hard fought, experienced based observations that will help novices avoid some of the potential growing pains. In addition, they give a solid taxonomy of test covering functional and non-functional. They address what types of testing to automate and when. Finally, they spend two chapters in detail on automation strategy and implementation. At regular intervals, readers see either "Lisa's Story" or "Janet's Story" that details with the concept being discussed. These either tell what worked well or how they overcame specific challenges.
I found Crispin and Gregory had a very accessible writing style, and they do a great job of getting their point across. If you are a traditional tester who is unsure or even afraid of moving into the agile world, this is the book that you need. They tackle the tough questions that most people have one by one with answers that can be put in practice. I plan to use the wisdom of this book in helping my testing organization make the transition. I highly recommend this book.
Overall: A
3 people found this helpful
Report abuse
Reviewed in the United States on June 25, 2013
Verified Purchase
I picked up this book when I took a job that required building a QA team from the ground up in an agile development environment that had already been developing for six months.
I say that because the usefulness of this book has a lot to do with your organization, and what your starting point is. If you are working on a development team starting from scratch then this is a must read for any lead or manager involved. There is a ton of high level conceptual information in here that will help you draw out an outline of what you need to think about in terms of testing over the next few months. This runs from what broad categories needs to be tested (Security, -ility, GUI, etc.) to who is responsible for automation (Unit test, API testing, etc.). I can honestly say that sticking to these concepts will help you make a better product faster.
Here's the downside. If you are coming in midway through a project then get ready for the battle of a lifetime getting this stuff implemented no matter how much sense it makes. Unit testing, as an example, is constantly brought up throughout the book, and that is not something that you can get up and going with a snap of your fingers. Especially if you have to educate development on how to do it. This book provides little support in that sort of area, and, honestly, that is most likely the scenario that most people in QA will run into. I have been in QA for ten years, and every place I have worked either had no unit testing at all or the had just enough to claim that they did.
The reality is that Agile Testing in this book equates to Test Driven Development with QA support. That mean QA is responsible for a lot of solution, end to end, and customer requirement verification testing, but very little feature and functionality testing since that is expected to be done in unit testing. If you are in QA and you need to read this book then you almost certainly do no have that already, and need a book that tells you how to do it.
So, anyways, this book is worth reading if you are just starting out, but make sure you are reading it with development and project management as well. If you are not just starting out then In my opinion these steps are required:
1. Get acceptance from Management, Dev, and Project Management that your current model is not sustainable, and that resources will be allocated to changing that.
2. Read this book with all of those involved.
3. Meet up and list out what the book recommends, where you are strong, and where you are weak.
4. Use that as a starting point to find other books and resources to strengthen up your weak points.
5. Make sure that management makes the success of these changes part of everyone's job responsibility, and emphasizes it as part of performance evaluations. Period.
In my experience, if you can't get the five steps above completed then you might as well throw this book out the window, because you'll waste a bunch of time implementing QA practices that will fail miserably due to their reliance on a non existant foundation. Step five is the real key. Otherwise you get one of the following:
1. "Great Idea!" with no action following
2. "You're right, we need these changes," and then an expectation that QA will be responsible for all of them. Including things like forcing individual dev's to do unit testing.
The weakness in the book is that it doesn't really address the needs of QA in terms of helping you get through those five steps.
If you use this book as a planning tool then you will be in good shape and the value is absolutely there. It is a quick and easy read, gets the concepts across in a way that pretty much anyone can understand, and does so convincingly. Just don't go in expecting it to answer all your problems without some supplemental reading. You will need to read up on automation and unit testing frameworks and test driven development.
I say that because the usefulness of this book has a lot to do with your organization, and what your starting point is. If you are working on a development team starting from scratch then this is a must read for any lead or manager involved. There is a ton of high level conceptual information in here that will help you draw out an outline of what you need to think about in terms of testing over the next few months. This runs from what broad categories needs to be tested (Security, -ility, GUI, etc.) to who is responsible for automation (Unit test, API testing, etc.). I can honestly say that sticking to these concepts will help you make a better product faster.
Here's the downside. If you are coming in midway through a project then get ready for the battle of a lifetime getting this stuff implemented no matter how much sense it makes. Unit testing, as an example, is constantly brought up throughout the book, and that is not something that you can get up and going with a snap of your fingers. Especially if you have to educate development on how to do it. This book provides little support in that sort of area, and, honestly, that is most likely the scenario that most people in QA will run into. I have been in QA for ten years, and every place I have worked either had no unit testing at all or the had just enough to claim that they did.
The reality is that Agile Testing in this book equates to Test Driven Development with QA support. That mean QA is responsible for a lot of solution, end to end, and customer requirement verification testing, but very little feature and functionality testing since that is expected to be done in unit testing. If you are in QA and you need to read this book then you almost certainly do no have that already, and need a book that tells you how to do it.
So, anyways, this book is worth reading if you are just starting out, but make sure you are reading it with development and project management as well. If you are not just starting out then In my opinion these steps are required:
1. Get acceptance from Management, Dev, and Project Management that your current model is not sustainable, and that resources will be allocated to changing that.
2. Read this book with all of those involved.
3. Meet up and list out what the book recommends, where you are strong, and where you are weak.
4. Use that as a starting point to find other books and resources to strengthen up your weak points.
5. Make sure that management makes the success of these changes part of everyone's job responsibility, and emphasizes it as part of performance evaluations. Period.
In my experience, if you can't get the five steps above completed then you might as well throw this book out the window, because you'll waste a bunch of time implementing QA practices that will fail miserably due to their reliance on a non existant foundation. Step five is the real key. Otherwise you get one of the following:
1. "Great Idea!" with no action following
2. "You're right, we need these changes," and then an expectation that QA will be responsible for all of them. Including things like forcing individual dev's to do unit testing.
The weakness in the book is that it doesn't really address the needs of QA in terms of helping you get through those five steps.
If you use this book as a planning tool then you will be in good shape and the value is absolutely there. It is a quick and easy read, gets the concepts across in a way that pretty much anyone can understand, and does so convincingly. Just don't go in expecting it to answer all your problems without some supplemental reading. You will need to read up on automation and unit testing frameworks and test driven development.
11 people found this helpful
Report abuse
Reviewed in the United States on May 1, 2020
Verified Purchase
This book title is misleading. It is not a practical guide. Quite the opposite, It is just a collection of short testing methodology overviews. I hated this book. It is a waste of time. Do not get it if you are looking for some practical development testing book.
Reviewed in the United States on August 21, 2009
Verified Purchase
How delightful that two of the agile community's "rock stars" of testing have teamed up to write the guide that every agile team member needs on agile testing!
Chock-full of side stories, examples, wisdom points, and handy chapter mind maps, the authors cover the entire range of possible topics you need to know about agile testing. This book will serve your team well and is an excellent book to include as part of your team's community of practice book club.
In addition, I urge all business analysts moving to agile to get this book. Business analysts need to extend their skills and knowledge into the testing arena. With guidance from Lisa and Janet, you'll see how the testing mind set truly drives development to deliver value.
Chock-full of side stories, examples, wisdom points, and handy chapter mind maps, the authors cover the entire range of possible topics you need to know about agile testing. This book will serve your team well and is an excellent book to include as part of your team's community of practice book club.
In addition, I urge all business analysts moving to agile to get this book. Business analysts need to extend their skills and knowledge into the testing arena. With guidance from Lisa and Janet, you'll see how the testing mind set truly drives development to deliver value.
4 people found this helpful
Report abuse
Top reviews from other countries
D. Murphy
4.0 out of 5 stars
Very good, but somewhat dated now
Reviewed in the United Kingdom on December 2, 2019Verified Purchase
I'd still recommend getting it if you are new to agile and especially agile testing, But the industry has moved on and automation of tests, fully tied into the pipeline with tools such as Gauge, is increasingly normal. One of my recent projects we had one QA with our team of ten staff. She defined the testing and did the gauge scripts but develp[ers automated the scripts. The tests were built into the pipeline (GoCD). We also automated performance testing via Gattling. However, since then, I have found organisations seriously behind on this so there is still plenty of mileage in this book.
One person found this helpful
Report abuse
Mrs A
5.0 out of 5 stars
Great Agile Testing Book
Reviewed in the United Kingdom on October 1, 2019Verified Purchase
I thoroughly enjoyed reading this book! It contains a lot of the examples that I could relate to and gave me some ideas on how to improve in my own agile team. I'm a software developer with a keen interest in testing so it really helped me to understand how software testing fits within the agile process.
One person found this helpful
Report abuse
F Reavley
5.0 out of 5 stars
Excellent book, well thought-out (or tested) of course!
Reviewed in the United Kingdom on August 21, 2009Verified Purchase
I bought this book as it appeared to focus more on the testing angle of 'AGILE' software development rather than the developers, and I have enjoyed reading this immensely.
Not only have the authors laid the book out well, and have made it very readable, they have garnished the chapters with mind-maps and therefore made it very easy to find and review sections you want to read again.
The two authors clearly have had plenty of experience in the AGILE development environment, both on 'disorganised' and 'organised' teams, and are keen to promote how to turn a newbie agile team into an effective one, stressing the collaborative nature for AGILE. Lots of examples from their own experience and from other AGILE practitioners demonstrate the pitfalls and improvements which can be made by thinking about the points made in the book.
As a tester, I found this book very useful in describing how and where testers fit into the process, and how specialist testers can work to enhance things too, especially where views of testing have previously been that "it's done at the end", or that "anyone can test", or that "we'll let the testers know about the development work when (we consider) they need to".
I would recommend this book both to software developers, and to testers, as it can teach everyone a lot about how to get everyone focused on the right goals, improving quality, and meeting customer expectations, and keeping the so-called 'technical debt' of difficult-to-maintain code at bay. The more it's done from the word go, the easier it should be.
Not only have the authors laid the book out well, and have made it very readable, they have garnished the chapters with mind-maps and therefore made it very easy to find and review sections you want to read again.
The two authors clearly have had plenty of experience in the AGILE development environment, both on 'disorganised' and 'organised' teams, and are keen to promote how to turn a newbie agile team into an effective one, stressing the collaborative nature for AGILE. Lots of examples from their own experience and from other AGILE practitioners demonstrate the pitfalls and improvements which can be made by thinking about the points made in the book.
As a tester, I found this book very useful in describing how and where testers fit into the process, and how specialist testers can work to enhance things too, especially where views of testing have previously been that "it's done at the end", or that "anyone can test", or that "we'll let the testers know about the development work when (we consider) they need to".
I would recommend this book both to software developers, and to testers, as it can teach everyone a lot about how to get everyone focused on the right goals, improving quality, and meeting customer expectations, and keeping the so-called 'technical debt' of difficult-to-maintain code at bay. The more it's done from the word go, the easier it should be.
14 people found this helpful
Report abuse
Testing Testing 123 Testing
5.0 out of 5 stars
Invaluable read when approaching Agile test methodologies
Reviewed in the United Kingdom on July 3, 2011Verified Purchase
I had read recommendations for this book on various Agile user groups and I am glad I went for it. I had a fair idea of what Agile was, how it should work/be applied etc, and had been on a good 3 day workshop. But reality is very different. This book was a brilliant buy. We had decided to approach a project using iterative dev and testing methods, and I was so relieved to have this book alongside me, even if no one else followed 'the rules' I tried my best and it helpd enormously. Also helped to highlight the gaps in other areas of dev that were 'supposed' to be going the 'Agile' way. Hopefully I have learnt some good habbits I can apply on the next project or elsewhere. A must read for anyone new to Agile testing methodoligies or trying to convince others what should be happening. I also highly recommend Agile Estimating and Planning
Agile Estimating and Planning
brilliant for undertsanding scope and estimating.
Tony James
5.0 out of 5 stars
Learn from those with a lifetime of experience in Agile software testing
Reviewed in the United Kingdom on January 4, 2017Verified Purchase
I found this book very helpful - as someone that has been in software development for about 30 years and only recently started working in an Agile team (in which we all work on design, implementation and tests) - I found it gave me a much better insight into how to use different kinds of testing, when to automate and when not to, and many other facets of Agile Testing.
I really liked the recounting of stories experienced by the authors - the problems they had and how they tackled them.
The whole book has the feel of wisdom gained from a lifetime of experience with software testing in an Agile environment.
I really liked the recounting of stories experienced by the authors - the problems they had and how they tackled them.
The whole book has the feel of wisdom gained from a lifetime of experience with software testing in an Agile environment.
One person found this helpful
Report abuse
Customers who bought this item also bought
Page 1 of 1 Start overPage 1 of 1
Pages with related products.
See and discover other items: agile development, red team, software test, software quality assurance, unit testing, In Testing














