Project Management

Please login or join to subscribe to this thread

Would you do a change request if specific risk didn't occur and therefore, you didn't need the related contingency reserve?

linkedin twitter facebook  
avatar
Soha Karjawally Software development manager / Program Manager| Phoenix - USA Montréal, Quebec, Canada
Would you do a change request if specific risk didn't occur and therefore, you didn't need the related contingency reserve? What was the threshold used?

OR will you keep it as a buffer/reserves in case another unknown unknown occurs (other than those planned)? Then in this case, how would you explain/appear in front of the change board asking for a new change request for the opposite? Not justifying padding but I guess similar cases exist...

Thanks.
Sort By:
< 1 2 >
avatar
Tarun Nair Adoor, Kerala, India
avatar
Kamran Rezwanul Hakim Dhaka, Bangladesh
I would file for a change request only if a large amount of resources (financial, human, etc.) were earmarked/allocated to respond to that specific risk and only when I was absolutely certain that this was a phase-specific risk which won't be carried forward into the next one. If that isn't the case, it wouldn't be prudent to ask for contingency reserves to be withdrawn.

I'll need a bit more elaboration on the second part of your question.
...
1 reply by Soha Karjawally
Jun 20, 2020 11:23 AM
Soha Karjawally
...
Thanks, Kamran for your input.
In the second part, I was thinking that don't we lose our credibility if we do change requests for every single deviation we have in the project knowing that the decision-makers usually find this process heavy.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Soha -

I think we need to separate theory from practical application.

A good practice is to tie contingency reserves to specific milestones along the life of your projects so as those milestones are achieved, any unused contingency reserves would be returned to funding bodies.

I have also seen cases where contingency reserves are held in the project till the very end even if the identified risks which had been used to quantify/justify those reserves have expired. While this is not "by the book", decision makers also don't like to be hit with administrative change requests. The risk in doing this, of course, is that these reserves get abused for funding scope changes. It also represents an opportunity cost at the portfolio level to unnecessarily tie up funds.

Kiron
...
1 reply by Soha Karjawally
Jun 20, 2020 11:27 AM
Soha Karjawally
...
Thank you, Kiron,
I've seen in some cases Management/PMO would ask for a quick forecast to balance some resources between the projects to adjust the portfolio budget. Otherwise, knowing that it is not by the book, I've rarely seen PM returning reserves.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Project costs monitoring and control has to be performed along the project. While it depends on each project governance process defined into the organization the money for project risks that have not been materialized is debited from the project budged. Because of that, project risks must be correctly defined mainly the related dates. Then, no change request is needed.
...
1 reply by Soha Karjawally
Jun 20, 2020 11:31 AM
Soha Karjawally
...
Sergio,

That's interesting, thank you.
It would be great if we attain that level of maturity :)
avatar
Soha Karjawally Software development manager / Program Manager| Phoenix - USA Montréal, Quebec, Canada
Jun 20, 2020 4:34 AM
Replying to Kamran Rezwanul Hakim
...
I would file for a change request only if a large amount of resources (financial, human, etc.) were earmarked/allocated to respond to that specific risk and only when I was absolutely certain that this was a phase-specific risk which won't be carried forward into the next one. If that isn't the case, it wouldn't be prudent to ask for contingency reserves to be withdrawn.

I'll need a bit more elaboration on the second part of your question.
Thanks, Kamran for your input.
In the second part, I was thinking that don't we lose our credibility if we do change requests for every single deviation we have in the project knowing that the decision-makers usually find this process heavy.
avatar
Soha Karjawally Software development manager / Program Manager| Phoenix - USA Montréal, Quebec, Canada
Jun 20, 2020 8:31 AM
Replying to Kiron Bondale
...
Soha -

I think we need to separate theory from practical application.

A good practice is to tie contingency reserves to specific milestones along the life of your projects so as those milestones are achieved, any unused contingency reserves would be returned to funding bodies.

I have also seen cases where contingency reserves are held in the project till the very end even if the identified risks which had been used to quantify/justify those reserves have expired. While this is not "by the book", decision makers also don't like to be hit with administrative change requests. The risk in doing this, of course, is that these reserves get abused for funding scope changes. It also represents an opportunity cost at the portfolio level to unnecessarily tie up funds.

Kiron
Thank you, Kiron,
I've seen in some cases Management/PMO would ask for a quick forecast to balance some resources between the projects to adjust the portfolio budget. Otherwise, knowing that it is not by the book, I've rarely seen PM returning reserves.
avatar
Soha Karjawally Software development manager / Program Manager| Phoenix - USA Montréal, Quebec, Canada
Jun 20, 2020 8:53 AM
Replying to Sergio Luis Conte
...
Project costs monitoring and control has to be performed along the project. While it depends on each project governance process defined into the organization the money for project risks that have not been materialized is debited from the project budged. Because of that, project risks must be correctly defined mainly the related dates. Then, no change request is needed.
Sergio,

That's interesting, thank you.
It would be great if we attain that level of maturity :)
...
1 reply by Sergio Luis Conte
Jun 20, 2020 1:38 PM
Sergio Luis Conte
...
Plese let me say. Is not about maturity. Is about what the project manager accept as her/his mission. Believe me, my actual work place has very low maturity on the matter but what I have to do? Being a change agent is about this not about lot if things people and organizations say outsiide there. Obviously, you have to do your own cost/benefit analisys
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Jun 20, 2020 11:31 AM
Replying to Soha Karjawally
...
Sergio,

That's interesting, thank you.
It would be great if we attain that level of maturity :)
Plese let me say. Is not about maturity. Is about what the project manager accept as her/his mission. Believe me, my actual work place has very low maturity on the matter but what I have to do? Being a change agent is about this not about lot if things people and organizations say outsiide there. Obviously, you have to do your own cost/benefit analisys
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
Soha,

I agree that decision makers generally don't like to deal with small project deviations. In the scenario you described I would create a table showing the risks that didn’t occur and the contingency funds I could return to the funding center. I’d then post the table somewhere and inform the decision makers about it, explaining that I’ll keep the funds within my project to cover unknown unknowns unless they request them back, and that I would update the table throughout the project. This gives the decision makers the option to reabsorb the funds at any time while avoiding the hassle of processing many change requests. In my experience most decision makers have no problem leaving the unused contingency funds attached to the project until its conclusion.
...
2 replies by ARPAN MAGOO and Soha Karjawally
Jun 21, 2020 11:49 AM
Soha Karjawally
...
Nice, easy, and practical way! Thanks, Eric.
Jun 27, 2020 3:30 PM
ARPAN MAGOO
...
Among all thoughts, I agree with this, We are also using same strategy in our project.
avatar
Soha Karjawally Software development manager / Program Manager| Phoenix - USA Montréal, Quebec, Canada
Jun 21, 2020 11:27 AM
Replying to Eric Simms
...
Soha,

I agree that decision makers generally don't like to deal with small project deviations. In the scenario you described I would create a table showing the risks that didn’t occur and the contingency funds I could return to the funding center. I’d then post the table somewhere and inform the decision makers about it, explaining that I’ll keep the funds within my project to cover unknown unknowns unless they request them back, and that I would update the table throughout the project. This gives the decision makers the option to reabsorb the funds at any time while avoiding the hassle of processing many change requests. In my experience most decision makers have no problem leaving the unused contingency funds attached to the project until its conclusion.
Nice, easy, and practical way! Thanks, Eric.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS
ADVERTISEMENT

Sponsors