Manage requirements changes
Purpose: To effectively manage requirements changes.
Stakeholders: Requirements engineer, PM, Domain SME, Sponsor.
Inputs
Elements
Outputs
1. Requirements
1. Record requirements changes.
1.
changes.
2. Determine if change is acceptable as per
project change management policy.
3. Propose change to change control board.
4. Update requirements documents once change
is accepted.
Tools and Techniques: Requirements Change management, Problem / Issue Tracker, Brain storming.
Manage solution scope, and requirements
Purpose: To obtain, and maintain consensus among key stakeholders about overall solution scope, and the
requirements that will be implemented.
Stakeholders: Domain SME, Implementation SME, Sponsor, and Project manager.
Inputs
Elements
Outputs
1. Requirements management
1. Manage solution scope.
1. Requirements
plan.
2. Manage conflicts, and issues.
[Approved].
2. Solution scope.
3. Present requirements for
3. Stakeholder list, roles, and
review.
responsibilities.
4. Obtain approval on
4. Stakeholder, solution, or
requirements.
transition requirements.
[Communicated or Traced]
Tools and Techniques: General techniques, Baselining, Sign-off.
4.1.2 Description
 Secure approval of requirements from stakeholders with appropriate authority.
 Manage issues that emerge during elicitation, and analysis by tracking them in Problem tracker.
 Seek approval of requirements at the end of a project phase or at intermediate points.
1.
2.
3.
4.
Baseline requirements after approval.
After baselining, use change control process for any changes to requirement, if permitted.
Track changes to requirements.
Change solution scope if business needs change during lifetime of an initiative.
4.1.3 Inputs
Solution scope: Approve requirements which support the solution scope, else modify solution scope.
Solution scope is a requirement, and should be managed like any other requirement.
Stakeholder, Solution, or Transition requirements [Communicated or Traced]: Only communicated
requirements can be managed.
4.1.4 Elements
Manage solution scope
Stakeholder, and solution requirements must be within the solution scope. Stakeholders often identify
additional needs which the solution may be able to address. If these requirements are not aligned with the
approved business requirements, or do not fall within the solution scope, business analyst must resolve the
conflict.
Manage conflicts, and issues
Conflicts arise as stakeholders view requirements from different perspectives, or may have different
priorities. Inconsistent requirements cannot be satisfied by a single solution. So any inconsistency must be
resolved.
Resolve conflicts affecting requirements before formal approval.
Present requirements for review
Determine how to present requirements to stakeholders.
Formally present written system requirements specification or conduct structured walkthrough with various
levels of stakeholders. This can include executive summaries, structured models, associated diagrams,
supporting text, detailed attributes, and revision information. Informal presentations can happen through an email message, a note, or verbally. Informal communications may result in key stakeholders missing information
or increased ambiguity in requirements.
Obtain approval
Assist stakeholders responsible for approving requirements to understand, and accept requirements.
Stakeholder approval may be needed for result of business analysis work, allocation of requirements,
proposed problem resolutions, and other decisions. Obtain approval from stakeholders individually or as a
group.4.1.5 Techniques
Problem tracking helps in managing issues identified with requirements, and in their resolution.
Baselining: Baseline requirements after approval. Record, and track all future changes. Baselining helps in
comparing current state with respect to the baselined state. Follow further changes to requirements follow the
change control process.
Signoff: Requirements signoff ensures stakeholders agree that the content, and presentation of documented
requirements are accurate, and complete.
4.1.6 Stakeholders
Project Manager is responsible, and accountable for the project scope. She must be involved in assessing the
solution scope to define the project scope, and also in reviewing any changes to the solution scope. If a proposed
requirement is not accepted by key stakeholders, she should manage the associated risk to the project (by
altering the project scope, escalating the issue, or through other appropriate responses).
Sponsor must review, and approve business case, solution or product scope, and all requirements.
4.1.7 Output
No specific inputs provided.
For agile based projects
For non-agile based projects