AoAD2 Chapter: Quality (introduction)

Book cover for “The Art of Agile Development, Second Edition.”

Second Edition cover

This is a pre-release excerpt of The Art of Agile Development, Second Edition, to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more.

Your feedback is appreciated! To share your thoughts, join the AoAD2 open review mailing list.

This excerpt is copyright 2007, 2020, 2021 by James Shore and Shane Warden. Although you are welcome to share this link, do not distribute or republish the content without James Shore’s express written permission.

Quality

For many people, “quality” means “testing,” but Agile teams treat quality differently. Quality isn’t something you test for; it’s something you build in. Not just into your code, but your entire development system: the way your team approaches its work, the way people think about mistakes, and even the constraints imposed by your organization.

This chapter has three practices to help your team dedicate itself to quality:

  • “No Bugs” on p.XX helps your team build quality in.

  • “Blind Spot Discovery” on p.XX help your team learn what it doesn’t know.

  • “Incident Analysis” on p.XX focuses the team on systemic improvements.

They’re supported by these key ideas:

  • “Key Idea: Build Quality in” on p.XX: Focusing on quality from the beginning is cheaper, faster, and better.

  • “Key Idea: Embrace Failure” on p.XX: Failure is inevitable, but it doesn’t have to prevent success.

Share your feedback about this excerpt on the AoAD2 mailing list! Sign up here.

For more excerpts from the book, or to get a copy of the Early Release, see the Second Edition home page.

If you liked this entry, check out my best writing and presentations, and consider subscribing to updates by email or RSS.