SaatPro
Where Technology Meets Clarity
Section 1: The “Just One More Thing” Email
It was Wednesday, the midpoint of Sprint 1. The 7Pro ODC was finally in a “flow state.” The database drivers were working, the code was passing the local gates, and the Biometric Gateway was 60% complete.
Then, at 7:45 PM Delhi time, an email arrived from Jason Vance in New Orleans. The subject line: “Quick Enhancement – High Priority.”
“Team,” the email read. “I was showing the prototype to the VP of Marketing. She loves the biometric login, but she says it must include a ‘Social Media Share’ button that posts a ‘I just secured my money with QT’ badge to X and Instagram. It’s just a button and a small API call. Can we slide this into Friday’s demo? We need to ‘Wow’ the stakeholders.”
Mohd Tariq read the email and put his head in his hands. “Kapil, he’s doing it again. He calls it a ‘small API call,’ but it requires a new security handshake, a UI change, and a whole new set of privacy disclosures for the Canadian module.”
“It’s not just a button, Tariq,” Kapil Mehta said, looking at the Sprint Burndown chart. “It’s Scope Creep. If we add this now, we won’t finish the core Biometric Gateway by Friday. We’ll have two half-finished features instead of one ‘Done’ feature.”
Section 1 Breakdown: The PMP & ITIL Lens
- Scope Creep: This is the uncontrolled expansion of project scope without adjustments to time, cost, and resources. Jason is attempting to bypass the formal Change Control process.
- Sprint Integrity (Agile): In Scrum, once a Sprint starts, the “Sprint Goal” should not be changed. Adding new stories mid-sprint disrupts the team’s focus and invalidates the initial planning.
- Gold Plating: Marketing wants to add “extra” features that weren’t in the original requirements to “wow” the customer. In PMP, gold plating is discouraged because it introduces unnecessary risk and cost.
Section 2: The “Negotiation” Bridge
Kapil didn’t hit “Reply” immediately. He knew that simply saying “No” to a client in New Orleans could damage the relationship. He needed to use the Change Control Board (CCB) logic, even in an Agile setting.
He jumped on a quick call with Jason. “Jason, I see the vision for the ‘Social Share’ feature. It’s a great marketing hook. But we are in the middle of a committed Sprint. If we pull the developers off the Biometric logic to work on this button, we will miss the Friday delivery for the Gateway.”
“It’s just one button, Kapil!” Jason pushed back. “Can’t the guys just stay an extra two hours tonight?”
“It’s not about hours; it’s about Capacity,” Kapil replied calmly. “Every hour spent on ‘Social Share’ is an hour stolen from ‘Security.’ According to our Sprint Backlog, we are at 100% capacity. If this is a ‘Must-Have’ for Friday, we have to remove a different story of equal size to make room. Which feature do you want to cancel?”
Jason went quiet. The “Trade-off” talk always changed the perspective.
Section 2 Breakdown: The PMP & ITIL Lens
- The Triple Constraint (Iron Triangle): You cannot change the Scope without affecting Time or Cost/Quality. Kapil is forcing Jason to see the impact on “Time.”
- Change Control Process: Even in Agile, changes must be managed. Instead of a formal paper trail, the “Change Control” happens through Backlog Prioritization.
- Conflict Management (Collaborating/Problem Solving): Kapil isn’t being an “obstructionist.” He is being a “consultant,” showing the client the reality of their request.
Section 3: The London Wall – Quality vs. “The Wow Factor”
While Jason was pushing for the “Social Share” button in New Orleans, Mate Rossi in London was already reviewing the pull requests for the core Biometric Gateway. The moment he heard about the mid-sprint change, the “London Lockdown” returned.
“Kapil,” Mate’s voice was like ice on the bridge line. “I see a new API dependency for ‘Instagram-Auth’ in the staging logs. This was not in the Functional Specifications. We haven’t vetted the data privacy implications for the Canadian users. If you push this ‘Social Button’ to my environment, I will fail the entire build.”
Mohd Tariq looked at Kapil. “He’s right. The Canadian ‘PIPEDA’ laws are strict about sharing financial app data with social media. If we ‘Wow’ the marketing team, we might actually be breaking the law.”
The “Social Share” button wasn’t just a distraction; it was a Compliance Risk. Kapil realized that the “Marketing Wow” was actually a “Legal Nightmare” in disguise.
Section 3 Breakdown: The PMP & ITIL Lens
- Compliance Performance Domain: PMP 7th Edition emphasizes that projects must operate within legal and regulatory frameworks. “Social Sharing” from a banking app is a high-risk compliance area.
- Product Owner vs. Stakeholder: Jason (The Product Owner) wanted the feature, but the Marketing VP (A Stakeholder) was the one driving the “Scope Creep.” A PM must help the PO manage these external pressures.
- Definition of Done (DoD): Mate is enforcing the DoD. If the code doesn’t meet “Security and Compliance” standards, it isn’t “Done,” no matter how many buttons it has.
Section 4: The “Value-Based” Pivot
Kapil didn’t tell Jason “No.” He told him “Not Now.”
“Jason,” Kapil said in the final sync of the day. “We’ve analyzed the ‘Social Share’ request. It’s a great idea for the Phase 2 roadmap, but adding it now triggers a Compliance Audit that will delay our launch by three weeks. We are going to move it to the Product Backlog and prioritize it for the next release cycle.”
“Three weeks?” Jason gasped. “Okay, forget it. Let’s stay focused on the Gateway. The VP can wait.”
By standing his ground with data and compliance facts, Kapil protected the team. The developers went back to finishing the core gateway, and by Friday morning, the Biometric Login was demo-ready, secure, and—most importantly—compliant.
Wrapping Up Article 5: The Mid-Sprint Ambush
Scope creep is like a leak in a dam; if you don’t plug it early, the whole project eventually collapses. In this episode, the 7Pro team learned that “Yes” isn’t always the right answer for a client. By using the Triple Constraint and Compliance as their shield, they delivered real value instead of a risky “Wow factor.”
Section 5: Summary – What Did We Learn?
- Protect the Sprint Goal: Once a Sprint starts, avoid adding new work. If it’s truly urgent, something of equal size must be removed.
- Beware of Gold Plating: Adding “extra” features to impress stakeholders often introduces hidden risks, especially in security and compliance.
- Use Data to Say No: Don’t just say “we’re busy.” Explain the impact on the Critical Path or Compliance to help stakeholders understand the “Why.”
- The Power of the Backlog: A “No” today is a “Not Yet.” Moving requests to the Product Backlog ensures the ideas aren’t lost, just properly prioritized.
- Compliance is Non-Negotiable: Never sacrifice legal or security standards for a visual enhancement.
What’s Next in the Series?
The Biometric Gateway is a hit! But success brings its own problems. The user base is growing faster than the Budapest servers can handle. We’re facing a Resource Crisis.
Next Episode: Article 6 – The Bottleneck: Managing Resource Overload and Burnout. How does Kapil handle it when his best developer, Mohd Tariq, hits the wall?
