Phase 3 · Requirements Analysis & Documentation
TopicsManaging Requirement Changes
Part of the Business Analyst Roadmap.
Summary
Requirements inevitably change mid-project — a formal change control process (assess impact, get approval, update documentation) prevents scope creep from silently derailing a project.
How to Learn This
- 1Draft a simple change request template capturing what changed and its impact.
- 2Learn to assess a change's ripple effect on timeline, budget, and other requirements before approving it.
- 3Practice the phrase 'let's evaluate the impact before committing' when a change is requested.
More topics in Requirements Analysis & Documentation
Functional vs Non-Functional RequirementsBusiness Requirements Document (BRD)Functional Requirements Document (FRD)User Stories & Acceptance CriteriaUse Cases & Use Case DiagramsRequirements Traceability Matrix (RTM)Requirements Prioritization (MoSCoW)Writing Clear, Testable RequirementsRequirements Validation & Sign-Off
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — free on the InsideEdge app.