Question 571 · 1401 in bank
An organization is struggling to start an important project. The project manager has identified that the scope definition is the main item preventing the project from starting. Although most of the scope items are defined and agreed upon among the stakeholders, there are a few items that are hard to grasp and very complex to define at this stage. What should the project manager do?
Show answer
Answer: A
Explanation
Ans D: If we have to really make an argument about this - How many times do we really come across a scenario where a part of project is chosen to be in Predictive approach and a part on Agile. Its not going to happen in reality! And even if some requirements are known, who would go back to a Predictive approach. Nowhere it says that if requirements are clear, you cannot do Agile. The issue is part of the scope is not well defined, hard to grasp and complex. I would go with D where you update the Risk register, Escalate the issue to management and ask for resources to define the scope well. D is the right fit.
Source: Adapted from community discussion — psvexam