Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Salesforce Consultant
medium

How do you handle scope creep on a Salesforce project?

Scope creep is the gradual expansion of project scope beyond what was originally agreed — usually without proportional adjustment to budget or timeline.

Why it happens:

  • Stakeholders see the system come together; new ideas appear.
  • Original requirements were incomplete; gaps surface during Build.
  • Adjacent business needs become "obvious" once the platform is live.
  • Pressure from leadership: "while we're at it, can you also...".

Why it's dangerous:

  • Schedule slippage compounds (every "small ask" is rarely small).
  • Quality drops as the team rushes.
  • Original commitments get missed.
  • Team burns out.

Management approach:

1. Establish a clear scope baseline upfront. Solution Design Document. Signed off. Reference document.

2. Change control process. Every new request goes through a defined gate:

  • Capture: what's being asked, why, who from.
  • Assess: effort, dependencies, risk.
  • Decide: approve, defer, or reject.
  • Communicate: whatever the answer is, document and broadcast.

3. Use "in scope" / "out of scope" / "future" labels. Don't reject ideas; defer them. Builds backlog for Phase 2.

4. Track impact transparently. "If we add this, X is delayed by 2 weeks and Y is at risk." Make trade-offs visible.

5. Prioritise ruthlessly. When 10 new asks arrive, they can't all happen this sprint. Top 3, defer the rest.

6. Renegotiate if the original scope is genuinely wrong. Sometimes the original Discovery missed something fundamental. Don't pretend otherwise; replan formally.

7. Engage the sponsor. Scope creep often comes from middle managers; the sponsor can prioritize across them.

Sentinel signs that scope is creeping:

  • Sprint velocity dropping without explanation.
  • Backlog growing faster than it's burning down.
  • "Just one more thing" becoming common.
  • Team morale declining; quality complaints rising.
  • Re-estimating project end-date weekly.

Senior consultant move: distinguish "scope creep" from "scope discovery". Genuine new requirements that emerge from real Discovery deserve formal change orders. Frivolous requests need to be deferred. The art is telling them apart.

Why this answer works

Senior. The scope creep vs scope discovery distinction and the change-control gate are mature.

Follow-ups to expect

Related dictionary terms