Free Practice Questions for PMI PMI-ACP Exam

The correct answer is B – Ensured the early engagement of key stakeholders. Agile emphasizes early and continuous stakeholder involvement. In this case, engaging enterprise architects and standards stakeholders early in the design process would have helped detect conflicts before sprint execution.

From the PMI Agile Practice Guide:

“Key stakeholders should be engaged early in the development cycle to ensure alignment with organizational policies, standards, and expectations.”

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

Mike Griffiths notes:

“Involving stakeholders early helps mitigate the risk of late surprises and rework. Enterprise architects should be consulted during backlog grooming or prior to sprint planning.”

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

Incorrect options:

A is reactive and escalatory.

C presumes the standards are flawed without analysis.

D ignores necessary compliance and does not solve the issue proactively.

Answer: B

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

When significant architectural flaws are discovered, agile teams inspect and adapt. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives and Adaptation), the product owner and team should collaboratively reassess priorities and rewrite backlog items to reflect the rework needed. This is aligned with agile’s incremental delivery and continuous adaptation.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) stresses that rework should be handled through backlog refinement and collaborative planning—not panic or reactive decisions.

Option C is correct: reassessing the backlog with stakeholders aligns with agile practices.

Option A abdicates product responsibility.

Option B is too rigid for agile, unless the risk matrix is already very mature and agile-focused.

Option D cancels value delivery and is unnecessarily drastic.

Delivering value in agile depends on frequent prioritization and real-time feedback. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Prioritization), product owners and agile teams must continuously reprioritize the backlog based on changing stakeholder needs, market shifts, and feedback. Failure to do so can result in building the wrong product—even if it ' s " done. "

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) stresses that value delivery is iterative and depends on current priorities, not static backlogs. It is vital that teams confirm that they ' re working on the highest-value items before committing to a sprint.

Option A is correct: proper backlog refinement and reprioritization ensures alignment with evolving stakeholder needs.

Option B is an anti-pattern; agile welcomes change even late in development.

Option C and D are irrelevant or do not address the core issue of prioritization.

The Scrum Master’s role as a servant leader is to support the team, not to resolve conflicts for them. It is important for the team to work through their disagreements themselves, as this fosters collaboration and improves their problem-solving skills. The Scrum Master should encourage open communication and guide the team toward healthy conflict resolution, ensuring that the disagreements are addressed constructively. This approach helps the team build trust, improves their cohesion, and strengthens their ability to handle challenges in the future.

The Scrum Master should facilitate open discussions between the product owner and the development team to help them align on the initial features and the first stages of implementation. By encouraging dialogue, the Scrum Master can ensure that both parties understand each other’s perspectives and collaborate to find a solution that meets the goals of the project. This approach fosters a collaborative environment and ensures that everyone is aligned on what needs to be delivered, promoting shared ownership of the product’s success.

Security features are typically considered non-functional requirements (NFRs), which should be captured in the product backlog and prioritized accordingly. As per the PMI Agile Practice Guide (Section 5.1: Product Backlog) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), any requested functionality—whether business- or system-level—must be clearly defined as a backlog item so the team can plan for it.

Option A is correct: security requirements should be added to the backlog and prioritized like other features.

Option B may come later if implementation is unclear, but first, the work must be defined and logged.

Option C and D represent clarification steps but don’t directly support implementation as backlog management does.

The correct answer is D – Work with the team to ensure that acceptance criteria is being properly defined and understood.

Incomplete work that fails to meet stakeholder expectations often results from unclear or misunderstood acceptance criteria. Clarifying the definition of “done” and ensuring alignment between the Product Owner and development team can drastically reduce rework and defects.

From the PMI Agile Practice Guide:

“Clear and testable acceptance criteria help ensure shared understanding. Quality issues frequently stem from misaligned expectations or vague requirements.”

(PMI Agile Practice Guide, Section 5.2 – Definition of Done and Acceptance Criteria)

Mike Griffiths writes:

“Teams must understand what success looks like for each story. Poorly defined or misunderstood acceptance criteria are a major cause of defects and missed expectations.”

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

Other options explained:

A (spike) is used for research or uncertainty—not fixing misunderstood requirements.

B (burndown chart) helps track progress, not resolve defects.

C may help indirectly but doesn ' t address the core problem of unclear requirements.

Answer: D

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

The correct answer is A — Practicing the servant leadership style of working with an agile team.

Servant leadership is foundational to Agile. The agile project leader serves the team by removing impediments, supporting their needs, and promoting transparency. Using information radiators and being involved in team progress reflects servant leadership in action.

PMI Agile Practice Guide:

“Agile leaders act as servant leaders. They support the team, remove obstacles, and foster a transparent, collaborative environment.”

(PMI Agile Practice Guide, Section 6.2 – Coaching and Servant Leadership)

Mike Griffiths:

“Servant leadership is about enabling the team to succeed. Agile leaders serve by ensuring the team has what it needs, while maintaining visibility through information radiators.”

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

Incorrect options:

B and C are valid Agile behaviors but not the most specific or complete match.

D references feedback loops but not leadership style.

Answer: A

—

The correct answer is B – Break the story up and focus on the most valuable parts. Agile promotes progressive elaboration, and large or complex stories (epics) should be broken down into smaller, testable user stories. This practice enables clarity, faster feedback, and more accurate planning.

From the PMI Agile Practice Guide:

“Large stories (epics) should be split into smaller user stories to enable understanding, estimation, and incremental delivery. Stories should be small enough to be completed within an iteration.”

(PMI Agile Practice Guide, Section 5.3 – User Stories and Story Splitting)

Mike Griffiths states:

“When a user story is too large or unclear, the team should break it down into smaller pieces, focusing on the most valuable parts first. Story splitting is a key agile practice.”

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

Incorrect options:

A discourages collaboration and learning.

C delays the resolution unnecessarily.

D avoids solving the actual problem and abandons valuable work.

Answer: B

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

In this scenario, the development team is working closely with different business units to deliver value early and often. This aligns with the agile value of delivering working software frequently, with a preference for shorter timescales. By collaborating with business units, the team is enabling early feedback and adapting to changing requirements, which is a core principle of agile methodologies like Scrum.