What problem does it solve? After requirements are baselined, changes arrive constantly but teams lack a structured way to evaluate, approve, and track them, leading to uncontrolled scope creep or overly rigid processes that block legitimate changes. ## Core Features & Use Cases - CCB Establishment: Define Change Control Board membership, charter, quorum rules, and meeting cadence for governance. - Change Request Lifecycle: Process requests through submission, classification, impact analysis, CCB decision, implementation, verification, and closure. - Volatility Metrics: Track change activity with volatility charts and origin analysis to detect scope instability and improve upstream elicitation. - Use Case: A project baselines 42 requirements, then receives 7 change requests over two months. Use this workflow to classify each request, run impact analysis, get CCB decisions with documented rationale, and renegotiate schedule commitments when scope grows. ## Quick Start Set up a change control board and process for my project so we can evaluate and track incoming requirements changes against our baseline.
