Before we delve into the details of the patterns and how to adopt and adapt them to meet your goals, some introductory material is in order.
A pattern describes a particular problem and its solution context. Specifically in this book, a pattern describes a (set of) problematic situation(s) on a development team that can be fixed by applying an Agile practice. Patterns are to be trusted because each one has been used several times on real development teams and projects. Patterns are not one-off solutions or good ideas that might or might not work. Patterns are discovered, not created.
The pattern format used in this book is as follows:
Name. The name of the pattern.