Change Control Flashcards
(7 cards)
1
Q
What are the 3 possible recommendations following a change request?
A
- Accept
- Reject
- Defer
2
Q
What are the steps following approval of a change request?
A
- Update baselines and budgets including project benefits
- Communicate to stakeholders, and update roles and responsibilities to implement the change
- Update configuration records and latest documentation to reflect the change
3
Q
What are the stages of a change control request?
A
- Request (this can be made by any project stakeholder)
- Initial evaluation (considers whether the change should be evaluated in detail or rejected)
- Detailed evaluation (considers impact of change on project success criteria)
- Recommendation (results of evaluation)
- Update plans and communicate change
- Implement change
4
Q
What is information is captured in a change request?
A
- Description of change
- Reason for change
- Areas of impact (resource, budget, benefits)
- Source of change
- Change request owner
- Date raised
- Status of request
- Final decision
5
Q
What are the possible areas of impact for change?
A
- Benefits (may reduce or deliver additional benefits)
- Risk (impact existing or create new risks)
- Budget (additional budget may be required)
- Resource (may impact team capacity)
- Timeline (work may need to be replanned)
- Business case (project may no longer be viable)
6
Q
What are the possible impacts of not communicating change?
A
- Project may go over budget
- Project documentation may become outdated
- Benefits may not be realised
- Activity may need to be replanned
- Resources may be impacted
7
Q
Why is change control important for linear lifecycles?
A
- Linear projects have fixed scope and quality
- Ensures change is made in a controlled way
- Ensures alignment of change with project objectives
- Supports management of risks
- Provides an audit trail of decisions on proposed changes