Legit PMP Exam Download

For a fixed time-and-budget engagement with an uncertain-scope core component, the contract should explicitly manage financial exposure created by agile discovery. Tiering the contract (D) separates predictable, well-defined deliverables under fixed terms from the uncertain component under agile terms (e.g., timeboxed iterations, capped spend, or negotiated backlog). This creates transparency for governance and protects margin by preventing agile uncertainty from overrunning fixed-price assumptions. Limiting the number of iterations (E) is a direct cost-control mechanism that enforces timeboxing and a hard cap on effort, helping keep profitability intact while still allowing iterative refinement. A governance committee (A) can improve oversight but does not directly cap cost. Requiring only internal resources (B) is an organizational staffing constraint, not a contract control for scope uncertainty, and may reduce flexibility. Providing “alternatives to scope change” at phases (C) is vague and less effective than explicit commercial structures and iteration caps for agile work.

==========

When stakeholders report poor coordination and limited progress visibility across dependent work streams, the project manager should address the system that governs information flow, coordination mechanisms, and reporting—not just hold a one-off meeting. Reviewing and updating the communications management plan (C) is the best action because it defines how progress is captured, how dependencies are managed and communicated, what forums exist (scrums-of-scrums, integration checkpoints, cross-stream planning), what reporting artifacts are used (dashboards, dependency boards, milestone charts), and the frequency/ownership of updates. A team status meeting (B) can be a short-term tactic, but it doesn’t fix the structural gap that created the visibility problem. Escalating to sponsor or steering committee (A, D) is unnecessary as a first response; escalation is appropriate only if the PM cannot implement the needed communications/coordination improvements or if decisions exceed authority. Updating the plan restores alignment on expectations, improves transparency, and provides repeatable governance for multi-stream coordination—directly supporting stakeholder engagement and predictable delivery.

==========

This question belongs to the People domain because it concerns stakeholder communication and engagement. PMI communication guidance explains that effective communication requires messages to be received, understood, and acted upon where appropriate, and PMI stakeholder guidance notes that stakeholder plans should be revisited as projects evolve and new needs emerge.

Because multiple stakeholders are requesting updates only a few weeks into the project, the clearest signal is that the current communication approach does not fully meet their information needs. The best response is to schedule a meeting with relevant stakeholders to review the project communications plan. This allows the project manager to clarify update frequency, format, reporting channels, and stakeholder expectations in a structured way. Option A is too dismissive and weakens stakeholder engagement. Option C is inappropriate because daily standups are not meant to become broad stakeholder reporting sessions. Option D is clearly wrong and contrary to PMI stakeholder management principles. PMP-style reasoning favors tailoring communications to stakeholder needs and formally adjusting the communications approach when those needs are not being met.

This question belongs to the People domain because it focuses on stakeholder communication and engagement. When business unit managers complain about not receiving updated project information, the likely issue is that stakeholder information needs are not being met by the current communication approach. PMI guidance emphasizes planning communications systematically and tailoring them to stakeholder needs. Reviewing the communications management plan and the stakeholder register is the most appropriate next step because those artifacts define who needs what information, how often, and through which channels.

Option A is not the main issue, because the complaint is about information flow rather than role ownership. Option B may help some stakeholders, but it assumes meetings are the right answer for everyone without checking actual needs. Option D is unrelated, since Monte Carlo simulation is a quantitative risk-analysis technique, not a communication diagnostic tool. PMP-style reasoning favors first reviewing the planned communication approach and stakeholder records, then adjusting communication methods as needed. This ensures the response is structured, targeted, and aligned with official communication management practices.