Examples of mistakes, manifestations, and problems help us understand all parts of the software. Brian Marick suggests Web resources that examine software failures.

Errors start with individuals, and a primary job of testers/QA people is to prevent those errors in the first place. But an equally important part of the job is to find them once they are there, understanding that errors will happen. Jon Hagar asks, "What can we do personally, above and beyond the normal day-to-day jobs that we testers and developers have?"

Johanna Rothman recommends the book Adaptive Software Development by James Highsmith. She says, "Highsmith shows the reader how to recognize when development practices need to change and how to acquire the skills to adapt. For a fresh approach to software development, be sure to check it out."

The kind of collaboration that Extreme Programming engenders can benefit both publications and development. Writing, like programming, is a naturally iterative, revisionary process. Dana De Witt Luther shares what she's learned about documenting an Extreme Programming project, using iterative planning meetings and story cards.