PMI-ACP Exam Dumps - PMI Agile Questions and Answers

A product roadmap is a strategic plan that outlines the vision for the product, the business objectives that need to be achieved, and the timeframes for delivering key milestones or features. It provides a high-level overview of the product ' s development, aligning the team and stakeholders on the product ' s direction and the expected delivery timeline.

Product vision defines what the product aims to achieve and the value it will deliver to customers or the business.

Business objectives outline what the product aims to accomplish in terms of business impact, like increasing revenue or improving customer satisfaction.

Timeframes indicate when key milestones or releases are planned to occur, ensuring that progress can be tracked and expectations set.

This high-level structure is essential for guiding product development and keeping stakeholders aligned, without delving into the specific details of design or project management, which are more suited for other planning documents.

In this situation, the Scrum Master observes that the developer is confused about a business rule during the daily coordination meeting. The best approach is to address the issue directly with the developer after the meeting. This ensures that the developer receives the clarification they need without disrupting the flow of the meeting or drawing unnecessary attention to the issue during the daily standup.

The correct answer is B – Align with stakeholder expectations and releasable product increments.

In Agile, sprint or iteration reviews provide an opportunity for the team to present completed work and validate it against stakeholder expectations. Demonstrations should showcase working, potentially shippable increments that align with business goals and value delivery.

From the PMI Agile Practice Guide:

“The purpose of iteration reviews is to showcase a working product increment. The review should focus on what was completed and how it aligns with stakeholder expectations and business objectives.”

(PMI Agile Practice Guide, Section 3.5 – Iteration Review)

PMBOK® Guide further reinforces this point:

“The team should deliver functional product increments that are valuable to stakeholders. These should be validated for alignment with scope and business value.”

(PMBOK® Guide, 6th Edition, Section 5.5 – Validate Scope)

Mike Griffiths notes:

“Product demonstrations should confirm stakeholder needs are being met. The team’s focus should be on verifying value delivery, product completeness, and stakeholder alignment.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery / Stakeholder Feedback)

Why other options fall short:

A is valuable context, but doesn’t directly ensure demonstration success.

C reflects team improvement but is not the purpose of a product demo.

D speaks to collaboration, not validation of stakeholder alignment.

Answer: B

The correct answer is C – Use class of service. In Kanban, the Class of Service (CoS) model is a key technique for prioritization and flow management. It helps teams decide which work items should be expedited, delayed, or treated as standard. Using CoS enables teams to handle tasks based on urgency, business value, and risk.

From PMI Agile Practice Guide:

“Classes of service define the rules by which work is selected, prioritized, and delivered. They help make prioritization policies explicit and transparent to stakeholders and team members.”

(PMI Agile Practice Guide, Section 5.4 – Kanban and Flow-Based Approaches)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Class of service models—such as ‘Expedite’, ‘Fixed Delivery Date’, ‘Standard’, or ‘Intangible’—allow teams to prioritize tasks by business value, risk, and urgency. This is particularly useful in Kanban systems where items flow continuously.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery / Kanban Practices)

Option A (involving the product owner) is more applicable to Scrum teams; Kanban teams often have shared ownership of flow.

Option B (reviewing WIP limits) affects flow but doesn’t guide task prioritization.

Option D (measuring lead time) helps with process analysis but not immediate prioritization.

Answer: C

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

Gold-plating—adding extra features not requested or prioritized—is an anti-pattern in agile. Agile emphasizes delivering the highest-priority features first, and product changes should always go through the Product Owner for prioritization and validation.

According to the PMI Agile Practice Guide (Section 5.1: Backlog and Value Delivery) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), when capacity is available, the team should pull more stories from the prioritized backlog, ensuring that all work aligns with stakeholder-defined value.

Option D is correct: confirm backlog priority and use time to deliver customer-prioritized value.

Option A supports scope creep.

Option B is partially correct but doesn’t optimize the time to deliver value.

Option C perpetuates gold-plating and undermines value alignment.

The MoSCoW method (Must have, Should have, Could have, Won’t have) is a prioritization technique commonly used in agile to determine which stories deliver the most value. The PMI Agile Practice Guide (Section 5.1: Prioritization Techniques) lists MoSCoW as one of the methods used by product owners and teams to prioritize backlog items.

Option A is correct: MoSCoW is a proven agile prioritization method.

Option B is used for estimation, not prioritization.

Option C is not a standard agile prioritization method.

Velocity is a measure of the amount of work a team can handle during a sprint, typically measured in story points. While it can fluctuate slightly from sprint to sprint, the goal is to have velocity stabilize over time, as this helps in forecasting future sprints and planning. An increase in velocity from 27 to 35 could indicate an improvement in the team ' s capacity to deliver, which should be celebrated if it aligns with the team ' s capabilities. However, a stable velocity over time is what typically matters for predictability and planning.

The correct answer is A – Explore options for increasing knowledge in the next iteration ' s backlog.

One of the key principles of Agile is continuous learning and improvement. When the team identifies a skills gap during a retrospective, the appropriate response is to turn that learning need into actionable items in the upcoming backlog. This can include training, pairing, spikes, or experimenting in a time-boxed way during the next iteration.

From the PMI Agile Practice Guide:

“Teams should regularly inspect their tools, practices, and outcomes and incorporate improvement actions into their backlog. Continuous learning is a shared responsibility.”

(PMI Agile Practice Guide, Section 3.5 – Retrospectives and Section 6.2 – Coaching the Agile Team)

Mike Griffiths also supports this:

“Improvement actions should be planned, prioritized, and implemented like any other work. Skills development should be addressed through backlog items such as training, spikes, or pairing.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement)

Why the other options fall short:

B adds scope mid-sprint, which violates Agile principles (sprint backlog should remain stable).

C may be viable long-term, but doesn’t address the team ' s agreed goal of learning the tool.

D brings in an external expert rather than empowering the team to grow their capabilities.

Answer: A

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

This approach reinforces the core values of agile, particularly the idea that a self-managed team should be collaborative and support one another. The agile lead should focus on creating a safe environment where team members feel comfortable sharing challenges and asking for help. This will not only help the junior team member but also improve the overall team dynamics and performance by fostering a culture of openness and mutual support.