A project manager is assigned to a new software development project. During the initiation phase, the project sponsor is hesitant to approve the project charter because the business case does not clearly quantify the expected benefits. The project manager has gathered initial requirements and conducted a feasibility study. What should the project manager do next to move the project forward?
The charter is blocked by an unquantified business case, so the project manager must collaborate with the sponsor to express benefits in measurable financial terms. Refining the business case addresses the approval constraint directly, rather than proceeding to planning or re-running the feasibility study.
Why this answer
The sponsor's concern is that the business case lacks quantified benefits, which is a prerequisite for charter approval. The project manager should collaborate with the sponsor to refine the business case and make the benefits measurable, addressing the root cause before seeking approval. This keeps the project moving while respecting the sponsor's gatekeeping role in initiation.
Exam trap
PK0-005 often tests the instinct to escalate or proceed when a stakeholder raises a concern — candidates may pick escalation, but the exam expects the PM to first collaborate and resolve the issue at the source.
How to eliminate wrong answers
Option A is wrong because proceeding to planning without an approved charter violates the initiation-to-planning sequence; the charter authorizes the project and the PM. Option B is wrong because escalation is premature — the PM has not yet attempted to resolve the issue directly with the sponsor, and escalation should be a last resort. Option D is wrong because ignoring the sponsor's concern is insubordinate and risks charter rejection; the sponsor's approval is required.