ABSTRACT
In the last 30 years, I have taught project management and requirements gathering to more than 25,000 people worldwide. In most of those classes, there has been discussion about why projects, especially information technology (IT) projects, fail. Inevitably, the number one reason comes back to unclear or changing requirements. When organizations try to address these problems, they often try for quick fixes such as buying new tools or hiring a consultant. However, it takes more than that. Good requirements do not come from a tool, or from a customer interview. They come from a repeatable set of processes that take the project from the early idea stage through to the creation of an agreed-upon project and product scope between the customer and the developer. This repeatable set of processes, and the tools and techniques that help execute them, are what I want to address in this book.
