SaatPro
Where Technology Meets Clarity
Section 1: The “Hero” Culture Hits a Wall
It was Thursday of the second Sprint. The QT Money app was gaining traction in the beta environment, but the “Success” was starting to look like a crisis in the 7Pro ODC. Mohd Tariq hadn’t left the office before midnight in three days.
“Tariq, you still here?” Kapil Mehta asked, walking over to Tariq’s desk at 9:00 PM.
Tariq didn’t look up. He was staring at a flickering screen of Java stack traces. “The Mexico API is timing out, the Budapest database is lagging, and Jason just sent three more ‘high priority’ bugs from the New Orleans testers. If I don’t fix these tonight, the morning stand-up will be a disaster.”
Kapil looked at the Resource Histogram on the wall. Tariq was allocated at 140% capacity. He was the “Key Man” dependency—the only one who understood the full integration between the three regions.
“You’re red-lining, Tariq,” Kapil said quietly. “If you crash, the whole project stops. We’ve created a Single Point of Failure, and that person is you.”
Section 1 Breakdown: The PMP & ITIL Lens
- Resource Over-allocation: In PMP, this happens when a team member is assigned more work than they can perform in a standard work period. It leads to burnout, high error rates, and project risk.
- Key Man Risk: This is a specific type of Resource Risk. When a project depends too heavily on one person’s knowledge, that person becomes a bottleneck.
- Team Performance Domain: PMP 7th Edition emphasizes “Team Health.” A high-performing team isn’t just one that works hard; it’s one that has a sustainable pace.
Section 2: The “Leveling” Conversation
Kapil knew he couldn’t just tell Tariq to “go home.” He had to address the root cause: the Workload. He opened a bridge call with Tim John (Norwalk) and Jason Vance (New Orleans).
“Tim, Jason, we have a resource crisis,” Kapil stated. “Tariq is at 140% capacity. The rest of the India team is at 90%. We are pushing the limits of Sustainable Development. If we don’t apply Resource Leveling right now, we are going to lose our lead architect to burnout.”
“We can’t slow down, Kapil,” Jason interjected. “The marketing launch is set!”
“I’m not suggesting we slow down the project,” Kapil replied. “I’m suggesting we Smooth the work. We are going to move the non-critical bugs to Sprint 3 and reassign the documentation tasks from Tariq to the junior devs in Delhi. We need to offload the ‘noise’ so Tariq can focus on the ‘signal.'”
Section 2 Breakdown: The PMP & ITIL Lens
- Resource Leveling: Adjusting the project schedule (start and finish dates) based on resource constraints. This often extends the timeline but protects the team.
- Resource Smoothing: Adjusting the activities within their “float” so that the resources don’t exceed limits. The finish date doesn’t change, but the workload is balanced.
- Servant Leadership: Kapil is acting as a “Shield” for his team. A Servant Leader’s primary role is to remove impediments—and sometimes, the impediment is an unrealistic workload.
Section 3: Knowledge Transfer – Breaking the Bottleneck
The next morning, Kapil implemented a “No-Code Wednesday.” Instead of Tariq fixing bugs, he was tasked with a Knowledge Transfer (KT) session.
“Tariq,” Kapil said, “Today, you aren’t a developer. You’re a teacher. You’re going to walk Shakira and Deepak through the Mexico API integration. We are going to turn your ‘private knowledge’ into ‘organizational assets.'”
It was painful at first. Tariq felt the urge to grab the keyboard and “just do it himself.” But by the afternoon, Shakira had successfully resolved a timeout issue in the Sandbox. The Bottleneck was starting to widen.
Section 3 Breakdown: The PMP & ITIL Lens
- Knowledge Management: In PMP, managing project knowledge involves both “Explicit Knowledge” (documentation) and “Tacit Knowledge” (experience). Kapil is converting Tariq’s tacit knowledge into team capability.
- Cross-Training: An Agile practice that aligns with PMP’s Resource Management Plan. It creates a “T-Shaped” workforce where everyone has a broad set of skills and one deep specialty.
- Organizational Process Assets (OPAs): The documentation produced during this KT session becomes an OPA that will help 7Pro on future projects, not just this one.
Section 4: The “Sustainable Pace” Victory
By Friday, the atmosphere in the ODC had shifted. Tariq had left the office at 7:00 PM for two nights in a row. Shakira was now handling the basic API fixes, and the Sprint Burndown chart was actually looking healthier.
“Jason,” Kapil said during the demo. “We delivered all the high-priority items. We didn’t do the ‘Social Share’ button, and we pushed the documentation to next week. But my team is fresh, our error rate has dropped by 20%, and we are ready for Sprint 3.”
Tim John nodded on the screen. “Good call, Kapil. I’d rather have a team that can finish the marathon than one that collapses after the first mile.”
Wrapping Up Article 6: The Bottleneck
A project manager’s most valuable assets aren’t the servers or the software licenses—it’s the people. In this episode, 7Pro learned that “Heroics” are a sign of a broken process. By using Resource Smoothing and Knowledge Transfer, they turned a “Single Point of Failure” into a resilient, cross-functional team.
Section 5: Summary – What Did We Learn?
- Monitor Your Histogram: Always look at your Resource Histogram to see who is over-allocated. Catch the “Red” before the person burns out.
- Leveling vs. Smoothing: Know when to extend the timeline (Leveling) and when to just re-distribute the work within the existing time (Smoothing).
- Kill the “Key Man” Risk: If the project fails when one person gets sick, your plan is flawed. Prioritize Knowledge Transfer (KT) early.
- Sustainable Pace is a Metric: High velocity is useless if it leads to high turnover or massive error rates.
- Protect the Team: A PM must be willing to have the “Hard Conversation” with stakeholders to protect the team’s health.
What’s Next in the Series?
The team is balanced and the code is solid. But now, a new threat emerges. A major Currency Fluctuation and a change in Import Taxes in the UK are threatening the project’s budget.
Next Episode: Article 7 – The Budget Bleed: Managing Costs and Procurement Risks. How does Kapil handle it when the ‘Money’ part of ‘QT Money’ starts to vanish?
