What are the pros and cons of putting functional requirements into release/exit/ship criteria?
closed as primarily opinion-based by Bruce McLeod♦ Aug 15 '13 at 4:30
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
In our organizations, functional requirements are usually too detailed to list each one as separate or specific release criteria.
Functional requirements usually stem from user stories or scenarios, so we might list all user stories / scenarios pass as part of our exit criteria.
Exit criteria is usually derived from high level data points (quantitative) that are critical factors for success in the marketplace, as well as a qualitative assessment of the product and other information.