Chapter 2. Key process patterns
Specification by Example is a set of process patterns that facilitate change in software products to ensure the right product is delivered effectively. The key patterns that are commonly shared by the most successful teams that I interviewed in researching this book, along with their relationships, are shown in figure 2.1. Most of the teams implemented new process ideas by trial and error during their search for ways to build and maintain software more efficiently. By revealing the patterns in their processes, I hope to help others implement these ideas deliberately.
Why patterns?
The process ideas presented in this book make up patterns in the sense that they are recurring elements used by different teams; I am not referring to Christopher Alexander’s pattern definitions. Process ideas that I have cited occur in several different contexts and produce similar results. I haven’t documented the forces and changes expected in more traditional pattern books. Due in part to the case studies in this book, the Agile Alliance Functional Testing Tools group organized several pattern-writing workshops to document and build a catalog of patterns in a more traditional sense, but this work will take some time to complete. I’ve decided to leave expanding the patterns into a more traditional format for future editions of this book.