My projects always seem to "bleed" extra features that weren't in the original charter. I want my dashboard to highlight scope creep as a specific risk before the budget is gone. Does anyone have a creative way to show "Initial Scope" vs "Current Scope" in a visual format that hits home for stakeholders?
3 answers
The best way to visualize this is a "Burnup Chart" with a moving "Total Scope" line. In a healthy project, the "Work Completed" line should be chasing a flat "Total Scope" line. When scope creep happens, you see that top line start to stair-step upward. When you show this to a client, it’s a very powerful visual: "Look, we are working faster than agreed, but you keep moving the finish line." It moves the conversation from "Why are you late?" to "How do we prioritize these new requests?" It’s much more effective than a boring text-based change log.
How do you handle "Small Tasks" that don't seem like scope creep individually but add up to a significant delay over time?
I use a simple "Scope Variance" percentage. Anything over 10% change turns the project status to "Amber" automatically.
Simple and effective, Kevin. Sometimes a single bold number is all it takes to get an executive to ask the right questions during a review.
Jeffrey, to answer your point, we call that "Death by a Thousand Cuts." On our dashboard, we have a specific category for "Unplanned Work %." Even if a task takes only 1 hour, if it wasn't in the sprint plan, it gets tagged. When the dashboard shows that 30% of the team's weekly capacity is being eaten by "Minor Tweaks," it gives me the data I need to stop the stakeholders from bypassing the formal change request process. It makes the invisible work visible to everyone.