PMP · Question #929
A project manager is assigned to a critical project to build a complex application for a client whose goal is to achieve an ideal state for their business model, but is unsure about how to achieve…
The correct answer is C. Request that proper stakeholders, including the client, are assigned. When a client has an ideal business goal but lacks clarity on the solution for a complex application, the project manager should ensure all relevant stakeholders, including the client, are actively assigned and involved in the collaboration model.
Question
Options
- AAsk the client to specify their business needs in a contract format and approve it.
- BSchedule quarterly review meetings with the client.
- CRequest that proper stakeholders, including the client, are assigned.
- DAsk the project team to write the business requirements based on the client's needs.
How the community answered
(55 responses)- A7% (4)
- B4% (2)
- C71% (39)
- D18% (10)
Why each option
When a client has an ideal business goal but lacks clarity on the solution for a complex application, the project manager should ensure all relevant stakeholders, including the client, are actively assigned and involved in the collaboration model.
Asking the client to specify all business needs in a contract format upfront is characteristic of a traditional, fixed-scope approach, which is unsuitable when the client is 'unsure about how to achieve the solution' for a complex application.
Quarterly review meetings provide infrequent feedback, which is insufficient for a complex project where the solution path is unclear and continuous client input is needed to navigate uncertainties and define the ideal state.
For a complex project where the client knows their goal but not the solution, close collaboration and continuous input are essential. By ensuring that proper stakeholders, including key client representatives, are assigned roles and actively participate, the project team can iteratively define requirements, validate solutions, and co-create the application that meets the evolving 'ideal state' vision, fostering shared understanding and joint problem-solving.
While the project team helps elaborate requirements, asking them to write business requirements based on the client's needs without direct, continuous client involvement risks misinterpretation and a solution that doesn't truly align with the client's evolving ideal state.
Concept tested: Client collaboration in complex, ambiguous projects; stakeholder involvement
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/project-stakeholder-management
Topics
Community Discussion
7Confirmed C on exam last week. The key phrase is the client being unsure how to achieve the solution, which means you need heavy collaboration with the right people in the room from the start. Requesting proper stakeholders including the client gets everyone aligned on the vision and keeps the discovery process moving forward together. The other options either push the work back on the client or the team without actually fostering that collaborative relationship you need when the path is unclear.
C is correct because the client knows the desired end state but not the path to get there, which means you need heavy stakeholder collaboration to surface and refine requirements as the project unfolds. Getting the right stakeholders assigned, including the client, is the prerequisite for any iterative discovery work. A and D jump straight to documented requirements too early when the client is still uncertain. B alone is just a cadence, not a collaboration model, and quarterly is way too sparse for a complex application where the solution is unclear. Saw this on my exam last week and almost picked A because it sounded like proper contract
Agree C is correct. The stem says client is unsure how to achieve solution, so you need proper stakeholders assigned to collaborate.
Agreed on C, and would add that the "unsure how to achieve" language is also pointing you toward a proof-of-concept or design session before any actual build work, so the stakeholder assignment is step one, not the whole answer.
Going with C here since the client knows the end goal but not the path to get there, you need all the right stakeholders engaged to figure it out together. Quick question for anyone who has taken the exam recently, does the PMP still frame this as a collaboration model specifically, or is it more about stakeholder engagement in general?
Going with B here. When the client knows the end goal but not the path to get there, you need structured collaboration points built into the timeline so the team and client can iteratively refine what the solution looks like, and quarterly reviews give you that recurring checkpoint without overwhelming the process.
Actually C is the right call here, Anjali. When the client knows the destination but not the exact route, you want frequent feedback loops built into the delivery itself, not formal quarterly reviews that come too late to course-correct.