You should use plan B which should be part of your planning to manage the project.
How to plan for plan B? any suggestions how plan B should be like
...
1 reply by Riad Alhammoud
May 12, 2021 4:33 PM
Riad Alhammoud
...
Hi Vencat,
Plan B is one of the risk responses which are planned during planning stage and are implemed once plan risks are happened. For more details you can read risk managent knowledge area in pmbok.
Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
Your initial risk assessment should have identified the risk of losing a key team member - not specifically which team member but a team member. The initial risk assessment should have developed mitigation measures, or plan B that Riad referred to. In a pinch there are two obvious measures: 1) spread the load, or 2) find a replacement.
While you're at it, what is the risk of further personnel loss and what are you going to do about it? What other risks can be identified? Otherwise you are reactive-driven management rather than proactive.
I don't have much sympathy for those that fail to plan for the inevitable. Absenteeism is a known risk and should be addressed at the onset. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You always can change deliverable date. While it can depend on the agile based method you are using remember that, talking about things that happend on most of the methods, if you commit to create features/stories and you see that the commit can not be achieved then it has to be "deleted" from the current iteration. The key is do not loose credibility then work on committed and not committed is key. Saving Changes...
Riad AlhammoudProject management| LanganAbu Dhabi, United Arab Emirates
May 12, 2021 9:38 AM
Replying to venkat ganti
...
How to plan for plan B? any suggestions how plan B should be like
Hi Vencat,
Plan B is one of the risk responses which are planned during planning stage and are implemed once plan risks are happened. For more details you can read risk managent knowledge area in pmbok. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Venkat,
as you are using agile, I would first ask the self organising team to cover the situation and see what they come up with. It is their team commitment anyhow.
Then, or in parallel, look for replacements outside the team, from other teams, existing contractors, or outside the company.
In general, I agree with others, this situation should have been handled as a risk with high impact and mitigated, e.g. by having pairs working in one role, or having members who can take multiple roles, or just duplicate key resources on the team.
As Sergio says, negotiate with the PO how to handle this exception.
An agile approach minimises the impact of staff absences through the use of cross-functional teams and frequent delivery.
In a cross-functional team sickness presumably means a temporary drop in velocity and cycle time unless you can fill the gap immediately or compromise on scope. If you are using fixed iterations then you can take account of reduced resources in the next iteration planning meeting where necessary so that expectations are set accordingly. Scope or resource is what changes rather than dates. Saving Changes...
