Scope Creep vs Gold Plating: PMP Exam Distinctions That Matter

Scope Creep and Gold Plating: Two Different Problems, One Exam Topic

The PMP exam frequently tests whether candidates can distinguish between scope creep and gold plating. Both involve work that was not part of the approved project scope, but they differ in origin, intent, and management response. Confusing the two on the exam — or on a real project — leads to wrong answers and wrong decisions.

What Is Scope Creep?

Scope creep is the uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources. It happens when new requirements, features, or deliverables are added to the project without going through the formal change control process.

Characteristics of Scope Creep

• Changes originate from stakeholders, customers, or even team members.
• Changes bypass the integrated change control process.
• The scope baseline is not formally updated to reflect the added work.
• Budget, schedule, and resource plans become misaligned with actual work.

Example

A stakeholder asks the development team to add a reporting feature during a sprint review. The team agrees and starts working on it without submitting a change request. No impact analysis is performed, no baseline is updated, and the schedule slips because the team is doing work that was never planned.

What Is Gold Plating?

Gold plating is when the project team delivers more than what was specified in the scope baseline — adding extra features, functionality, or quality beyond what the customer requested. Unlike scope creep, gold plating is initiated by the team, not the stakeholder.

Characteristics of Gold Plating

• The team voluntarily adds extra work that no one asked for.
• The intent is usually positive — the team believes they are adding value.
• It consumes resources and time that should be allocated to approved scope.
• It introduces unnecessary risk — the added features may contain defects or cause integration issues.

Example

A developer finishes a login page that meets all requirements but decides to add an animated transition effect "because it looks better." No one requested the animation, and it was not in the scope statement. If the animation introduces a bug or delays the next deliverable, the team has created risk for zero approved value.

Key Differences for the PMP Exam

The exam tests these distinctions in scenario-based questions. Use this comparison:

• Origin: Scope creep comes from stakeholders or external pressure. Gold plating comes from the team.
• Intent: Scope creep is often unintentional or the result of poor change control. Gold plating is intentional — the team chooses to add extras.
• Process violation: Scope creep bypasses change control. Gold plating may not involve a formal change request because the team acts unilaterally.
• PMI's stance: Both are unacceptable. The correct approach is to deliver exactly what the scope baseline specifies and use change control for anything else.

Prevention Strategies

For the PMP exam, the correct answer to preventing both scope creep and gold plating involves the same core mechanism: a robust integrated change control process supported by a clearly defined scope baseline.

Preventing Scope Creep

1. Ensure all change requests go through the Change Control Board (CCB).
2. Maintain a detailed scope statement with explicit exclusions.
3. Educate stakeholders on the change request process during stakeholder engagement.

Preventing Gold Plating

1. Train the team to deliver to requirements — no more, no less.
2. Define clear acceptance criteria in the WBS Dictionary and scope statement.
3. Review deliverables against the scope baseline during quality control.

Practice distinguishing scope creep from gold plating with realistic scenario questions in our PMP practice exams.