The book will change the way that you look at requirements. It uses subtle humor and common sense to present and reinforce ideas. It's not a technical book and has something for everyone involved in product development.
The book is full of simple but important points:
Development is the process of transforming someones desires into a product that satisfies those desires.
The art of requirement process is not so much to provide answers as to raise new questions.
Instead of trying to compete ... on a feature-by-feature comparison ... identify the functions that will be needed to compete.
No single failure of requirements work leads to more lawsuits than the confident declaration, " No sane person would do that!"
Almost any real project, no matter how well planned and managed, contains a certain amount of hacking, because the real world always plays tricks on our assumptions.
The book is good at pointing out some of the more subtle parts of the process. For example, the types of requirements decisions:
- Choices - made directly and consciously
- Assumptions - made unconsciously through bias, error, or lack of information
- Impositions - forced by law, custom, or higher-authority
The requirements process begins with ambiguity. Gradually the ambiguity is removed, clarified, and/or constrained. Even though not all ambiguity can be removed, at some point "you decide you have enough agreement to move on into the design phase." This book will help you confidently deal with ambiguity and move on.