For More Information
Boehm and Basili (2001) summarize 10 ways to reduce defects in code, including peer reviews and perspective-based reviews (such as using scenarios to walk through your requirements).
Boehm and Hoh (1999) describe a technique for analyzing and negotiating conflicts in requirements.
Brooks (1995), a classic on the human aspects of software engineering, points out that eliciting requirements is the most difficult part of building software. The author emphasizes the need to continually refine and iterate requirements with customers.
Buzan (1989) provides insights and techniques, based on research on the human brain, for tapping into the right and left sides of our brains.
Cockburn (2001) presents wisdom on how software teams work best. Chapter 4, on methodologies, provides an excellent discussion on how you must tailor your methodology for each project, including the types of work products and their precision.
Cohen (1995) provides a step-by-step guide to quality function deployment (QFD), a systematic methodology for deriving and evaluating product features from both customer and designer points of view. The key technique, the "voice of the customer," is explained along with Kano's understanding of quality from the customer's perspective.
Chapter 9 of Highsmith (2000) discusses workstate lifecycle management, in which teams iteratively deliver components (from requirements to code and tests) in a predefined state, rather than focus on workflow.
Howell (1995) is a useful reference for a variety of visual tools you can adapt for your supplemental workshop deliverables. Included are tools for representing text information in provocative and interesting ways, such as circles, continuums, workflows, t-charts, and a variety of worksheets.