Assess Requirements Change

The purpose is to evaluate the implications of proposed changes to requirements and design.

  • Task Name - Uses uses Business Rules Analysis, Decision Analysis, Risk Analysis and Management, Business Cases, Workshops, Item Tracking, Interviews, Interface Analysis, Financial Analysis, Interviews, Document Analysis, and Estimation techniques to assess requirement changes.

  • A Change Assessment – Uses Legal/Regulatory Information, the Change Strategy, the Requirements Architecture, Domain Knowledge, the Solution Scope and the Governance Approach as guidelines.

The relationships between these guidelines, tools, techniques and Requirements, are detailed in the BABOK under the Guidelines and Tools and Techniques sections of the Prioritize Requirements task.

Workers

The people involved with creating a Change Assessment.

The relationships between these roles and a requirements and design Change Assessment are detailed in the BABOK under the Stakeholders section of Assess Requirements Change task.

  • End User - Provides information about the impact on the user of the solution.

  • Customer - Provides information about the value of the change.

  • Domain Subject Matter Expert - Provides information about the impact on the organization.

  • Operational Support - Provides information about their ability to support the change.

  • Project Manager - Determines the project work necessary to complete the change.

  • Regulator - Confirms the change compliance to the applicable standards.

  • Sponsor - Provides knowledge used to assess the change.

  • Tester - Assists with assessing the impact of the change.