BP-C.2: Identify product success criteria

This practice should be initiated at the requirements phase and then periodically re-iterated during subsequent phases.

The practice applies to all projects.

• 3.3. Determination of relevant quality characteristics
• 3.4. Quality assurance verification criteria

1. Identify relevant quality characteristics
   
   1. Review available software quality models for the relevant quality characteristics
   2. Discuss the relevant quality characteristics with the team
   3. Involve stakeholders in the discussion
   4. Assign priorities to the captured characteristics.
2. Identify test conditions that need to be verified
   
   1. Identify test conditions based on literature review, experience and/or brainstorming.
   2. Assign responsibility for maintaining the test condictions (to the Test Leader)
   3. Repeat the sessions of the test conditions discovery periodically

1. Stakeholders are not consulted
   
   1. Some characteristics relevant for the project are not properly covered
2. Priorities assigned to the characteristics and test conditions do not reflect actual needs
   
   1. Necessary trade-offs between priorities are not resolved adequately
3. Test conditions have not been correctly identified
   
   1. Conformance to the quality requirements is not properly verified

• BP-C.3: Elaborate and maintain quality plan for the project
• BP-C.6: Periodically validate the quality with project stakeholders