PMI-ACP Exam Dumps - PMI Agile Questions and Answers

Agile emphasizes just enough detail to start work and adapt through ongoing conversation. According to the PMI Agile Practice Guide (Section 5.2 Requirements and User Stories), stories should be clear enough for estimation and discussion, but not over-specified. The INVEST model (Independent, Negotiable, Valuable, Estimable, Small, Testable) supports this.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reiterates that stories should not contain exhaustive detail up front; rather, they evolve through collaborative dialogue with the product owner.

Option C is correct because it supports collaboration and adaptive planning.

Option A and B lead to over-specification and undermine agility.

Option D addresses testing but doesn’t resolve confusion about appropriate story detail.

In Agile, it ' s important to maintain focus on the current sprint ' s goals and scope. Since the sprint deadline is approaching, adding additional features may compromise the team ' s ability to deliver the planned work on time. The best approach is to explain to the client that the new features can be considered for the next sprint, ensuring that the team can finish the current work and deliver value on time. This also allows the team to properly plan for the new features in the next iteration without overloading the current sprint.

The correct answer is D — Work with the team to analyze the market opportunity and create a tailored agile approach if needed.

Agile promotes context-based tailoring. Just because an approach works well in one project doesn’t guarantee it will fit another. The agile leader should collaborate with the team to analyze current needs and adapt or design the most suitable process accordingly.

PMI Agile Practice Guide:

“There is no one-size-fits-all approach. Agile methods should be tailored to suit the project context and objectives.”

(PMI Agile Practice Guide, Section 2.1 – Tailoring Agile)

Mike Griffiths:

“Teams must evaluate project needs and customize their process accordingly. Blind reuse of past methods often fails to address unique challenges.”

(PMI-ACP Exam Prep, Chapter 1 – Agile Principles and Mindset)

Incorrect options:

A involves stakeholders, but D emphasizes team and tailoring for delivery.

B ignores the unique needs of the new project.

C undermines agility and team ownership.

Answer: D

—

When issues recur across multiple iterations, it’s a strong indication that the root cause has not been addressed. The PMI Agile Practice Guide (Section 5.6 Retrospectives) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) recommend performing root cause analysis techniques (e.g., 5 Whys, Fishbone diagram) to ensure that the true source of recurring problems is uncovered and resolved.

Option B is correct: identifying root causes is essential to sustainable improvements.

Option A may help but doesn’t address the underlying team-level process.

Option C is useful after a solution is implemented but not the priority when the cause is unknown.

Option D is helpful for tracking, but again, ineffective if the root cause is unidentified.

According to the PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement), managing stakeholder expectations starts with establishing a shared vision and involving stakeholders in key activities like iteration reviews. This ensures transparency, feedback, and alignment on progress and priorities.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the idea that a common vision and shared goals foster trust and improve stakeholder relationships.

Option A is correct: a shared vision and active involvement lead to better stakeholder alignment.

Option B and C are partially right but limit collaboration or dismiss stakeholder input.

Option D is inconsistent with agile’s emphasis on open, continuous communication.

The correct answer is C – Ask the team to collaboratively work out a solution. Agile teams are self-organizing, and problem-solving is most effective when handled collaboratively. The Scrum Master’s role is to facilitate discussions and remove impediments—not to impose solutions.

From the PMI Agile Practice Guide:

“Problem detection and resolution is a continuous process. Agile teams regularly identify and resolve problems as part of the team’s responsibility. The Scrum Master supports the team by facilitating resolution discussions rather than solving problems directly.”

(PMI Agile Practice Guide, Section 6.5 – Problem Detection and Resolution)

Mike Griffiths states:

“When technical challenges arise, the team should collaborate to assess the issue and determine the best course of action. The Scrum Master enables this by fostering open communication and guiding the team through the problem-solving process.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A delays resolution and pushes it into the future unnecessarily.

B undermines team autonomy and ownership.

D introduces unnecessary hierarchy into team-level problem-solving.

Answer: C

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

The correct answer is D — Periodically, at both the release and project level.

Agile planning is iterative and layered. When new requirements or constraints emerge, plans should be updated at the appropriate levels—sprint, release, and potentially the overall project level. Periodic adjustments ensure continued alignment with business needs and system dependencies.

PMI Agile Practice Guide:

“Agile planning is done at multiple levels: product vision, roadmap, release, iteration, and daily. These plans are continually updated based on new learning and stakeholder feedback.”

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

Mike Griffiths:

“Effective planning includes periodic updates at all planning horizons. Adjusting at both the project and release levels ensures strategic alignment and tactical feasibility.”

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

Incorrect options:

A misses the iterative nature of Agile planning.

B and C are too narrow in scope.

Answer: D

—

The correct answer is D – Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important. Agile encourages learning and experimentation through techniques like spikes (time-boxed research or exploration activities).

From the PMI Agile Practice Guide:

“Agile encourages teams to experiment and learn continuously. Time-boxed spikes can be used to investigate alternative designs, reduce uncertainty, and support informed decisions.”

(PMI Agile Practice Guide, Section 5.3 – Spikes and Uncertainty Reduction)

Mike Griffiths supports this:

“Spikes are short, time-limited investigations into a design or technical approach. They are a vital part of agile development for reducing risk, exploring alternatives, and enabling innovation.”

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

Incorrect options:

A and C discourage innovation and agility.

B defers action rather than enabling real-time learning.

Answer: D

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

In agile, information radiators—such as visual boards placed in common areas—are used to make project data accessible, transparent, and real-time. According to the PMI Agile Practice Guide (Section 7.1 Communication), visibility improves coordination across interdependent teams.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) recommends that agile teams use visible, shared artifacts such as task boards, burn charts, or Kanban walls to improve cross-team communication and reduce friction.

Option B is correct: a physical or virtual board offers transparency and encourages informal communication.

Option A is useful but not as effective for rapid visibility.

Option C is one-way and doesn’t support real-time updates.

Option D is reactive and could cause delays or misalignment.

Agile principles emphasize just-in-time (JIT) planning and design, meaning work should not begin until it ' s pulled into the current sprint or iteration. According to the PMI Agile Practice Guide (Section 5.4 Iteration Planning) and Mike Griffiths (Chapter 6: Adaptive Planning), teams should focus on committed iteration work and avoid speculative work that is not yet planned or prioritized.

Designing item B early introduces unvalidated assumptions and risks rework if priorities or requirements change. Agile encourages deferring decisions until the last responsible moment to preserve flexibility.

Option A is correct: the team should wait until item B is formally planned before investing effort.

Option B violates agile principles by introducing premature work.

Option C and D suggest formal escalation that is unnecessary and not in the spirit of agile’s decentralized decision-making.