Project Management

Please login or join to subscribe to this thread

If I have a risk which will impact the project schedule, thus is right to show the slippage into the schedule or we can just mentioned the impact of the particular on schedule in risk register

linkedin twitter facebook   Risk Management   Scheduling  
avatar
Prateek Singh IT PMO & Governance| Danaher Corporation Pune, India

Recently, I had an argument with the Program Manager where she was asking me to show the schedule slippage in the project schedule. However, I explained that since the slippage has not yet occurred, doing so would create an unintended impact on stakeholders, leading to passive acceptance of the delay. Instead, I suggested that we document this risk in the Risk Register and highlight its potential significant impact on the schedule at a high level. This would allow us to conduct both quantitative and qualitative analysis to assess the risk properly before making any changes to the project schedule.

Did I do something wrong?
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Prateek -

No - if the slippage is just a potential but not a guarantee, you shouldn't be forecasting it in the schedule. It is advisable to understand and advise risk stakeholders of the potential schedule impacts to encourage them to take appropriate measures to respond to the risk.

Kiron
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada

Prateek, I believe your approach was reasonable, as it focused on proactive risk management rather than prematurely modifying the schedule for a potential delay which is aligned with good project management practices.

If slippage is shown in the schedule before it actually occurs, stakeholders may passively accept the delay instead of taking steps to mitigate it.
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany

Hi Prateek,
There is the actual schedule, which should reflect facts as well as possible, and schedule scenarios that show potential effects of risks (what if ..). Your program manager looks at the complete picture and needs to anticipate risks for activities down the line, not in your project.



Your caution about the perception of team members is valid.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
The key thing is to define a risk management process and make it visible to all the stakeholders. You do not need to do nothing in the current project documentation except for the deliverable you define in your risk management process. Risk and issues must be put on the table into each project review then all related to them will be visible.
avatar
Md. Golam Rob Talukdar
Community Champion
Project Manager| AWR Development (BD) Ltd. Cox's Bazer , Bangladesh
Prateek -
Absolutely right No,
But then it occurred to me that getting into a conflict with the program manager could be a career risk. The root cause needs to know why he said this.

Golam

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Anyone who is capable of getting themselves made president should on no account be allowed to do the job."

- Douglas Adams

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters