14. Reviewing the Specification
in which we decide whether our specification is correct and complete, and set the priorities of the requirements
At some stage in your requirements process, you will want to release your specification. It does not have to be complete at this stage: it could be a partial version for the next iteration; a version of the specification you want to publish for marketing reasons; or any other version. But before releasing the specification, you need to review it.
We use the term “specification” here to mean whatever collection of requirements you have. It does not have to be a paper specification. It does not even have to be formal; it could be a blog, wiki, or something similar. It might hold only the requirements ...