Change Control Flashcards

(7 cards)

1
Q

What are the 3 possible recommendations following a change request?

A
  1. Accept
  2. Reject
  3. Defer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the steps following approval of a change request?

A
  1. Update baselines and budgets including project benefits
  2. Communicate to stakeholders, and update roles and responsibilities to implement the change
  3. Update configuration records and latest documentation to reflect the change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the stages of a change control request?

A
  1. Request (this can be made by any project stakeholder)
  2. Initial evaluation (considers whether the change should be evaluated in detail or rejected)
  3. Detailed evaluation (considers impact of change on project success criteria)
  4. Recommendation (results of evaluation)
  5. Update plans and communicate change
  6. Implement change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is information is captured in a change request?

A
  1. Description of change
  2. Reason for change
  3. Areas of impact (resource, budget, benefits)
  4. Source of change
  5. Change request owner
  6. Date raised
  7. Status of request
  8. Final decision
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the possible areas of impact for change?

A
  1. Benefits (may reduce or deliver additional benefits)
  2. Risk (impact existing or create new risks)
  3. Budget (additional budget may be required)
  4. Resource (may impact team capacity)
  5. Timeline (work may need to be replanned)
  6. Business case (project may no longer be viable)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the possible impacts of not communicating change?

A
  1. Project may go over budget
  2. Project documentation may become outdated
  3. Benefits may not be realised
  4. Activity may need to be replanned
  5. Resources may be impacted
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why is change control important for linear lifecycles?

A
  1. Linear projects have fixed scope and quality
  2. Ensures change is made in a controlled way
  3. Ensures alignment of change with project objectives
  4. Supports management of risks
  5. Provides an audit trail of decisions on proposed changes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly