Transform stakeholder needs, expectations, constraints, and interfaces into prioritized customer requirements.
Translate stakeholder needs, expectations, constraints, and interfaces into documented customer requirements.
The various inputs from the relevant stakeholders should be consolidated, missing information should be obtained, and conflicts should be resolved as customer requirements are developed and prioritized. The customer requirements can include needs, expectations, and constraints with regard to verification and validation.
In some situations, the customer provides a set of requirements to the project, or the requirements exist as an output of a previous project’s activities. In these situations, the customer requirements could conflict with the relevant stakeholders’ needs, expectations, constraints, and interfaces and will need to be transformed into the recognized set of customer requirements after appropriate resolution of conflicts.
Relevant stakeholders representing all phases of the product’s lifecycle should include business as well as technical functions. In this way, concepts for all product related lifecycle processes are considered concurrently with the concepts for the products. Customer requirements result from informed decisions on the business as well as technical effects of their requirements.
Complete Customer Requirements Document
Using the Baseline Project Charter and the Draft Customer Requirements Document, [the Business Analyst] consulting with [the Product Owner] is responsible for Translating stakeholders needs, expectations, constraints, and interfaces into documented customer requirements.
Create Requirements Traceability Matrix
Using the Requirements Traceability Matrix Template and the Draft Customer Requirements Document, [the Business Analyst] is responsible for creating the Requirements Traceability Matrix.