A local government provides subsidies for energy-efficient activities. An Organization plans a project to install solar panels to reduce energy costs. After the solar panel project has started, the government announces that solar panels may not continue to qualify for subsidies. What should the project manager do?
a) Create a change request.
b) Update the issue log.
c) Use the contingency reserve.
d) Raise the risk level.
According to me I think its option A.Reasoning -As per the question government announce the change in law and project has already started.So the project manager should create change request to accommodate the changes because of this new law. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Hey Keith and Rami, I'll stick to my guns. Nowhere in the PMBOK Guide does it even hint at a relationship between a triggered risk and an issue. If anything, the PMBOK Guide 6 is woefully silent on issue management.
...
1 reply by Rami Kaibni
May 19, 2020 11:23 PM
Rami Kaibni
...
Stephane
Why is your gun single loaded ? The PMBOK is not the onlty reference and it is not all inclusive. If something is not mentioned there is doesn't mean it doesn't exist.
On a project level, this might not be as obvious because you manage risk in a risk register but when it comes to program and portfolios, when a risk occur in a project that affects the program or portfolio, it is reflected as an issue. There is a close relation between the Risk Register and the Issue Register. As a matter of fact, and I am not sure if it is a coincidence or not but one of the question I got in my Portfolio Exam was related to this and it asks what if the probably of a risk is 100%, the answer was obvious it will be an issue.
Likewise in business analysis, especially when doing business analysis for cybersecurity, there is a fine line between both.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
May 19, 2020 9:12 PM
Replying to Stéphane Parent
...
Hey Keith and Rami, I'll stick to my guns. Nowhere in the PMBOK Guide does it even hint at a relationship between a triggered risk and an issue. If anything, the PMBOK Guide 6 is woefully silent on issue management.
Stephane
Why is your gun single loaded ? The PMBOK is not the onlty reference and it is not all inclusive. If something is not mentioned there is doesn't mean it doesn't exist.
On a project level, this might not be as obvious because you manage risk in a risk register but when it comes to program and portfolios, when a risk occur in a project that affects the program or portfolio, it is reflected as an issue. There is a close relation between the Risk Register and the Issue Register. As a matter of fact, and I am not sure if it is a coincidence or not but one of the question I got in my Portfolio Exam was related to this and it asks what if the probably of a risk is 100%, the answer was obvious it will be an issue.
Likewise in business analysis, especially when doing business analysis for cybersecurity, there is a fine line between both.
RK
...
1 reply by Stéphane Parent
May 20, 2020 9:01 AM
Stéphane Parent
...
When a risk is realized, I put the contingency plan into action. Does the realized risk have an impact on my project? Sure. My contingency plan is a pre-approved change request that is covered by my contingency reserve. But an issue? Given that my contingency plan will be added to the project schedule, why do I also need to track it in my issue log? If you want it highlighted, you can have an associated milestone.
If the risk was unforeseen or without a contingency plan then, yes, I agree you have an issue. (In fact, you could have two issues: the realized risk and the lack of foresight.)
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
May 19, 2020 11:23 PM
Replying to Rami Kaibni
...
Stephane
Why is your gun single loaded ? The PMBOK is not the onlty reference and it is not all inclusive. If something is not mentioned there is doesn't mean it doesn't exist.
On a project level, this might not be as obvious because you manage risk in a risk register but when it comes to program and portfolios, when a risk occur in a project that affects the program or portfolio, it is reflected as an issue. There is a close relation between the Risk Register and the Issue Register. As a matter of fact, and I am not sure if it is a coincidence or not but one of the question I got in my Portfolio Exam was related to this and it asks what if the probably of a risk is 100%, the answer was obvious it will be an issue.
Likewise in business analysis, especially when doing business analysis for cybersecurity, there is a fine line between both.
RK
When a risk is realized, I put the contingency plan into action. Does the realized risk have an impact on my project? Sure. My contingency plan is a pre-approved change request that is covered by my contingency reserve. But an issue? Given that my contingency plan will be added to the project schedule, why do I also need to track it in my issue log? If you want it highlighted, you can have an associated milestone.
If the risk was unforeseen or without a contingency plan then, yes, I agree you have an issue. (In fact, you could have two issues: the realized risk and the lack of foresight.)
...
1 reply by Rami Kaibni
May 20, 2020 11:56 AM
Rami Kaibni
...
This is one approach only that is suitable within a Project in isolation but that’s not how it works when things escalate from Projects and feed into Programmes to Portfolios.
In all cases, this discussion is probably outside the scope of this thread so I will agree to disagree for now. Cheers !
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
May 20, 2020 9:01 AM
Replying to Stéphane Parent
...
When a risk is realized, I put the contingency plan into action. Does the realized risk have an impact on my project? Sure. My contingency plan is a pre-approved change request that is covered by my contingency reserve. But an issue? Given that my contingency plan will be added to the project schedule, why do I also need to track it in my issue log? If you want it highlighted, you can have an associated milestone.
If the risk was unforeseen or without a contingency plan then, yes, I agree you have an issue. (In fact, you could have two issues: the realized risk and the lack of foresight.)
This is one approach only that is suitable within a Project in isolation but that’s not how it works when things escalate from Projects and feed into Programmes to Portfolios.
In all cases, this discussion is probably outside the scope of this thread so I will agree to disagree for now. Cheers ! Saving Changes...
Sticking to the question, I think in this particular instance, the keyword is "may". Since it is not yet a certain event, it can't be an issue. It is a risk and with the known additional information (that govt may no longer qualify solar panels for subsidies) warrant a raise in the risk level (probability & impact). If no action is taken, then yes it can turn into an issue.
This is very poorly drafted question.
And the options given are also poorly drafted. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Regarding issues, PMBoK glossary defined it as
- a current condition/situation that may have impact on project objectives
and in 4.3.3 it says issues are
- problems, gaps, inconsistencies, conflicts that occur unexpectedly and that require action so they do not impact project performance
Explicitly it says also, 'issues arise as the result of occurred risks', and 'unmanaged threats may result in issues'
I think a difference between a problem and an issue is that with an issue the solution can be already known (like a contingency plan), while with a problem we still have to engage in solutioning (quote: a problem exists when we do not know what to do). Saving Changes...
Community Champion
