Key takeaways
- Describe a change before deciding how to respond.
- A changed requirement may affect several domains and phases.
- Traceability helps prevent inconsistent local adaptations.
Explain what changes and why
A Change Request formalizes a proposed modification. It may arise from a new constraint, implementation findings, an altered requirement, or an external event. It explains the reason for change, scope, expected consequences, and references needed for review. Its existence does not mean the change has already been accepted.
The request should identify affected elements and work, priorities, recommendations, and decisions needed. A team may discover, for example, that a partner cannot provide information at the expected frequency. The request explains the adaptation needed and its effects instead of silently changing an approved interface.
Follow the impact on requirements
Requirements Impact Assessment examines the consequences of new needs or requirement changes. It may identify ADM phases to revisit, descriptions to update, and recommendations to stakeholders. Traceability to objectives, decisions, and solutions helps determine the actual extent of change. Approvals and versions are then adjusted according to governance arrangements.
- Identify affected elements and associated risks.
- Compare options and consequences before approval.
- Update connected information after the decision.
TERMS TO KNOW
The terms, in context.
- Change Request
- Formal proposed modification submitted for a decision.
- Requirements Impact Assessment
- Analysis of the consequences of changes to requirements.