I am currently leading a software development project where the main stakeholder keeps adding "small" features every week. This scope creep is pushing our go-live date back, and the dev team is getting frustrated. How do I say no without damaging the relationship, especially when this person is a high-level executive? Is there a formal change management process that actually works?
3 answers
Scope creep is the silent killer of projects. You need to implement a formal Change Request (CR) process immediately. Every time the executive suggests a "small" change, perform an impact analysis. Show them exactly how much it will cost and how many days it will add to the timeline. When they see that a "small" button change adds $5,000 and 3 days, they often reconsider. It's not about saying "no," it's about saying "Yes, and here is the cost." This shifts the burden of the decision back to them while you remain the professional facilitator.
Do you have a clearly defined and signed-off Scope Statement from the beginning of the project? If the baseline wasn't firmly established, it becomes much harder to argue against these incremental changes later on.
Transparency is key. Use a visual dashboard that shows the "Health" of the project. When scope increases, the "Timeline" bar should automatically turn red to show the impact.
Visual aids are so powerful! Executives usually respond much better to a red status bar than a long email explaining technical debt or resource constraints.
James, that's exactly the issue many of us face. Even with a signed document, executives feel they have the right to pivot. I find that maintaining a "Product Backlog" even in Waterfall-ish projects helps. I tell them, "We can add this to the backlog for Phase 2," which acknowledges their idea without compromising the current Sprint or the immediate deadline.