Change Control Quiz: Can You Manage Scope Creep?

1. Which approach best prevents scope creep?

Avoid creating a detailed project scope statement

Define clear scope boundaries and require formal approval for all changes

Allow stakeholders unlimited modification rights

Ignore requests that aren't in the original plan

2. Effective Project Change Control (Project+) practices ensure that:

Projects never experience changes

Changes are managed systematically to protect scope, schedule, and budget

Only executives can request changes

All changes are approved regardless of impact

3. True or False: A change that improves project quality should be approved automatically without review.

True

False

4. The project manager's role in change control includes:

Making all change decisions unilaterally

Facilitating the change process and updating stakeholders

Preventing all changes from being requested

Approving changes without impact analysis

5. A 'gold-plating' scenario occurs when:

The project runs out of budget

Team members add features beyond scope without approval

The project schedule is compressed

Stakeholders reduce their expectations

6. Which factor should NOT influence a CCB's decision to approve a change?

Impact on project objectives

Availability of resources

The requestor's seniority level

Risk implications

7. What is a 'change log' used for?

Recording the personal feelings of team members

Tracking all approved and rejected changes throughout the project

Determining project success metrics

Assigning blame for project issues

8. True or False: All changes, regardless of size, require the same level of review and approval.

True

False

Submit

10. A change request is rejected by the CCB. The appropriate next step is:

Implement it anyway with team support

Document the rejection and communicate the decision to the requestor

Submit it again without modifications

Escalate it to upper management immediately

11. What is the primary purpose of a change control process in project management?

To prevent all changes from occurring

To evaluate, authorize, and track modifications to project scope

To eliminate the need for project documentation

To reduce communication between stakeholders

12. True or False: Informal change requests should be documented and tracked through the formal change control process.

True

False

13. A change impact assessment should evaluate:

Only financial implications

Only schedule implications

Schedule, budget, quality, resources, and risk

Only stakeholder preferences

14. What does 'configuration management' ensure in project change control?

All project deliverables are identical

Accurate tracking of project components and their versions

Changes are made without documentation

Only the project manager can modify deliverables

15. The project baseline is updated only after:

A change is requested

A change is submitted to the CCB

A change is formally approved and implemented

Team members vote on the change

16. Which of the following is NOT typically part of a change request?

Description of the requested change

Justification and business rationale

Impact analysis on schedule and budget

Personal opinions of all team members

17. True or False: Emergency changes should bypass the change control process to maintain project momentum.

True

False

18. A change control board (CCB) is responsible for:

Implementing all approved changes immediately

Reviewing, evaluating, and approving or rejecting change requests

Preventing stakeholders from requesting changes

Creating the project baseline

19. Which document formally initiates the change control process?

Project charter

Change request

Status report

Risk register

20. Scope creep most commonly occurs when:

Stakeholders request undocumented changes without formal approval

The project budget increases

Team members work overtime

The project schedule is extended

Change Control Quiz: Can You Manage Scope Creep?

1. Which approach best prevents scope creep?

2.

What first name or nickname would you like us to use?

2. Effective Project Change Control (Project+) practices ensure that:

3. True or False: A change that improves project quality should be approved automatically without review.

4. The project manager's role in change control includes:

5. A 'gold-plating' scenario occurs when:

6. Which factor should NOT influence a CCB's decision to approve a change?

7. What is a 'change log' used for?

8. True or False: All changes, regardless of size, require the same level of review and approval.

9. The change control process helps maintain project ____ by preventing unauthorized modifications.

10. A change request is rejected by the CCB. The appropriate next step is:

11. What is the primary purpose of a change control process in project management?

12. True or False: Informal change requests should be documented and tracked through the formal change control process.

13. A change impact assessment should evaluate:

14. What does 'configuration management' ensure in project change control?

15. The project baseline is updated only after:

16. Which of the following is NOT typically part of a change request?

17. True or False: Emergency changes should bypass the change control process to maintain project momentum.

18. A change control board (CCB) is responsible for:

19. Which document formally initiates the change control process?

20. Scope creep most commonly occurs when: