View all services
Talk to QA Advisor
Browse the Knowledge Hub211 resources
/Books/More Agile Testing
Books · Honest notes

More Agile Testing: is it worth reading?

The sequel, covering what the first book left out: scaling, distributed teams, and testing beyond the functional.

We earn nothing from any link on this page. No affiliate links anywhere in this library.

published
2014
key ideas
3
reading path
1

Reviewed by Viral Patel

Co-Founder, QAble

Cover of More Agile Testing
Agile testing

More Agile Testing

Learning Journeys for the Whole Team

by Janet Gregory, Lisa Crispin

Publisher
Addison-Wesley
Year
2014
ISBN
9780321967053

Useful when you are: Senior / lead, Manager

Verdict

Should you read it?

Read it if

You have read the first book, or you already work this way, and you are now hitting the scaling and non-functional questions it did not cover.

Skip it if

You are new to agile testing. Start with Agile Testing Condensed, then this. Reading this first is confusing because it assumes the first book.

The argument

What it argues

The follow-up addresses the questions the first book raised and did not answer. How testing works across several teams rather than one. How distributed and offshore teams handle the collaboration the approach depends on. How performance, security and accessibility fit into an iterative cycle rather than being deferred to a phase that no longer exists.

It also covers the testing role itself more directly: what a tester career looks like in an agile organisation, how testing skills are developed, and what happens to testers whose work was predominantly manual regression.

Structured as learning journeys with contributed experience reports rather than as a single argument, which makes it a better reference than a read-through.

Key ideas

Ideas worth taking from it

  1. 01

    Testing in scaled agile

    The hard problems move to the boundaries between teams, where integration, end-to-end journeys and shared environments belong to nobody in particular.

  2. 02

    Non-functional testing in iterations

    Performance, security and accessibility attached to the stories where they matter rather than deferred to a hardening phase, which is the usual reason they get dropped entirely.

  3. 03

    The changing tester role

    What happens to a testing career when manual regression is automated, and what the remaining work actually is.

Criticism

What has dated, and what it gets wrong

The experience-report structure makes it uneven, since contributed sections vary considerably in quality and depth. It is also a difficult book to read straight through, and works better consulted on a specific question.

Reading paths

On our reading paths

From tester to test lead

Book 2 of 5 · Moving into a lead role

Picks up where Agile Testing stops, with the problems of leading testing across several teams, distributed groups and organisational change.

  1. Cover of Perfect Software1. Perfect Software
  2. Cover of More Agile Testing2. More Agile Testing (this book)
  3. Cover of Fifty Quick Ideas to Improve Your Tests3. Fifty Quick Ideas to Improve Your Tests
  4. Cover of How Google Tests Software4. How Google Tests Software
  5. Cover of Accelerate5. Accelerate

Keep reading

What to read next

Ready

Reading about quality is cheaper than learning it in production.

QAble runs QA for products in BFSI, gaming, healthcare and SaaS, with engineers who have read these and argued about them. Start with a free QA audit.

Talk to QA Advisor