SaatPro
Where Technology Meets Clarity
Section 1: The “Grid Failure” – When the Lights Go Out
It was 3:00 PM on a sweltering Tuesday in Delhi. The 7Pro ODC was at peak productivity, finishing the final integration tests for the Canadian “Interac” payment gateway.
Suddenly, the hum of the air conditioners stopped. The dual monitors on Mohd Tariq’s desk flickered and died. The emergency lights kicked in, casting a dim orange glow over the silent office.
“Kapil!” Tariq called out, his silhouette dark against the window. “The local transformer just blew. And the building management says the backup generator has a fuel pump failure. We’ve lost the main servers, the cooling, and the high-speed fiber link. We are completely offline.”
Kapil Mehta checked his phone. A notification from the regional power authority confirmed a massive grid failure due to the record-breaking heatwave.
“The Canada demo is in four hours,” Kapil said, his voice steady despite the rising heat in the room. “The New Orleans team is waking up, and they’re expecting a live environment. If we don’t restore connectivity, this isn’t just a delay—it’s a breach of our Service Level Agreement (SLA).”
This wasn’t a “Known-Unknown” like a bug; it was a Black Swan.
Section 1 Breakdown: The PMP & ITIL Lens
- The Black Swan Event: A term popularized in risk management for an event that is beyond the realm of normal expectations, has a massive impact, and is often explained with hindsight.
- Service Level Agreement (SLA): In ITIL, the SLA defines the level of service expected by a customer (QT Money) from a supplier (7Pro), laying out the metrics by which service is measured (e.g., Uptime).
- Risk Response – Active Acceptance: 7Pro had a backup generator (a mitigation strategy), but the generator’s failure turned a managed risk into a full-blown Crisis.
Section 2: Activating the BCP (Business Continuity Plan)
Kapil didn’t waste time blaming the building manager. He reached into his desk and pulled out the Business Continuity Plan (BCP)—a document the team had mocked during “peace time” but was now their only map.
“Tariq, we are moving to Phase 2: Decentralized Execution,” Kapil commanded. “We can’t wait for the generator. Grab your encrypted laptop. Shakira, Deepak—you too. Everyone who has a 5G hotspot and a charged battery, go home or to the nearest co-working space with power. We are pivoting to the Virtual ODC model immediately.”
“What about the Budapest staging server?” Tariq asked, already packing his gear. “We can’t reach it from local home networks without the VPN tunnel that’s currently down with our office router.”
“I’m calling Daniel Silva in Mexico City,” Kapil said. “He’s our Disaster Recovery (DR) lead. He’s going to re-route the VPN gateway to the Norwalk cloud hub. We’re bypassing the Delhi office entirely.”
Section 2 Breakdown: The PMP & ITIL Lens
- Business Continuity Planning (BCP): The process of creating systems of prevention and recovery to deal with potential threats to a company. It ensures that “business as usual” continues even if the primary office is gone.
- Disaster Recovery (DR): A subset of the BCP that focuses specifically on the IT and data systems (e.g., Daniel re-routing the VPN).
- Communication Management Plan: In a crisis, the PM must switch to a Command and Control communication style—clear, direct, and frequent.
Section 3: The “Kitchen Table” Demo
By 6:30 PM Delhi time, the 7Pro ODC was an empty, dark shell. But across the city, the “Virtual ODC” was humming. Mohd Tariq was sat at his kitchen table, his laptop tethered to a mobile hotspot. Shakira was in a nearby cafe that still had a working UPS.
The Zoom call with Jason Vance (New Orleans) and the Canadian stakeholders popped up.
“Kapil,” Jason said, looking at the grainy video feed of Kapil sitting in his car using the interior light. “Why does it look like you’re in a parking lot? And why is Tariq’s background a kitchen? Is the office okay?”
“We’ve had a regional grid failure, Jason,” Kapil said, his voice steady. “But our Business Continuity Plan is in effect. We’ve migrated the VPN gateway to the Norwalk hub. The code is live on the staging server in Budapest. Tariq, show them the Interac integration.”
Tariq shared his screen. Despite the flickering fans in the background of his house, the software worked perfectly. The Canadian stakeholders watched as a test transaction moved from a Toronto bank account to the QT Money wallet in seconds.
“Wait,” one of the stakeholders asked. “You’re doing this during a blackout?”
“The project doesn’t live in a building,” Kapil replied. “It lives in the Cloud and in our Agile processes. The location is irrelevant; the delivery is what matters.”
Section 3 Breakdown: The PMP & ITIL Lens
- Virtual Teams: A core PMP concept. In a crisis, the ability to transition from a physical ODC to a distributed virtual team is the ultimate test of Resource Management.
- Stakeholder Engagement: By being transparent about the crisis but showing the solution immediately, Kapil turned a potential disaster into a “Moment of Trust” with the client.
- ITIL Service Continuity Management: This ensures that the IT service provider can always provide minimum agreed service levels. 7Pro’s ability to run the demo during a blackout is the definition of Resilience.
Section 4: The Aftermath – Hardening the System
Two days later, the power in Delhi was fully restored. The team gathered back in the office, but the mood wasn’t just “business as usual.” They were conducting a Post-Incident Review (PIR).
“We got lucky,” Mohd Tariq admitted. “Our mobile hotspots held up, but if the cell towers had gone down too, we would have been dark. We relied too much on ‘hope’ and not enough on ‘redundancy.'”
Kapil nodded, marking the Issue Log. “We are updating our Risk Management Plan. From now on, every lead developer will be issued a satellite-linked secondary internet failover. And we are moving our primary Git repository and CI/CD pipeline to a Multi-Region Cloud Provider. We are removing the ‘Delhi Office’ as a dependency for the project’s life.”
The “Black Swan” had arrived, it had challenged them, and it had left them stronger.
Section 5: Summary – What Did We Learn?
- The BCP is Not “Shelf-ware”: A Business Continuity Plan is only useful if every team member knows their “Phase 2” role without needing to ask. Practice your “Fire Drills.”
- Redundancy is Not Waste: In PMP, extra costs for backup systems (like satellite internet or multi-region servers) are often seen as “Gold Plating” until a crisis hits. Then, they become the most valuable Work Packages in the project.
- Decentralize the Knowledge: If the “Keys to the Kingdom” (VPN access, passwords, deployment scripts) are only in one physical office, you have a Single Point of Failure.
- Transparency Builds Trust: Don’t hide a crisis from your stakeholders. Tell them: 1) What happened, 2) How you are fixing it, and 3) What the impact on the deadline is.
- The Post-Incident Review (PIR): Never waste a good crisis. Use the PIR to update your Organizational Process Assets (OPAs) so the next “Black Swan” finds a much tougher target.
What’s Next in the Series?
The team has survived fire, budget cuts, and blackouts. Now comes the most dangerous phase of all: The Final Handover. We are 90% done, but as every PM knows, the last 10% takes 90% of the effort.
Next Episode: Article 9 – The Finish Line: Managing UAT, Go-Live, and “Day 2” Support. Will the Canadian users actually like what 7Pro built?
