Study guide

4.4 Assess Requirements Changes

CBAP Certified Business Analysis Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & BACCM Framework

1.1 CBAP Exam Structure, Eligibility & Study Plan 1.2 The Business Analysis Core Concept Model (BACCM) 1.3 Key Concepts, Terms & Requirements Classification 1.4 Business Analysis Governance & Stakeholder Engagement Principles

2 Chapter 2: Business Analysis Planning and Monitoring

2.1 Plan Business Analysis Approach 2.2 Plan Stakeholder Engagement 2.3 Plan Business Analysis Governance 2.4 Plan Business Analysis Information Management 2.5 Identify Business Analysis Performance Improvements

3 Chapter 3: Elicitation and Collaboration

3.1 Prepare for Elicitation 3.2 Conduct Elicitation 3.3 Confirm Elicitation Results 3.4 Communicate Business Analysis Information 3.5 Manage Stakeholder Collaboration

4 Chapter 4: Requirements Life Cycle Management

4.1 Trace Requirements 4.2 Maintain Requirements 4.3 Prioritize Requirements 4.4 Assess Requirements Changes 4.5 Approve Requirements

5 Chapter 5: Strategy Analysis

5.1 Analyze Current State 5.2 Define Future State 5.3 Assess Risks 5.4 Define Change Strategy 5.5 Business Case Development & Financial Analysis

6 Chapter 6: Requirements Analysis and Design Definition

6.1 Specify and Model Requirements 6.2 Verify Requirements 6.3 Validate Requirements 6.4 Define Requirements Architecture 6.5 Define Design Options 6.6 Analyze Potential Value and Recommend Solution 6.7 Data Modeling & Process Modeling Techniques 6.8 Use Cases, User Stories & Acceptance Criteria Definition 6.9 Non-Functional Requirements & Solution Constraints

7 Chapter 7: Solution Evaluation

7.1 Measure Solution Performance 7.2 Analyze Performance Measures 7.3 Assess Solution Limitations 7.4 Assess Enterprise Limitations 7.5 Recommend Actions to Increase Solution Value

8 Chapter 8: Underlying Competencies, Techniques & Perspectives

8.1 Analytical Thinking, Problem Solving & Business Knowledge 8.2 Behavioral Characteristics & Interaction Skills 8.3 Core BABOK Techniques Master Review 8.4 Business Analysis Perspectives

4.4 Assess Requirements Changes

Key Takeaways Explain This Topic AI

Assess Requirements Changes (BABOK Task 14) evaluates the impact, cost, risk, and feasibility of proposed modifications to previously baselined requirements or designs.

Comprehensive impact analysis evaluates six dimensions: Scope, Cost, Schedule, Quality, Risk, and Architecture.

Formal change management relies on a Change Control Board (CCB) that reviews Change Requests (CRs) and issues explicit decisions (Approve, Reject, Defer, Request Information).

Predictive (Waterfall) projects use formal CR gating protocols, whereas Adaptive (Agile) frameworks manage change fluidly through product backlog refinement.

BAs must remain objective advocates for value, preventing scope creep while ensuring beneficial changes are properly evaluated and integrated.

Last updated: August 2026

  • 4.4 Assess Requirements Changes
  • Core Purpose and BABOK v3 Context

Change is inevitable in business analysis. As project execution progresses, business environments evolve, new market opportunities emerge, and technical constraints are uncovered. Task 14: Assess Requirements Changes provides a structured mechanism to evaluate proposed modifications, additions, or deletions to baselined requirements and designs.

The goal of this task is not to prevent change, but to ensure that only beneficial, fully understood changes are approved , while unvetted or disruptive changes are rejected or deferred. Uncontrolled change leads to "scope creep"—the silent, unauthorized expansion of project boundaries that causes cost overruns, missed deadlines, and solution instability.

Comprehensive Impact Analysis Framework

When a Change Request (CR) is submitted, the BA must conduct a rigorous Impact Analysis across six core project dimensions before taking the request to decision-makers:

Impact Dimension Analytical Questions & Assessment Focus High-Impact Red Flags

1. Scope Does the change alter core business boundaries, add new user roles, or expand system interfaces? Expanding functionality beyond the original Business Case boundaries.

2. Cost & Effort How many additional engineering, testing, and business analysis hours are required to build and deploy? Requiring specialized external vendor consultants or unbudgeted cloud infrastructure.

3. Schedule Does the change push back critical milestone dates, sprint delivery commitments, or regulatory go-live targets? Pushing deployment past a fixed legal compliance deadline.

4. Quality & Testing Will this change degrade system response times, security posture, or necessitate extensive regression testing? Invalidating 50% of existing, pre-executed user acceptance test scripts.

5. Risk What new technical, operational, or vendor risks are introduced by modifying existing functionality? Introducing single points of failure in established microservices.

6. Architecture Does the proposed change violate established enterprise architecture patterns or require structural database redesign? Breaking backward compatibility for existing enterprise APIs.

End-to-End Formal Change Request (CR) Workflow

In structured or predictive initiatives, requirement changes follow a formal, audited governance lifecycle: [1. Submit Change Request]

  • │
  • ▼
  • [2. Initial BA Screening] ──(Invalid / Duplicate)──► [Rejected / Retract]
  • │
  • ▼ (Valid CR)
  • [3. Perform Impact Analysis] ──(Evaluate 6 Dimensions & Traceability Links)
  • │
  • ▼
  • [4. Formulate Recommendation] ──(Approve, Reject, or Defer + Justification)
  • │
  • ▼
  • [5. CCB Evaluation Session] ──(Review BA Impact Report & Stakeholder Trade-offs)
  • │
  • ├───────────────────────┼───────────────────────┐
  • ▼ ▼ ▼
  • [6a. Approved] [6b. Rejected] [6c. Deferred]
  • │ │ │
  • Update Baseline Archive CR with Place in Future
  • & Traceability Reason Log Backlog Pool
  • Step-by-Step Breakdown

Submission : Stakeholder submits a written CR specifying the requested change, business rationale, and perceived urgency.

Screening : BA verifies if the request is truly a scope change or simply a clarification of an existing approved requirement.

Detailed Impact Analysis : BA leverages the Requirements Traceability Matrix (RTM) to identify every derived requirement, code module, and test script affected.

Recommendation Formulation : BA calculates total cost/benefit impact and authors an objective recommendation.

CCB Presentation : BA presents findings to the Change Control Board.

Decision Execution : Baseline artifacts, project schedules, and budgets are formally adjusted based on CCB output.

Change Control Board (CCB) Structure & Governance

The Change Control Board (CCB) is the formal governance body cross-functionally authorized to approve, reject, or defer proposed requirement changes.

Typical CCB Composition

Executive Sponsor / Chair : Ultimate financial authority.

Lead Business Analyst : Presents impact analysis, traceability maps, and objective recommendations.

Project Manager / Delivery Lead : Assesses schedule, budget, and staffing impact.

Lead Solution Architect / Tech Lead : Assesses architectural feasibility and technical risk.

Quality Assurance Lead : Evaluates testing effort and regression risks.

Business Unit SME / Product Owner : Assesses operational business impact.

CCB Decision Criteria

Approve : Change adds validated net business value exceeding its cost and risk, and budget/schedule adjustments are accepted.

Reject : Change adds insufficient value, introduces unacceptable risk, or violates core architectural standards.

Defer : Change has merit but cannot be accommodated in the current release due to schedule constraints (deferred to a future release backlog).

Request More Information : Impact analysis is incomplete; BA instructed to perform further research.

Managing Changes in Adaptive (Agile) vs. Predictive (Waterfall) Lifecycles

BABOK v3 emphasizes that while the need to assess change is universal, the mechanism varies dramatically based on project methodology:

Dimension Predictive (Waterfall / Traditional) Adaptive (Agile / Lean)

Change Baseline Fixed baseline documented in formal Business Requirements Document (BRD). Dynamic, prioritized Product Backlog baseline.

Change Governance Formal Change Control Board (CCB) meeting bi-weekly or monthly. Product Owner continuous prioritization during Backlog Refinement.

Assessment Cost High—requires formal CR impact analysis documents and formal sign-offs. Low—evaluated in minutes via User Story estimation and trade-off discussions.

Scope Adjustment Budget and schedule are adjusted to accommodate newly approved scope. Budget and schedule are fixed (timeboxed sprints); lower-priority stories are swapped out.

BACCM Connections in Assessing Changes

Change : Core subject of this task; systematically evaluated before execution.

Need : Verifies whether the change addresses a genuine business need or merely a superficial preference.

Solution : Analyzes how the proposed modification alters existing or planned solution architecture.

Stakeholder : Identifies all stakeholders impacted by the change and collects their input.

Value : Weighs incremental value added against incremental cost and risk introduced.

Context : Considers external environmental factors (regulatory changes, market moves) triggering the change.

Worked Example: Core Banking API Change Assessment

Scenario : Two weeks before user acceptance testing for a core banking upgrade, a Fintech integration partner requests a modification to the Open Banking API schema to add 3 new customer data fields.

BA Impact Analysis :

Traceability Query : Tracing API schema dependencies reveals that 14 downstream reporting microservices and 22 automated security test cases depend on the current schema.

Impact Calculations : Building and testing the 3 new fields requires 80 developer hours, $25,000 in vendor QA costs, and delays UAT launch by 8 business days.

Risk Assessment : Changing the schema late increases regression bug risk by 35%.

BA Recommendation to CCB : Defer . Recommend implementing the schema change in Release 2.1 (scheduled 6 weeks post-launch) to protect the hard go-live date for Release 2.0.

CCB Decision : CCB accepts the BA's recommendation, approving Release 2.0 baseline as scheduled and queuing the API modification for Release 2.1.

CBAP Exam Tips & Common Pitfalls

💡 Exam Tip : On the CBAP exam, when a stakeholder informally requests a change to a baselined requirement, the BA's immediate first step is ALWAYS to perform an Impact Analysis and follow the formal change process—never agree to implement the change immediately or refuse it outright without analysis.

⚠️ Common Trap : Do not confuse evaluating a change with approving a change. The BA conducts the impact assessment and formulates recommendations, but formal authority to approve changes affecting budget or schedule rests with the CCB or Executive Sponsor .

Loading diagram... Change Control Board (CCB) Evaluation & Impact Analysis Governance Workflow

Cost-of-Change Trajectory vs Project Lifecycle Phase