13. The Quality Gateway
in which we prevent unsuitable requirements from becoming part of the specification
Consider how requirements come about. It isn’t exactly random—we give you trawling techniques to help with your elicitation—and it isn’t exactly badly formed—we give you a template and a snow card to help formulate your requirements. But the requirement comes from people who are not always sure of what they need, are not always able to explain what it is that they want, and it cannot always be carefully written so it is unambiguous and complete.
Here is the point of doing requirements: You have to ensure that what is handed to the developers is a precise, complete, and unambiguous statement of the real need. Anything less negates the reason ...