PMI Agile Certified Practitioner (PMI-ACP) — Free Practice Questions
10 free sample questions from a bank of 510, with the correct answers and explanations. No signup required — start practising right now.
1A newly formed development team experienced difficulty with accurately estimating product backlog items. As a result, the team failed to deliver all of the features in the sprint backlog for the past two iterations.
What should the team do to improve the accuracy of their estimates?
Decrease the sprint time box until the team is able to deliver the entire agreed-upon sprint backlog in a single sprint
Discuss estimating techniques in the daily scrum meeting
Increase the size of the development team until the team is able to deliver the entire agreed-upon sprint backlog in a single sprint
Begin tracking estimated effort metrics as an input to performance evaluation
Answer: D
The short version
D — Track estimated effort metrics to improve new-team estimates. Collecting completed versus planned work over several sprints reveals velocity for better forecasting.
Key concepts in this question
New-team variance: Early sprints lack history, so commitments often exceed proven capacity.
Velocity emergence: Stable throughput appears after four or five sprints of measured delivery.
Metric use: Counts of delivered points or items calibrate how much to pull next, without judging individuals.
Harmful shortcuts: Shrinking timeboxes, adding staff or debating in standups do not create estimation data.
Why D is correct
The settled key chooses tracking effort metrics because only observed delivery converts guesses into velocity-based plans. Keeping cadence fixed while measuring output lets the team learn sustainable load. That measure-then-forecast logic directly addresses repeated overcommitment.
Why the others are wrong
A. Shorter timebox is wrong because less time reduces capacity further and breaks stable measurement.
B. Daily scrum debate is wrong because standups coordinate daily work, not estimation technique coaching.
C. Larger team is wrong because adding people increases communication cost without improving estimate accuracy.
PMI-ACP exam tip
For new-team estimation trouble, pick track velocity over several sprints, and keep timebox stable to make data comparable.
2During a sprint, the team encounters a technical problem that becomes an impediment to completing two stories.
What should the scrum master do?
Ask the lead developer to identify a solution, and then share the details with the team
Ask a technical manager or architect to determine a solution to the problem
Work with the product owner to add a spike to the next sprint to identify a solution
Create a collaborative team environment so that the team can explore a solution together
Answer: D
The short version
D — Foster collaboration so the team solves the impediment together. Self-organizing problem solving preserves ownership and uses diverse skills during the sprint.
Key concepts in this question
Scrum master role: Removes blocks by enabling the team, not by assigning technical answers.
Collaborative environment: Encourages swarming, pairing and shared exploration of options.
Escalation traps: Routing to leads or architects sidelines the team and weakens accountability.
Spike timing: Next-sprint investigation helps for deep unknowns, but current-sprint collaboration comes first.
Why D is correct
The settled answer favors team exploration because agile relies on collective ownership of delivery. Creating space, time and psychological safety lets the team test fixes fast. That enable-don-not-direct stance matches the scrum master mandate.
Why the others are wrong
A. Lead developer solution is wrong because top-down answers bypass team collaboration and learning.
B. Manager or architect directive is wrong because external decisions undermine self-organization.
C. Next-sprint spike is wrong because deferring delays two stories when immediate joint effort may unblock them.
PMI-ACP exam tip
Choose enable-the-team for impediment stems, reserving spikes for timeboxed research only when collaboration needs structured investigation.
3During a retrospective, the agile practitioner discovers that a team member's process improvement idea has worsened the outcome.
What should the agile practitioner do?
Commend the team on trying the idea, then encourage discussion regarding alternatives
Ask a manager to direct the team on fixing the process
Encourage the team to continue executing the idea to see if it improves
Privately speak with the team member to convey that their idea worsened the outcome
Answer: A
The short version
A — Praise experimentation then discuss alternatives. Safe-to-fail trials drive learning, so the practitioner protects morale while guiding adaptation.
Key concepts in this question
Retrospective purpose: Inspect outcomes and adapt process without blame.
Psychological safety: Teams innovate only when failed ideas bring coaching rather than punishment.
Private scolding trap: Singling out the contributor chills future suggestions.
Persist-or-direct traps: Continuing a harmful idea or ordering fixes violates team ownership.
Why A is correct
Commending effort validates initiative, then open discussion turns the setback into shared insight about better options. That balance sustains improvement culture. The settled key therefore pairs encouragement with facilitated alternatives.
Why the others are wrong
B. Manager direction is wrong because imposed fixes erode self-organization and learning.
C. Continue the idea is wrong because persisting a worsening outcome ignores retrospective evidence.
D. Private rebuke is wrong because shaming suppresses future experimentation and trust.
PMI-ACP exam tip
For failed improvement ideas, pick commend plus collaborate on alternatives, never blame or escalate to management.
4Early in a project, stakeholder analysis is performed; however, an organizational restructure redefines key roles.
What should the project team do?
Note the changes to the restructure and roles that affect team activities
Use direct engagement and two-way conversation to update the stakeholder analysis for any new stakeholder requirements
Email a copy of the project vision to those redefined for key roles and ask if they need to be involved in the project
Obtain a copy of the redefined key roles to update the stakeholder analysis
Answer: B
The short version
B — Re-engage stakeholders directly to refresh analysis. Restructured roles change needs and influence, requiring two-way conversation rather than paper updates.
Key concepts in this question
Stakeholder analysis: Living view of interests, power and expectations that must follow org changes.
Direct engagement: Conversations uncover new requirements faster than emailed documents.
Agile value: Individuals and interactions over processes and tools guides the approach.
Note-or-copy traps: Filing changes or sending vision decks without dialogue misses hidden expectations.
Why B is correct
New role holders bring different goals and authority, so the team must listen and realign through dialogue. Two-way engagement updates salience and requirements collaboratively. That human-first refresh makes B the settled response.
Why the others are wrong
A. Note changes is wrong because passive recording does not elicit new stakeholder needs.
C. Email vision is wrong because one-way broadcast lacks confirmation of involvement or requirements.
D. Copy role definitions is wrong because titles alone do not reveal expectations without conversation.
PMI-ACP exam tip
When restructure appears, choose direct two-way engagement to update stakeholders, reflecting individuals-over-tools.
5A team member has spent 5 days on a spike and the first set of experiments has not been successful. The issue is the development team member has determined a short-term rather than a long-term solution.
What should the project leader do?
Assign the spike to another resource to continue research for the long-term solution
Re-estimate the spike, encourage experimentation and collaborate with the team
Stop experimentation and negotiate the short-term solution with the customer
Schedule a root-cause analysis with the development team on the main issues with the spike
Answer: B
The short version
B — Re-estimate the spike and keep collaborating experimentally. Timeboxed research should adapt with team input rather than forcing a short-term patch or reassignment.
Key concepts in this question
Spike purpose: Timeboxed learning to reduce technical uncertainty before committing.
Short-term trap: Settling for expedient fixes incurs debt and misses long-term value.
Collaboration value: Shared experiments surface options faster than solo work or handoffs.
Re-estimation: Resets expectations based on findings while preserving learning momentum.
Why B is correct
Five days without success signals scope or approach needs adjustment, not abandonment. Re-estimating with encouragement and teamwork sustains inquiry toward a durable solution. That adapt-and-continue pattern is the settled agile leadership move.
Why the others are wrong
A. Reassign resource is wrong because handoffs break continuity and imply command-style staffing.
C. Stop and negotiate short-term is wrong because it trades lasting quality for expedience.
D. Root-cause meeting alone is wrong because analysis without continued experimentation stalls learning, especially when the cause is already known.
PMI-ACP exam tip
Link struggling spikes to re-estimate plus encourage experimentation, never to reassign or settle for short-term.
6An agile team notices that the same problems continue to occur during multiple iterations. Several team members have suggestions to fix the problem.
What is the proper agile approach to handle this?
Hold frequent retrospectives and share the responsibility for making changes
Understand that this is the nature of innovative business and strive to work harder
Collect team member feedback and discuss them privately with the product owner
Conduct a team-building exercise to increase trust among the team members
Answer: A
The short version
A — Hold frequent retrospectives with shared change ownership. Recurring issues need regular inspection plus collective responsibility for fixes.
Key concepts in this question
Retrospective cadence: Frequent reflection catches systemic causes across iterations.
Shared ownership: Team commits to experiments and follows through together.
Work-harder trap: Effort without process change repeats the same defects.
Private PO route: Sidelines the team and misplaces process ownership with the product owner.
Why A is correct
Repeated problems indicate process debt that only disciplined inspect-and-adapt can remove. Frequent sessions plus joint accountability turn suggestions into tested improvements. That loop is the settled proper agile approach.
Why the others are wrong
B. Work harder is wrong because intensity without change preserves the underlying cause.
C. Private PO discussion is wrong because process improvement belongs to the team, not product ownership.
D. Team building alone is wrong because trust helps but does not replace targeted process adaptation.
Shared follow-through ensures experiments are tried, measured and adapted rather than merely suggested.
PMI-ACP exam tip
Map same-problem-multiple-iterations to frequent retrospectives plus shared ownership, not harder work or PO escalation.
7An experienced product owner presents the epics and corresponding stories during a release planning session with the established team. The executive sponsor asks the team when the features will be delivered.
What should the agile team do?
Evaluate how much can be delivered based on the Scrum Master's estimation
Identify a set of user stories based on the team's velocity
Initiate an estimation session
Consult historical data for project completion
Answer: C
The short version
C — Initiate an estimation session with the established team. Delivery dates need team-owned sizing of epics and stories before commitments.
Key concepts in this question
Release planning: Translates product vision into rough scope and timing using team judgment.
Team estimation: Those who build the work size it, creating credible forecasts.
Scrum master and velocity traps: Facilitators do not estimate and past velocity alone cannot size new epics without fresh sizing.
History limits: Prior data informs but cannot replace sizing current features.
Why C is correct
Only a collaborative estimation session produces shared understanding and a forecast the team will own. Executive pressure does not substitute for sizing. That team-estimates-then-forecasts sequence makes C the settled action.
Why the others are wrong
A. Scrum master estimation is wrong because facilitators do not own delivery estimates.
B. Velocity-only selection is wrong because pulling stories without sizing new work repeats past overcommitment.
D. History alone is wrong because old completion rates need current story points to project dates.
PMI-ACP exam tip
When asked when-features-deliver after epics appear, answer estimation session, since no forecast precedes team sizing.
8An agile team is planning the next iteration for a product release that has accumulated technical debt.
What should the team do?
Add code cleanup activities to the product backlog and request prioritization by the product owner
Add code cleanup activities to the next iteration and request clarification from the product owner
Add code cleanup activities to the next iteration and ask the product owner to end the current iteration
Add code cleanup activities to the next release backlog and request documentation from the product owner
Answer: A
The short version
A — Put cleanup in the backlog for product owner prioritization. Technical debt needs visible ordering against features rather than hidden insertion into sprints.
Key concepts in this question
Backlog transparency: All work competes openly so value and risk tradeoffs are explicit.
PO prioritization: Business owner balances debt repayment with feature delivery.
Direct insertion trap: Adding work to an active iteration bypasses planning and capacity agreements.
Documentation dodge: Logging debt elsewhere without prioritization leaves it unaddressed.
Why A is correct
Code cleanup carries cost and benefit that the product owner must weigh. Backlog placement with prioritization request respects team capacity and value focus. That visible-queue discipline is the settled correct handling.
Why the others are wrong
B. Next iteration plus clarification is wrong because it presumes inclusion without PO value ordering.
C. Next iteration plus end current is wrong because disrupting the timebox harms focus and commitments.
D. Next release plus docs is wrong because deferral with paperwork hides debt instead of prioritizing it.
PMI-ACP exam tip
Route technical debt to product backlog plus PO prioritization, never straight into active iterations.
9An agile project manager is planning the initial scope, schedule, and cost range estimates on a new project. The team will be using Kanban to control work.
What metrics should the team use to measure performance?
Lead time, throughput, and due date performance
Work in progress limits, Kanban board, and time boxes
Work item types, sprint cadences, and defect classes
Burndown charts, scatter diagrams, and throughput
Answer: A
The short version
A — Measure Kanban with lead time, throughput and due-date performance. These flow metrics reflect delivery speed and predictability without sprints.
Key concepts in this question
Lead time: Elapsed time from request to delivery for a work item.
Throughput: Count completed per period, showing capacity.
Due-date performance: Reliability against commitments, critical for service expectations.
Scrum and board traps: WIP limits, boards, burndowns and cadences are practices or Scrum tools, not Kanban outcome metrics.
Why A is correct
Kanban controls work through flow, so initial estimates need flow-based measures of speed, volume and reliability. That trio directly supports scope, schedule and cost ranges. The settled key therefore selects those three flow metrics.
Why the others are wrong
B. Limits plus board plus timeboxes is wrong because those are Kanban practices, with timeboxes belonging to Scrum.
C. Types plus cadences plus defects is wrong because categories describe work, they do not measure performance.
D. Burndown plus scatter plus throughput is wrong because burndowns track sprint scope, not core Kanban flow health.
PMI-ACP exam tip
Associate Kanban performance with lead time plus throughput plus due-date, keeping boards and WIP as practices not measures.
10During project inception, an agile practitioner engages the stakeholder to ensure alignment on the project's strategy and vision. The stakeholder asks for detailed requirements, design, and delivery plans.
What should the agile practitioner do?
Provide all information requested by the stakeholder
Set expectations regarding the appropriate level of details requested during this stage
Inform the stakeholder that no detailed documents are provided using agile practices
Ask the team to supply the information to the stakeholder
Answer: B
The short version
B — Set expectations on appropriate detail for inception. Early alignment needs vision-level clarity, not full requirements and plans that agile refines later.
Key concepts in this question
Inception purpose: Agree on strategy, success criteria and guardrails with just-enough detail.
Progressive elaboration: Details emerge through iterations as feedback accrues.
Provide-all trap: Overpromising detail creates false certainty and brittle plans.
The practitioner must honor the request while educating about agile uncertainty, agreeing on level of detail suitable now. Expectation setting preserves trust and enables adaptive planning. That balanced communication is the settled response.
Why the others are wrong
A. Provide all is wrong because detailed plans at inception ignore evolving learning and risk.
C. No documents claim is wrong because agile values working solutions but still uses lean documentation.
D. Ask team to supply is wrong because the team cannot credibly detail what inception has not yet discovered.
PMI-ACP exam tip
For detailed-plans-too-early stems, choose set expectations on appropriate detail, blending respect with agile education.