Free PMI-ACP PMI Updates

The correct answer is B – It prevents a wasteful buildup of requirements inventory that may never be processed. Rolling wave planning is a core agile planning practice where detailed planning is deferred until closer to execution. It aligns with lean principles by avoiding over-specification and prioritizing only near-term, high-value work.

From the PMI Agile Practice Guide:

“Rolling wave planning minimizes wasted effort by only detailing work that is near execution. Planning further ahead can result in rework or unused artifacts if requirements change or become irrelevant.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning and Rolling Wave Planning)

Mike Griffiths writes:

“Agile avoids big upfront planning. Rolling wave planning reduces waste, improves responsiveness, and focuses on delivering the highest-value features first while leaving less valuable work unplanned until necessary.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A is misleading; agile allows varying levels of detail, not fixed.

C is a traditional (waterfall) planning mindset.

D suggests fixed scope per release, which contradicts agility.

Answer: B

────────────────────────────────────

The correct answer is C — Work with the product owner to assess the impact for reprioritization.

Agile recognizes that new priorities may emerge during a sprint. The product owner owns the backlog and prioritization. If a request threatens sprint commitments, it should be reviewed and discussed with the product owner to determine the trade-offs and make informed decisions.

PMI Agile Practice Guide:

“New requests should be assessed in collaboration with the product owner. The team should make prioritization trade-offs in a transparent manner to maintain focus on delivering value.”

(PMI Agile Practice Guide, Section 5.5 – Iteration Planning and Section 5.7 – Change Management)

Mike Griffiths:

“Product owners are responsible for backlog prioritization. When urgent issues arise, teams should discuss them with the PO rather than unilaterally shifting focus.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A risks burnout and violates sustainable pace.

B avoids accountability.

D assumes the change can wait, which may not align with customer needs.

Answer: C

—

The correct answer is A — Stakeholders should have regularly been engaged to obtain feedback and reduce the functionality risk.

In Agile, stakeholder engagement and iterative feedback loops ensure that the solution being built is aligned with business value. Simply meeting documented requirements is insufficient. Agile practices such as demos and user feedback sessions minimize the risk of building features that fail to deliver value.

PMI Agile Practice Guide:

“Agile emphasizes ongoing stakeholder engagement. Demonstrating working software at the end of each iteration and gathering feedback ensures that the product is delivering business value.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths states:

“Value-driven delivery is achieved not just by delivering what was asked for, but by ensuring it actually meets customer needs. Regular feedback from stakeholders is critical to avoid building low-value features.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B refers to the lean principle of “decide as late as possible,” but feedback, not delay, would have addressed the issue.

C is unrelated to this context.

D lacks the collaborative engagement approach emphasized in Agile.

Answer: A

—

The correct answer is A – Inform the stakeholder that all updates are provided in the sprint review sessions and encourage them to attend.

The Sprint Review is designed to provide transparency to stakeholders, demonstrate completed work, and gather feedback. Stakeholders should be encouraged to attend these events to stay updated and engaged.

From the PMI Agile Practice Guide:

“Sprint reviews are intended to engage stakeholders in reviewing completed work and discussing priorities. This event ensures transparency and encourages stakeholder collaboration.”

(PMI Agile Practice Guide, Section 5.5 – Stakeholder Engagement)

Mike Griffiths adds:

“Agile teams encourage stakeholder participation in regularly scheduled review meetings to maintain alignment and foster transparency.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options:

B adds non-Agile overhead and undermines Agile transparency mechanisms.

C and D are dismissive and uncollaborative, potentially damaging relationships.

Answer: A

══════════════════════════════════════════════════