Which process helps avoid scope creep and disputes when changes occur in a project?

Which process helps avoid scope creep and disputes when changes occur in a project?

• A. Change management
• B. Quality assurance
• C. Risk register
• D. Lessons learned

Answer: (A)

Managing changes through a formal change management process prevents scope creep and disputes by requiring each request to go through logging, impact analysis, and formal approval before the project plan is updated. This creates a controlled workflow with clear authority (often a change control board), so changes are evaluated for their effect on scope, schedule, and budget, and only approved changes are implemented. The result is everyone aligned on what’s in scope and how it will be delivered, with a documented record to resolve disagreements. Other processes, like quality assurance, focus on meeting quality standards; a risk register tracks potential threats; and lessons learned captures experiences after the work, but none directly governs change requests and baseline updates in a structured way.

Managing changes through a formal change management process prevents scope creep and disputes by requiring each request to go through logging, impact analysis, and formal approval before the project plan is updated. This creates a controlled workflow with clear authority (often a change control board), so changes are evaluated for their effect on scope, schedule, and budget, and only approved changes are implemented. The result is everyone aligned on what’s in scope and how it will be delivered, with a documented record to resolve disagreements. Other processes, like quality assurance, focus on meeting quality standards; a risk register tracks potential threats; and lessons learned captures experiences after the work, but none directly governs change requests and baseline updates in a structured way.