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 into your entire development system: the way your team approaches its work, the way people think about mistakes, and even the way your organization interacts with your team.
This chapter has three practices to help your team dedicate itself to quality:
“No Bugs” builds quality in.
“Blind Spot Discovery” helps team members learn what they don’t know.
“Incident Analysis” focuses your team on systemic improvements.
1 I haven’t been able to find a definitive source for the origins of Chaos Engineering. It was formalized by Casey Rosenthal’s “Chaos Team” at Netflix in 2015, but the underlying ideas predate that team by several years. The original tool was Chaos Monkey, which [Dumiak2021] attributes to “Orzell and his Netflix colleagues.” US patent US20120072571A1, applied for in 2010, lists Greg Orzell and Yury Izrailevsky as the inventors.