Free PMI Agile Certified Practitioner PMI-ACP Exam Questions

When a team reports that user stories are unclear or lack sufficient detail, the correct agile response is to foster collaborative refinement and shared understanding. A user story workshop is a well-recognized practice that involves the team and product owner collaborating to write, clarify, and refine stories. This is supported by the PMI Agile Practice Guide (Section 5.2: User Stories and Backlog Refinement), which recommends story-writing workshops as a proactive way to clarify requirements.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) notes that good agile teams collaboratively refine stories in grooming sessions or workshops to ensure shared clarity and alignment.

Option C is correct: a workshop enables both the team and product owner to collaborate in improving story clarity.

Option A oversimplifies the solution---acceptance criteria alone don't fully define a story.

Option B misuses the retrospective, which is for process improvement, not story editing.

Option D escalates prematurely and undermines team ownership and collaboration.

The correct answer is A --- Coordinate a collaboration session so all the team members are involved in the solution process.

Agile encourages cross-functional collaboration and collective problem-solving. When technical uncertainty arises, the best course of action is to leverage the team's combined knowledge through collaboration rather than working in isolation.

PMI Agile Practice Guide:

''Agile teams rely on collaboration, especially when solving complex problems. A diversity of input and joint ownership leads to better and faster decisions.''

(PMI Agile Practice Guide, Section 4.2 -- Communications and Collaboration)

Mike Griffiths notes:

''Agile practitioners should encourage collaborative decision-making. Technical decisions made in isolation can result in integration issues and delay. Collaboration unlocks shared ownership.''

(PMI-ACP Exam Prep, Chapter 4 -- Team Performance)

Other options:

B shifts focus away from current challenges.

C is long-term and not immediately actionable.

D may help, but it introduces external dependency instead of leveraging team knowledge.

Answe r: A

---

The correct answer is B --- Hold regular retrospectives and have team members commit to specific actions.

Regular retrospectives enable the team to continuously reflect and adapt their processes and product based on new challenges or insights. Commitment to specific action items ensures accountability and fosters a culture of learning and responsiveness.

PMI Agile Practice Guide:

''Teams should hold regular retrospectives to identify areas for improvement and define concrete actions. These actions are tracked and reviewed in subsequent iterations.''

(PMI Agile Practice Guide, Section 5.8 -- Retrospectives)

Mike Griffiths:

''Continuous improvement is a core agile value. Retrospectives allow teams to evaluate their performance and commit to actionable improvements.''

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

Incorrect options:

A is a waterfall mindset.

C lacks structured reflection and accountability.

D is a poor coding practice and anti-pattern.

Answe r: B

---

The correct answer is D --- Help establish the next sprint's goal.

The sprint goal provides a shared objective and guides the selection and execution of user stories. It is established collaboratively between the product owner and the development team at the start of sprint planning and precedes task decomposition or estimation.

PMI Agile Practice Guide:

''The team collaborates with the product owner during sprint planning to define a sprint goal. The sprint goal gives the team clarity and focus on what it intends to achieve during the sprint.''

(PMI Agile Practice Guide, Section 5.5 -- Iteration Planning)

Mike Griffiths reinforces:

''Effective planning starts with understanding the desired outcome of the sprint. The sprint goal aligns the team and informs prioritization and task breakdown.''

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

Incorrect options:

A prematurely assigns tasks, which goes against Agile's collaborative ethos.

B and C happen later in the sprint planning process after defining the sprint goal.

Answe r: D

---

When comparing total scope (story points) and velocity, you can calculate the number of sprints each team expects:

Team A: 420 / 30 = 14 sprints

Team B: 280 / 20 = 14 sprints

Even though the story points are different, both teams estimate the same number of sprints, which means they estimate similar effort and duration relative to their own internal baselines. This aligns with the concept that story points are relative and not comparable across teams.

PMI Agile Practice Guide (Section 5.4: Velocity and Relative Estimation) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explain that velocity is a team-specific measure and cannot be directly compared between teams.

Option D is correct: both teams have estimated the same project size in their own context.

Options A and B incorrectly compare velocity between teams.

Option C is irrelevant; velocity is based on team experience, not technology assumptions.

The best answer is B because agile teams should use frequent feedback, customer data, and learning to adapt priorities. The problem is that teams are continuing to invest in low-adoption features because feedback is reviewed too late. Integrating usage analytics into prioritization creates a shorter feedback loop and supports value-based decision-making.

Option A improves review frequency but still keeps decisions at an executive review level rather than embedding feedback into the team's prioritization process. Option C shifts decision-making to regional managers, but agile prioritization should still consider product value, customer outcomes, and team learning. Option D focuses on output rather than outcome; delivering more features does not necessarily reduce churn or improve value.

PMI-ACP topics emphasize maximizing value, adapting to feedback, engaging stakeholders early, and using empirical information to improve future increments.

The correct answer is A -- Reduced or improper customer collaboration.

One of the core principles of Agile is continuous collaboration with the customer. If multiple feature changes are only identified during a late-stage review, it typically indicates that the customer was not involved sufficiently throughout the development process.

From the Agile Manifesto (cited in the PMI Agile Practice Guide):

''Customer collaboration over contract negotiation.''

''Working software is delivered frequently... with a preference to the shorter timescale.''

And from the PMI Agile Practice Guide:

''Ongoing engagement with the customer helps align product features with actual needs and reduce surprises during late-stage reviews.''

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

Mike Griffiths also emphasizes:

''When customers are involved in iteration reviews and backlog grooming, their evolving needs are captured in real time. Surprises during release reviews usually reflect a failure of ongoing communication.''

(Mike Griffiths, Chapter 3 -- Value-Driven Delivery)

Other options don't directly address the root cause:

B may contribute, but customer collaboration is the key differentiator in agile.

C and D are traditional causes of waterfall-style failure, not typically root causes in agile.

Answe r: A

Value stream mapping is a powerful tool in Agile and Lean methodologies used to visualize and analyze the flow of materials and information across the entire process. By mapping the current state, the team can identify bottlenecks, delays, and inefficiencies, especially when multiple teams are involved in sequential activities. Once these gaps and constraints are identified, the team can work on improving the process, such as by finding ways to increase the number of systems migrated per day from two to three, thus improving overall efficiency.

Kanban is continuous and can lead to burnout or low morale due to lack of visible milestones. The PMI Agile Practice Guide (Section 5.7: Flow-based Agile) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 3: Team Performance) suggest that recognizing and celebrating milestones or delivery points is essential to maintain motivation, especially in long-running Kanban teams.

Option A is correct: celebrating completed work gives the team a sense of closure and achievement, improving engagement.

Option B might help temporarily but doesn't address the root motivational issue.

Option C adds pressure and is counterproductive.

Option D may improve flow but doesn't directly address the lack of visible progress recognition.

When calculating cycle time, it's important to consider delays and bottlenecks in the process. Cycle time refers to the total time taken for a single unit of work to go through the entire process from start to finish. By identifying and understanding delays or bottlenecks, the team can gain insights into where improvements can be made to optimize the flow and reduce overall cycle time. This approach helps in identifying inefficiencies and improving the team's ability to deliver value more effectively.

The product owner is responsible for maintaining and prioritizing the product backlog based on stakeholder input. According to the PMI Agile Practice Guide (Section 5.1: Product Backlog and Prioritization) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), when a sponsor is dissatisfied, the product owner should confirm that their needs are clearly prioritized and represented in the backlog.

Option B is correct: ensuring priorities are accurately captured aligns delivery with stakeholder expectations.

Option A is reactive and not productive.

Option C presumes funding is the issue without confirming alignment.

Option D undermines the product owner's role.

The correct answer is C -- The team should discuss their definition of done (DoD) and make changes to ensure there is common understanding of the acceptance criteria.

A shared understanding of what ''done'' means ensures consistent quality across team members. When this understanding is missing, defects and inconsistencies arise. The Definition of Done (DoD) should be reviewed and updated collaboratively to set a clear standard for completeness and quality.

From the PMI Agile Practice Guide:

''The Definition of Done provides a shared understanding of when work is complete. This includes quality criteria, testing, and documentation. It should be revisited regularly to maintain alignment.''

(PMI Agile Practice Guide, Section 5.2 -- Definition of Done)

Mike Griffiths emphasizes:

''Quality issues often result from unclear or inconsistent DoD. Revisiting and refining it ensures consistent expectations across the team.''

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

Why the other options are incorrect:

A (TDD) may help, but won't solve the fundamental alignment issue.

B accepts a problem without resolving it.

D imposes a process without team collaboration, which is not agile.

Answe r: C

Effective stakeholder engagement starts with shared understanding and agreement on goals and requirements. The PMI Agile Practice Guide (Section 7.2 Stakeholder Engagement) emphasizes the need to collaborate with stakeholders early and often, especially on prioritization and epic-level expectations.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) underscores that misunderstandings are reduced when all parties are aligned on what 'done' means, and epics and requirements are collaboratively defined.

Option A is correct: agreement and shared understanding reduce misalignment and conflict.

Option B introduces unnecessary delays in planning.

Option C is useful but insufficient if initial requirements are misunderstood.

Option D may help in contract terms but doesn't solve day-to-day misalignment.

When the team is uncertain about a technical solution, a spike---a timeboxed research task---is used to explore possible approaches. The PMI Agile Practice Guide (Section 5.2: Spikes) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend spikes as a formal way to explore unknowns and reduce risk in the backlog.

Option B is correct: spikes provide structure for resolving uncertainty.

Option A ignores the technical risk.

Option C disrupts team structure and ownership.

Option D defers the problem without seeking resolution.

The correct answer is A --- Capture risks and make them visible, and use a burndown chart to focus on reducing risks early in the project.

Technical uncertainty is a key area of risk in Agile projects. These risks should be clearly communicated, visualized, and prioritized early in the project to allow timely mitigation. Agile teams are empowered to make decisions and highlight blockers rather than delay work or seek hierarchical intervention.

PMI Agile Practice Guide states:

''Agile teams actively manage risk through transparency and continuous feedback. Risks should be made visible on information radiators and addressed early in the project to prevent impact on value delivery.''

(PMI Agile Practice Guide, Section 7.3 -- Risk Management)

Mike Griffiths adds:

''Teams facing uncertainty must surface risks openly and early. Using charts such as risk burndown and dashboards helps keep focus on managing these risks iteratively.''

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

Incorrect options:

B contradicts the time-boxing principle of sprints.

C raises awareness but lacks proactive risk mitigation.

D introduces a command-and-control dynamic, which is not agile.

Answe r: A

---