change-control-advisor
Purpose
Guide requirements engineers through the change control process -- evaluating change requests, performing impact analysis, and managing approval decisions. Use this when requirements are baselined and changes need structured evaluation.
This is not about preventing all changes. It is about making changes visible, evaluated, and deliberate instead of invisible, unevaluated, and accidental.
Key Concepts
Change Control Fundamentals
Baseline: A reviewed, agreed-upon set of requirements that serves as the basis for development. Changes to the baseline are controlled.
Scope Creep: Uncontrolled growth in project scope through incremental, unevaluated additions. Each individual change seems small; the cumulative effect derails the project.
Change Control Board (CCB): The group authorized to approve or reject changes to the baseline. Composition varies by project:
- Small projects: Product owner + lead developer + BA
- Large projects: Sponsor, BA, architect, project manager, test lead