I thought (d) would be the answer to the following question? But the practice tool showed it as wrong, I was wondering, why? I thought first step a PM should take would be what is described in choice (d)
During project execution, a stakeholder requests a change to ensure that the final product will stratify their requirements? What should the project manager do next?
a) Approve the request only if will not have impact on budget or schedule b) Submit a change request, as per the project's change control process c) Reject the request and record it in the product backlog d) Ask the team to determine the impact on the request on budget and schedule Saving Changes...
The correct answer should be b) Submit a change request, as per the project's change control process.
This is the first thing you need to do as a project manager, to ensure that the change is registered, assessed, and approved/rejected, during the change control process. Saving Changes...
Khai Ng.IT PMO | IT Project Manager| TTGROUPHanoi, Viet Nam
The answer is b) Submit a change request. Any role can fill a CR form and submit it. This activity triggers Change Request Process. Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
Stratify: 'to arrange the different parts of something in separate layers or groups'
My first response would be to question if this is in fact a change and, if so, how it would enhance the deliverable.
Option b) allows: 1) the stakeholder to clearly define what it is he wants to see, 2) the PM to determine if it is in fact a change, 3) if a change, a determination if it comply with the intent of the project and 4) other stakeholders (rarely is there only one stakeholder) input as to how this requests affects them.
b) it is
...
1 reply by Raz Sid
Feb 25, 2021 10:32 AM
Raz Sid
...
Peter, Sorry, "stratify" was a typo on my part. It was "satisfy". But the entire context is still the same. Now back to the substance: When they ask "What should the project manager do NEXT?" I translated it as "what would be the FIRST step PM should take"; and so I thought PM would first investigate the issue (impact etc.) before submitting it to CCB. Is it ok to submit the request to CCB without investigating first? Or, I may not be understanding the context here?
Stratify: 'to arrange the different parts of something in separate layers or groups'
My first response would be to question if this is in fact a change and, if so, how it would enhance the deliverable.
Option b) allows: 1) the stakeholder to clearly define what it is he wants to see, 2) the PM to determine if it is in fact a change, 3) if a change, a determination if it comply with the intent of the project and 4) other stakeholders (rarely is there only one stakeholder) input as to how this requests affects them.
b) it is
Peter, Sorry, "stratify" was a typo on my part. It was "satisfy". But the entire context is still the same. Now back to the substance: When they ask "What should the project manager do NEXT?" I translated it as "what would be the FIRST step PM should take"; and so I thought PM would first investigate the issue (impact etc.) before submitting it to CCB. Is it ok to submit the request to CCB without investigating first? Or, I may not be understanding the context here? Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
The clarification does not alter my response. Option d) requires effort, effort that may not be warranted. That determination should be with the CCB.
The Change Control Board is a group within the prject team responsible for making decisions related to project changes. Depending on their composition and mandate they would be in the best position to determined if applying effort is appropriate. Saving Changes...
It really depends on the change control process whether or not any investigation is required to submit the change request.
It is common for the process to start out by generating a formal change request so that it is recorded in the change management system, prior to any investigation at all. Then the team may be instructed to develop a rudimentary investigation of feasibility and impact (Phase 1). The result of that may determine it has minimal impact, major impact, or requires more study before any decision may be reached (Phase 2), prior to a formal determination of offerability and pricing. Phase 2 can be costly and time consuming so often there is a preliminary decision of whether or not it is even worth investigating further.
We sometimes refer to Phase 1 as a ROM (rough order of magnitude) estimate, and Phase 2 a commitment level estimate.
...
1 reply by Raz Sid
Feb 25, 2021 12:27 PM
Raz Sid
...
Keith,
Thank you for providing a bit more detailed explanation of why (d) may not be a good (or at least best) choice here - as Peter also stated "(d) requires effort...". Now I know why (b) is the best choice of given choices.
It really depends on the change control process whether or not any investigation is required to submit the change request.
It is common for the process to start out by generating a formal change request so that it is recorded in the change management system, prior to any investigation at all. Then the team may be instructed to develop a rudimentary investigation of feasibility and impact (Phase 1). The result of that may determine it has minimal impact, major impact, or requires more study before any decision may be reached (Phase 2), prior to a formal determination of offerability and pricing. Phase 2 can be costly and time consuming so often there is a preliminary decision of whether or not it is even worth investigating further.
We sometimes refer to Phase 1 as a ROM (rough order of magnitude) estimate, and Phase 2 a commitment level estimate.
Keith,
Thank you for providing a bit more detailed explanation of why (d) may not be a good (or at least best) choice here - as Peter also stated "(d) requires effort...". Now I know why (b) is the best choice of given choices. Saving Changes...
