Review the business case, and the project goals and objectives
Collaborate in the development of project goals and objectives by providing clarification of business needs and solution scope
Select methods for requirements change control by identifying channels for communicating requests and processes for managing changes
Develop requirements management plan by identifying stakeholders, roles and responsibilities, communication protocols, and methods for eliciting,
Select methods for document control by using documentation management tools and techniques
Identify stakeholders by reviewing goals, objectives, and requirements
Define strategy for requirements traceability using traceability tools and techniques
Define or review a business problem or opportunity using problem and opportunity analysis techniques
Collect and analyze information from a variety of sources using valuation tools and techniques
Determine stakeholder values regarding the product, using elicitation techniques
Define business metrics and acceptance criteria by collaborating with stakeholders
in order to establish a roadmap for delivering the expected solution.
to contribute to determining the value proposition of the initiative.
in order to establish a standard for requirements traceability and versioning.
in order to provide a baseline for prioritizing requirements
in order to develop a solution scope statement and/or to provide input to create a business case.
in order to provide context for business analysis activities.
in order to align the product with the organization’s goals and objectives.
in order to establish the level of traceability necessary to monitor and validate the requirements.
in order that the appropriate parties are represented, informed and involved.
in order to establish standard protocols for incorporation into the change management plan.
for use in evaluating when the solution meets the requirements
Validate requirements using tools and techniques such as documentation review, prototypes, demos, and other validation methods
Update a requirement’s status by communicating with appropriate stakeholders and recording changes in the traceability artifact or tool
Manage changes to requirements by assessing impacts and risks in accordance with the change control plan, and comparing to the requirements baseline
Communicate requirements status to project manager and other stakeholders using communication methods
Elaborate and specify detailed metrics and acceptance criteria using measurement tools and techniques
Allocate accepted or deferred requirements by balancing scope schedule, budget, and resource constraints with the value proposition
Monitor requirements throughout their lifecycles using a traceability artifact or tool
Elicit or identify requirements, using individual and group elicitation techniques
Write requirements specifications using process (such as use cases, user stories), data, and interface details
Track requirements using a traceability artifact or tools, capturing the requirements' status, sources and relationships (including dependencies),
Obtain sign-off on requirements baseline using decision-making techniques
Analyze, decompose, and elaborate requirements using techniques such as dependency analysis, interface analysis, and data and process modeling
Evaluate product options and capabilities by using decision-making and valuation techniques
in order to collaboratively uncover and clarify product options and capabilities.
in order to maintain the integrity of the requirements and associated artifacts.
using prioritization, dependency analysis, and decision-making tools and techniques in order to create a requirements baseline.
in order to ensure the appropriate supporting requirements artifacts are produced, reviewed and approved at each point in the lifecycle.
in order to communicate requirements that are measurable and actionable (that is, suitable for development).
for use in evaluating whether the solution meets requirements.
in order to provide evidence that the requirements are delivered as stated.
in order to keep them informed of requirements issues, conflicts, changes, risks, and overall status.
in order to track requirements towards closure.
in order to ensure requirements are complete, accurate and aligned with goals, objectives, and value proposition.
in order to determine which requirements are accepted, deferred, or rejected.
in order to facilitate stakeholder consensus and achieve stakeholder approval.
in order to discover and capture requirements with supporting details (e.g., origin and rationale).
Obtain stakeholder sign-off on the developed solution using decision-making techniques
Validate the solution's test results, reports, and other test evidence against the requirements acceptance criteria
Analyze and communicate the solution's identified gaps and deltas using quality assurance tools and methods
Evaluate the deployed solution using valuation techniques
in order to enable stakeholders to resolve discrepancies between solution scope, requirements, and developed solution.
in order to determine how well the solution meets the business case and value proposition.
in order to proceed with deployment
in order to determine whether the solution satisfies the requirements.