BP-A.3: Collect requirements

The practice applies to all projects. If the needs of stakeholders have not been identified previously, then this practice becomes the core part of the requirements elicitation strategy.

• 1.3. Analysis of requirements and their dependencies
• 1.4. Traceability of requirements
• 1.5. Validation of requirements

1. Formulate requirements based on the needs expressed by the stakeholders
   
   1. Each requirement reflects a single feature or constraint of the system
   2. Identify dependencies among the needs expressed by different stakeholders and reconcile them before defining requirements.
   3. Identify dependencies between the identified requirements
   4. Define testable verification criteria for each requirement
   5. Define and manage priorities for the requirements (in collaboration with stakeholders)
2. Maintain and manage traceability links between requirements and the needs
3. Use tools to support the management of requirements
   1. Give priority to the tools available and supported within the organization (Jira, wiki)
   2. If possible, use the versioning and dependency-tracking capabilities of the tool
4. Validate the requirements with stakeholders
   1. Obtain explicit approval from the key stakeholders, and at least implicit approval from the remaining ones

1. Requirements are not verifiable
   1. Requirements cannot be translated into test conditions/test cases
   2. The progress of the project cannot be appropriately tracked
   3. Feature regression is likely to happen.
2. Requirements cannot be traced back to the needs of stakeholders
   1. Stakeholders may lose orientation in the project's priorities and key directions
   2. Some requirements may become orphaned and not backed by the stakeholders
   3. Some needs may not be addressed appropriately by the requirements

• BP-A.1: Identify stakeholders
• BP-A.2: Establish communications with stakeholders