I have just attended to a meeting regarding one project of my running program. This kind of meeting is called « Project Meeting ». Initiated by the project manager, it aims to discuss with the program manager and other selected stakeholders some important facts about the projects before the official Project Review. It aims to deal with important issues and collect options from important sponsors beforehand.
Really often the project team uses those meetings to announce:
- a budget exceeding,
- a delay
What I realize today is that in most of the meeting I have participated to, the project team forgive to bring important information that are keys to their counterparts: a plan.
Explaining that budget is going wild, planning is dead and gold-plated deliverables are everywhere is in a sense not really interesting to take decision about the project. What the project team should focus on are its strategy to take the project on track according to the available options:
- Budget should remain unchanged
- Planning should remain unchanged
- Scope should remain unchanged
According to those 3 different strategy the team should provide scenarii to their stakeholders in order to have clear direction.
What is the plan to keep the budget unchanged while our scope is booming or delay is out of control?
What are the consequences if we keep the original planning (i.e. deliverables dates) regarding to the scope (descoping) or budget?
When experiencing troubles on projects, project teams should of course understand the reasons and act to stop the deviation but also work on alternative and scenarii about the future of its project. If not, the decision taken during a project review could be somehow definitive.
Do you see other things to focus on in that case?
thanks for reading.