My lead developer, who is the only one with the expertise for our current phase, has been reassigned to a "company-wide emergency" for the next two weeks. This puts our critical path at major risk. How should I communicate this delay to my client and what internal steps can I take to mitigate the damage?
3 answers
First, you must update your Risk Register and immediately perform a "What-If" scenario analysis. Document the exact impact on the milestone dates. When you talk to the client, do not lead with "we are delayed." Instead, present the solution: "Due to internal resource reallocation, we are shifting focus to [Task B] which was scheduled for later, while we wait for the developer to return." This shows you are still managing the project actively. Internally, you need to flag this to the PMO or your manager as a "Resource Conflict." If this is a recurring issue, it suggests a failure in capacity planning at the organizational level.
Is there any possibility of "Shadowing" or "Knowledge Transfer" happening before they leave, or is the emergency so immediate that you've lost them already?
Review your "Critical Path." You might find that you can fast-track other non-dependent tasks to keep the team busy and the project moving forward.
Precisely, Patricia. Shifting the schedule to focus on tasks that don't require the lead developer is the only way to minimize the total project slippage.
Unfortunately, William, they were pulled within two hours' notice. I am now looking at our junior staff to see if they can handle basic maintenance tasks to keep some momentum while the lead is away. It's a tough spot because our documentation isn't as robust as it should be, which is a hard lesson learned for me as a PM. I will definitely prioritize documentation in the next phase.