Scope creep is the silent assassin of IT projects. It starts innocently enough—a small request here, a minor tweak there. Before you know it, you’re not just building a Business Application; you’re constructing the digital equivalent of the Great Wall of China, complete with customizations that would make Da Vinci weep. Negotiating these creeping demands is an art form, one part diplomacy, one part stand-up comedy, and three parts panic.
The Prelude: “It’s Just a Small Request”
It begins during a routine project status meeting. We’re reviewing deliverables, timelines, and milestones when the Business Owner casually says:
Business Owner: “By the way, we’ve been thinking… Could we add a small feature to the system?”
Me (Pre-Sales Head): Small feature. The most dangerous words in any project.
The Cynic Upstairs: Small? Like adding a skylight to a skyscraper. Sure, no problem.
Me (diplomatic): “What’s the feature?”
Business Owner: “We’d like to include automated pricing suggestions for bulk orders.”
Me: “That’s not in the scope.”
Business Owner: “But it’s essential for us.”
The Cynic Upstairs: Essential? It wasn’t essential two weeks ago.
The Functional Heads Join the Party
Once the Business Owner plants the seed, the Functional Heads seize the opportunity.
Sales Head: “While we’re at it, can we also add a predictive customer demand module?”
Finance Head: “And multi-layered approval workflows for payments?”
Operations Head: “Plus, a dashboard to monitor chemical formulation efficiency in real time?”
Me: “These are all great ideas, but…”
The Cynic Upstairs: But we’re trying to finish Phase 1 this year.
Business Owner: “You said this ERP system is scalable. Can’t we just scale these features in?”
The Cynic Upstairs: Scalable doesn’t mean infinite. Otherwise, it’s called magic.
The Classic Justifications
The customer team breaks out the greatest hits of scope creep justification:
- The “It’ll Only Take a Few Hours” Argument
Sales Head: “The pricing suggestion feature shouldn’t take more than a few hours to implement, right?”
Me: “Well, it involves configuring rules, integrating with the product catalog, and testing…”
Sales Head: “But just a few hours, right?”
The Cynic Upstairs: Sure, if you live in a parallel universe where IT systems configure themselves.
- The “We Thought It Was Included” Gambit
Finance Head: “Wasn’t multi-layered approvals already part of the scope?”
Me: “No, it wasn’t.”
Finance Head: “Really? I’m pretty sure we discussed it in the initial meetings.”
Me: “We discussed it as a future phase.”
Finance Head: “Well, the future is now.”
The Cynic Upstairs: And the future is bleak.
- The “It’s a Simple Feature” Card
Operations Head: “The dashboard for chemical formulation efficiency is a simple feature. We just want to see real-time batch performance.”
Me: “You mean integrating data from multiple sensors, analyzing it in real time, and visualizing it in a user-friendly dashboard?”
Operations Head: “Exactly! See? Simple.”
The Cynic Upstairs: Simple. Like launching a rocket into space.
The Negotiation: Where Logic Goes to Die
At this point, I’m juggling requests while the Delivery Team is silently glaring at me, probably plotting my untimely demise.
Me: “We can include these features in future phases.”
Business Owner: “But we need them now.”
Me: “Adding them now will delay the timeline and increase the cost.”
Sales Head: “What if we keep the timeline the same and just work faster?”
The Cynic Upstairs: Faster? Sure. Let me just bend the space-time continuum.
Finance Head: “Can’t we shift resources around?”
Me: “That’s not how this works.”
Finance Head: “But can’t it be?”
The Cynic Upstairs: Yes, and while we’re at it, let’s reinvent physics.
The Magic Word: “Budget”
Finally, I bring out the ultimate weapon: money.
Me: “If we add these features, it will cost extra.”
Business Owner: “Extra? How much extra?”
Me (calculating quickly): “For these features, an additional ₹50 lakhs and two months.”
Finance Head: “₹50 lakhs? That’s outrageous!”
Me: “Custom features take time and resources.”
Operations Head: “What if we reduce testing?”
Me: “Then you risk deploying features that don’t work.”
The Cynic Upstairs: Deploy broken features? Bold strategy. Let’s see how that works out.
The Compromise: Kicking the Can Down the Road
After an hour of back-and-forth, we arrive at the inevitable conclusion:
Me: “We can document these requests as part of Phase 2.”
The Cynic Upstairs: “Common, use the term Wave 2, instead of Phase 2. They may remember the Corona Wave 2 and shun the Wave altogether or the project ;)”
Business Owner: “Phase 2? When’s that?”
Me: “After Phase 1 is live and stabilized.”
Finance Head: “So… six months?”
Me: “More like 12.”
Sales Head: “But that’s so far away!”
The Cynic Upstairs: Far enough for you to forget about it. Hopefully.
Me (smiling): “Let’s focus on delivering a successful Phase 1 first. After all, that’s the foundation for everything else.”
Business Owner (reluctantly): “Fine. But we’ll hold you to Phase 2.”
The Aftermath: Back at the Office
When I return to the office, the Delivery Team surrounds me like a pack of wolves.
Delivery Lead: “Please tell me you didn’t agree to those features.”
Me: “Of course not.”
Delivery Analyst: “Did they ask for anything outrageous?”
Me: “Just predictive pricing, multi-layered approvals, chemical dashboards, and instant magic.”
The Cynic Upstairs: Don’t forget the unicorn they casually requested.
As I sit down to document the meeting, I can’t help but marvel at the sheer audacity of scope creep.
The Cynic Upstairs: So, what’s the moral of the story?
Me: That no ERP project is complete without someone trying to sneak in their wish list.
The Cynic Upstairs: And your hair?
Me: Still intact. For now.
And with that, we prepare for the next status meeting—armed with clearer scope definitions and a growing sense of dread. For now.