Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are the pros and cons of putting functional requirements into release/exit/ship criteria?

share|improve this question

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.

The answer is going to be 'it depends'. I've worked on projects that were full of all sorts of release criteria and others that basically had none apart from 'release the latest build on Friday' What sort of answer were you looking for and what problem are you trying to solve by asking this question? – Phil Kirkham Aug 14 '13 at 15:30
In some ways yes, since I have based Acceptance Tests on specific functionality being present, or in the case of a Sprint the sashime was the functionality. Echoing Phil a little bit, are you trying to answer a question on functional requirements are not release criteria in your organization or are you planning ahead? – MichaelF Aug 14 '13 at 18:17
I was trying to figure out whether it is a good idea to keep functional reqs in my release criteria document. Of course, different people may have different answers, but it is still valuable to hear their recommendations – oldbam Aug 16 '13 at 9:01

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.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.