PMI Agile Certified Practitioner (PMI-ACP), 2024-revamped exam outline (PMI-ACP) PMI-ACP Questions 76–150 | Page 2/4

MCQmedium

A product owner needs to show the long-term product roadmap to the board. What is the most appropriate format?

A.A detailed Gantt chart with fixed dates for every task.

B.A list of all team members and their assignments.

C.A high-level view showing themes and time horizons.

D.A printout of the entire product backlog.

AnswerC

A roadmap communicates direction, not delivery dates, so themes mapped against time horizons give the board a strategic view without implying fixed commitments. Detailed feature lists or sprint backlogs belong to release and iteration planning, which would misrepresent long-term uncertainty to executives.

Why this answer

An Agile product roadmap is a high-level, outcome-oriented view that communicates themes, epics, and time horizons (e.g., now/next/later or quarterly) rather than fixed dates and tasks. For a board audience, this format conveys strategic direction and adaptability while avoiding false precision. It aligns with Agile's empirical approach and allows for re-planning as market conditions change.

Exam trap

PMI-ACP often tests the distinction between Agile roadmaps (high-level, adaptive) and traditional Gantt charts (detailed, fixed)—candidates who default to 'detailed plan' answers fail because Agile values responding to change over following a plan.

How to eliminate wrong answers

Option A is wrong because a detailed Gantt chart with fixed dates for every task is a predictive/waterfall artifact that contradicts Agile planning and creates brittle commitments. Option B is wrong because listing team members and assignments is a resource plan, not a product roadmap, and provides no strategic product direction. Option D is wrong because printing the entire product backlog is tactical and overwhelming; the backlog is a living artifact for the team, not a board-level communication tool.

Full explanation →

MCQmedium

A team has a very low 'say/do' ratio. What does this suggest?

A.The team needs to work longer hours.

B.The team needs to look at their commitment and estimation practices.

C.The team is incompetent.

D.The team is under-performing.

AnswerB

A low say/do ratio signals the team consistently commits to more work than it completes, so the gap lies in how commitments are made and stories estimated. Reviewing estimation practices and commitment discipline directly addresses that shortfall, unlike remedies targeting velocity metrics, capacity planning or stakeholder communication.

Why this answer

A low say/do ratio means the team is committing to more work than they actually complete, indicating a gap between promises and delivery. The correct response is to examine commitment and estimation practices, because the ratio is a reflection of how well the team forecasts and commits, not of their competence or effort. Improving estimation accuracy and realistic commitment will raise the ratio.

Exam trap

PMI-ACP often tests the misconception that a low say/do ratio indicates poor performance or laziness, when it actually points to over-commitment and estimation inaccuracy that should be addressed through better forecasting practices.

How to eliminate wrong answers

Option A is wrong because working longer hours does not fix a say/do ratio problem — it may worsen it by leading to burnout and lower quality, and it addresses effort rather than estimation accuracy. Option C is wrong because a low say/do ratio is a process and forecasting issue, not evidence of incompetence; labeling the team incompetent is both inaccurate and demoralizing. Option D is wrong because the team may be performing well but over-committing; the ratio measures commitment reliability, not overall performance or output.

Full explanation →

MCQeasy

In the context of the product roadmap, what is the primary purpose of a release plan?

A.To replace the need for sprint planning.

B.To dictate the exact daily tasks for each developer.

C.To provide a high-level view of when features will be available.

D.To guarantee that all features will be completed on time.

AnswerC

A release plan translates roadmap items into scheduled increments, showing which features will be delivered in each upcoming release and roughly when. This satisfies the roadmap's need for a high-level timeline view, without committing to sprint-level detail that iteration planning handles.

Why this answer

A release plan provides a high-level view of when features or feature sets will be available to users, bridging the product roadmap and sprint execution. It communicates intended release dates and scope at a coarse granularity without committing to exact daily tasks. This helps stakeholders align on delivery expectations while preserving agile flexibility.

Exam trap

PMI-ACP often tests the misconception that a release plan is a fixed commitment or a replacement for sprint planning, when it is actually a high-level, adaptable forecast.

How to eliminate wrong answers

Option A is wrong because a release plan does not replace sprint planning; sprint planning operates at a finer granularity and is still required to determine how work will be done in each iteration. Option B is wrong because dictating exact daily tasks is micromanagement and is not the purpose of any agile planning artifact. Option D is wrong because a release plan is a forecast, not a guarantee—agile embraces uncertainty and welcomes changing requirements, so guaranteeing all features on time contradicts agile principles.

Full explanation →

Multi-Selecthard

Which THREE factors should influence the priority of a product backlog item?

Select 3 answers

A.The personal preference of the developers.

B.The font size of the story description.

C.Business value to the customer.

D.Cost of development.

E.Technical risk or uncertainty.

AnswersC, D, E

Business value to the customer is the primary prioritisation driver, since backlog ordering should maximise delivered value. Items yielding greater customer benefit or revenue are sequenced earlier, ensuring the team builds what stakeholders actually need first.

Why this answer

Option C (business value to the customer) is correct because backlog prioritization should maximize delivered value, so items that provide greater customer or business benefit are ranked higher. Option D (cost of development) is correct because the effort and resources required affect return on investment; a high-value item that is cheap to build may outrank an equally valuable but expensive one. Option E (technical risk or uncertainty) is correct because high-risk or uncertain items are often prioritized early to reduce unknowns, validate assumptions, and avoid costly late rework.

Option A is not a valid factor because prioritization must be based on value and risk rather than developers' personal preferences, and Option B is irrelevant since the visual formatting of a story description has no bearing on its business importance.

Exam trap

PMI-ACP often tests whether candidates can distinguish genuine prioritization factors from irrelevant or subjective criteria, and the trap is selecting developer preference or cosmetic details as valid inputs.

Full explanation →

MCQhard

A stakeholder asks to change a completed feature. What is the correct response?

A.Evaluate the change's value and discuss the impact with the PO.

B.Tell them it's too late.

C.Charge the stakeholder for the rework.

D.Do the change immediately without question.

AnswerA

Completed work still passes through the product owner, who owns backlog ordering. Evaluating the change's value and impact lets the PO weigh it against other priorities and decide whether to reopen the feature, rather than the team unilaterally reworking delivered functionality.

Why this answer

In Agile, changes are welcome even late in development, but they must be evaluated for value and impact. The correct response is to assess the change's business value and discuss it with the Product Owner, who owns backlog prioritization. This ensures the change is weighed against other work and aligned with product strategy.

Exam trap

PMI-ACP often tests the balance between embracing change and maintaining sprint discipline; candidates may incorrectly think all changes must be accepted immediately or rejected outright, but the correct approach is to evaluate value and impact with the Product Owner.

How to eliminate wrong answers

Option B is wrong because Agile embraces change; saying 'it's too late' contradicts the principle of responding to change over following a plan. Option C is wrong because charging for rework is not an Agile practice; it creates adversarial relationships and ignores the collaborative nature of Agile contracts. Option D is wrong because implementing a change immediately without evaluation bypasses the Product Owner's authority and can disrupt sprint commitments and value delivery.

Full explanation →

MCQmedium

A team is experiencing frequent bottlenecks at the 'Quality Assurance' stage of their Kanban board. Which metric would provide the most insight into the nature of this bottleneck?

A.Sprint burndown chart.

B.Throughput run chart.

C.Lead time distribution chart.

D.Cumulative Flow Diagram.

E.Cycle time scatterplot.

AnswerD

A Cumulative Flow Diagram plots work-in-progress per column over time, so widening bands at the QA column reveal where items accumulate and how long they wait. This exposes the bottleneck's nature and trend, which a single-cycle-time or throughput number cannot show.

Why this answer

A Cumulative Flow Diagram (CFD) plots the number of items in each workflow state over time, so a widening band at the 'Quality Assurance' stage visually reveals where work is accumulating — the bottleneck. It shows both the quantity of work-in-progress in QA and how long items are sitting there, giving the most direct insight into the nature and magnitude of the bottleneck.

Exam trap

The trap is choosing a chart that measures time (lead time, cycle time) when the question asks about identifying WHERE work is accumulating — only the CFD shows WIP by workflow state, which is what reveals a stage-specific bottleneck.

How to eliminate wrong answers

Option A is wrong because a sprint burndown chart tracks remaining work in a sprint (typically story points or tasks) and is a Scrum artifact — it does not show where in the workflow items are piling up. Option B is wrong because a throughput run chart shows how many items are completed over time, but it does not reveal which stage is the bottleneck. Option C is wrong because a lead time distribution chart shows the distribution of total time from start to finish; while useful, it does not isolate the QA stage specifically.

Option E is wrong because a cycle time scatterplot shows variability in cycle time per item, but again does not show the accumulation of WIP at a specific stage the way a CFD does.

Full explanation →

MCQeasy

A team is consistently missing their sprint goals. What is the most effective way to empower the team to improve?

A.Assign a mentor to watch every task developers perform.

B.Facilitate a root-cause analysis in the retrospective to identify process blockers.

C.Analyze the velocity data and set higher targets for the next sprint.

D.Replace the team members who are underperforming.

AnswerB

A retrospective root-cause analysis lets the team itself identify why sprint goals are missed, addressing process blockers rather than blaming individuals. This empowers self-organisation, the agile principle behind continuous improvement, instead of imposing external fixes.

Why this answer

The retrospective is the team's dedicated inspect-and-adapt ceremony, and root-cause analysis (such as the Five Whys or fishbone diagram) within it surfaces the systemic process blockers causing missed sprint goals. This empowers the team to own the improvement rather than having a fix imposed from outside. Velocity data and personnel changes do not address underlying process defects.

Exam trap

PMI-ACP often tests the misconception that missed sprint goals are a performance problem to be fixed with higher targets or personnel changes, when the agile answer is almost always to inspect and adapt the process through the retrospective.

How to eliminate wrong answers

Option A is wrong because assigning a mentor to watch every task is micromanagement that erodes trust and autonomy, and it treats symptoms rather than the systemic causes of missed goals. Option C is wrong because analyzing velocity and setting higher targets is a command-and-control response that ignores why the team is missing goals and can push them into unsustainable over-commitment. Option D is wrong because replacing underperforming members assumes the problem is people rather than process; it destroys team cohesion and ignores the possibility that blockers, unclear requirements, or dependencies are the real cause.

Full explanation →

MCQmedium

You are the agile leader for a team that recently transitioned from a predictive environment. During the third sprint, you notice that team members consistently wait for your approval before making decisions about task assignments and process adjustments. How should you best respond to foster self-organization?

A.Reassign tasks daily based on your assessment of each member's strengths and current workload.

B.Continue approving decisions for now, but gradually increase the scope of decisions you delegate over several sprints.

C.Explain the concept of self-organization and then step back, allowing the team to make decisions and learn from the outcomes.

D.Escalate the team's dependency to the project sponsor and request additional coaching resources.

AnswerC

This response directly addresses the root cause: the team's habit of waiting for approval. By explaining self-organization and then deliberately stepping back, you shift decision rights to the team. They will likely make imperfect choices initially, but those become learning opportunities that build capability and confidence. This is the essence of servant leadership in agile, where the leader removes themselves as a bottleneck.

Why this answer

The team is exhibiting dependency on the leader's approval, a common pattern when moving from predictive to agile ways of working. The most effective action is to clarify what self-organization means and then intentionally step back, allowing the team to make decisions and own the results. This builds capability, trust, and ownership.

Continuing to approve or gradually delegating keeps the leader as a bottleneck and delays the team's development.

Exam trap

The trap here is assuming that a gradual, controlled release of decision-making authority is safer or more effective than fully stepping back, when in fact incremental delegation can prolong dependency and slow the team's growth.

Full explanation →

MCQmedium

A project is experiencing significant scope creep. How should the practitioner handle this to protect the team's delivery capacity?

A.Add more hours to the work week for the team.

B.Delete the backlog to force a restart.

C.Accept all new requests to please stakeholders.

D.Ask the Product Owner to evaluate and prioritize requests against the current sprint goal.

AnswerD

The Product Owner owns backlog ordering, so routing new requests there lets them be assessed against the sprint goal rather than injected directly. This shields the team's committed capacity while keeping scope decisions with the accountable role.

Why this answer

In agile/Scrum, the Product Owner is the single point of accountability for backlog prioritization and scope decisions. When scope creep threatens the sprint, the correct response is to route new requests through the Product Owner so they can be evaluated against the sprint goal and either deferred, split, or swapped for existing work. This protects the team's sustainable pace and preserves the sprint commitment without the team unilaterally absorbing extra work.

Exam trap

PMI-ACP often tests the misconception that the project manager or team lead should personally triage scope changes, when in agile the Product Owner is the sole authority for backlog prioritization.

How to eliminate wrong answers

Option A is wrong because extending work hours violates the agile principle of sustainable development pace and treats a prioritization problem as a capacity problem, which masks scope creep rather than resolving it. Option B is wrong because deleting the backlog destroys the product's value stream and historical prioritization data — it is a destructive overreaction, not a scope-control technique. Option C is wrong because accepting all new requests unconditionally is the definition of enabling scope creep; it removes the Product Owner's gatekeeping role and guarantees missed sprint goals.

Full explanation →

MCQhard

During a retrospective, the team is silent. How do you encourage participation?

A.Use a facilitation technique like 'silent brainstorming' or 'anonymous cards'.

B.Call on people one by one.

C.Threaten to report the team's silence to the manager.

D.End the meeting early.

AnswerA

Silent brainstorming or anonymous cards let quieter members contribute without speaking up in the group, removing social pressure. Written input is then shared and discussed, surfacing concerns that silence would otherwise hide during the retrospective.

Why this answer

When a team is silent during a retrospective, the Scrum Master or facilitator should use techniques that create psychological safety and encourage input without pressure. Silent brainstorming or anonymous cards allow individuals to contribute ideas without fear of judgment or speaking over others, which often breaks the silence and surfaces diverse perspectives.

Exam trap

PMI-ACP often tests facilitation techniques and the trap is selecting authoritarian or avoidance-based options that seem efficient but violate Agile principles of safety and collaboration.

How to eliminate wrong answers

Option B is wrong because calling on people one by one can increase anxiety and pressure, leading to superficial or defensive responses rather than honest reflection. Option C is wrong because threatening to report silence to a manager is coercive and destroys trust, which is counterproductive to the retrospective's purpose. Option D is wrong because ending the meeting early avoids the problem and fails to facilitate the team's improvement, which is the facilitator's responsibility.

Full explanation →

Multi-Selecteasy

Which THREE traits of a leader are essential for coaching an agile team? (Choose THREE)

Select 3 answers

A.Patience, recognizing that growth takes time.

B.Acting as a role model for agile values and behaviors.

C.Always being the one with the answers to every problem.

D.Active listening to understand the team's perspective.

E.Focusing only on the team's output, not their personal growth.

AnswersA, B, D

Patience directly satisfies the coaching constraint: agile teams acquire self-organisation through iterative reflection, not instruction. A leader who tolerates slow, uneven progress preserves the psychological safety needed for experimentation, letting the team own its improvement rather than reverting to command-and-control direction.

Why this answer

Option A (Patience, recognizing that growth takes time) is correct because coaching an agile team involves developing people iteratively, much like agile delivery itself, so a leader must allow team members to learn through experimentation and even failure rather than demanding instant mastery. Option B (Acting as a role model for agile values and behaviors) is correct because agile coaching depends on modeling the very principles being taught—such as collaboration, transparency, and self-organization—since teams learn more from observed behavior than from instruction alone. Option D (Active listening to understand the team's perspective) is correct because effective coaching requires genuinely hearing the team's concerns, ideas, and impediments so the leader can ask powerful questions and guide the team toward its own solutions instead of imposing answers.

Option C is incorrect because a leader who must always supply every answer undermines the team's self-organization and ownership, which are core agile principles. Option E is incorrect because focusing only on output while ignoring personal growth neglects the people-development aspect that defines coaching and sustains long-term team performance.

Exam trap

The trap is selecting traits that seem leader-like (having all answers, focusing only on output) but actually contradict agile coaching principles of empowerment and holistic development.

Full explanation →

MCQmedium

A team wants to change their way of working. How do you support this?

A.Tell them what to change.

B.Say no, because the current process works.

C.Wait for management approval.

D.Support their experiment and help them measure the outcome.

AnswerD

Treating the change as a safe-to-fail experiment lets the team trial the new way of working while generating data on its effect. Measuring the outcome provides evidence to decide whether to adopt, adapt, or abandon the practise, which is the essence of continuous improvement.

Why this answer

In Agile, the team owns its process and is empowered to inspect and adapt its way of working. The correct response is to support their experiment and help them measure the outcome, because continuous improvement is driven by empirical feedback rather than top-down mandates. This aligns with the PMI-ACP principle of self-organizing, empowered teams that use retrospectives to evolve their practices.

Exam trap

PMI-ACP often tests the misconception that a coach or manager should direct process changes, when in fact the correct Agile answer is almost always to empower the team to experiment and measure results themselves.

How to eliminate wrong answers

Option A is wrong because telling the team what to change is a command-and-control approach that undermines self-organization and team ownership. Option B is wrong because refusing change because 'the current process works' ignores the Agile principle of continuous improvement and the possibility of better outcomes. Option C is wrong because waiting for management approval introduces unnecessary delay and contradicts the empowered, self-organizing team model central to Agile.

Full explanation →

MCQhard

An agile team is consistently failing to deliver the 'must-have' features by the release deadline. What should the Product Owner do?

A.Remove the Scrum Master for not pushing the team harder.

B.Mandate mandatory weekend work for the team.

C.Collaborate with stakeholders to re-negotiate scope or the release date.

D.Lower the quality standards to get it done faster.

AnswerC

The team cannot meet must-have commitments within the fixed release window, so the Product Owner must engage stakeholders to adjust either scope or the release date. This restores a deliverable commitment aligned with actual team velocity, rather than pressuring the team or silently dropping features.

Why this answer

When an agile team cannot deliver must-have features by the release deadline, the Product Owner's responsibility is to manage scope and stakeholder expectations, not to squeeze the team. Collaborating with stakeholders to re-negotiate scope or the release date respects the Agile principle of delivering value within sustainable pace and acknowledges that fixed scope, fixed date, and fixed quality cannot all be guaranteed simultaneously. This is the only option that addresses the root cause through transparent negotiation rather than coercion or quality compromise.

Exam trap

PMI-ACP often tests whether candidates default to command-and-control or quality-cutting responses under deadline pressure — the trap is choosing an option that 'gets it done' (overtime, lower quality) instead of the Agile-aligned negotiation and sustainable-pace response.

How to eliminate wrong answers

Option A is wrong because removing the Scrum Master misdiagnoses the problem — the Scrum Master facilitates the process and removes impediments, but the team's delivery shortfall is a scope/capacity issue, not a servant-leadership failure. Option B is wrong because mandating weekend work violates the Agile principle of sustainable development, degrades morale, increases defect rates, and is unsustainable — it treats a planning problem as an effort problem. Option D is wrong because lowering quality standards to hit a date directly contradicts the Agile emphasis on technical excellence and working software, and it accumulates technical debt that slows future delivery.

Full explanation →

MCQmedium

A team is struggling with frequent context switching during their sprint. Which lean technique should the practitioner implement to optimize end-to-end flow?

A.Add more team members to distribute the workload.

B.Conduct a daily stand-up meeting for longer durations.

C.Increase the sprint duration to allow more time for tasks.

D.Implement strict Work In Progress (WIP) limits on the Kanban board.

AnswerD

WIP limits cap concurrent work, forcing the team to finish items before pulling new ones. This directly reduces the context switching described in the stem and shortens cycle time, optimising end-to-end flow across the value stream.

Why this answer

Implementing strict WIP limits on the Kanban board directly addresses context switching by constraining the number of items a team can work on simultaneously. When WIP limits are enforced, team members are forced to finish current work before pulling new tasks, which reduces multitasking and improves flow efficiency. This lean technique is grounded in Little's Law (Cycle Time = WIP / Throughput), meaning reducing WIP directly shortens cycle time and accelerates end-to-end delivery.

Thus, WIP limits are the most effective lean tool for optimizing flow and eliminating the waste of context switching.

Exam trap

PMI-ACP often tests the misconception that adding resources or extending timeboxes solves flow problems, when the lean principle is to limit WIP to reduce context switching and optimize flow.

How to eliminate wrong answers

Option A is wrong because adding team members increases communication overhead and onboarding time, often exacerbating context switching rather than reducing it, and it does not address the root cause of too much work in progress. Option B is wrong because longer daily stand-ups consume productive time and do not limit WIP or reduce context switching; in fact, they can become a source of distraction. Option C is wrong because increasing sprint duration merely extends the timebox without addressing the underlying flow problem—context switching persists and may even worsen as work expands to fill the longer sprint.

Full explanation →

MCQeasy

Which of the following is a key component of psychological safety?

A.Having clear instructions.

B.Being able to take risks without fear of punishment.

C.Working in a quiet environment.

D.Having high pay.

AnswerB

Taking interpersonal risks without fear of punishment or humiliation defines psychological safety, satisfying the stem's requirement for a key component. Amy Edmondson's research frames it as a shared team belief that enables candour, admitting mistakes and challenging the status quo — distinct from trust or personality, and essential for agile retrospectives and continuous improvement.

Why this answer

Psychological safety, as defined by Amy Edmondson, is the shared belief that team members can take interpersonal risks—speaking up, admitting mistakes, asking questions, proposing ideas—without fear of punishment or humiliation. Being able to take risks without fear of punishment is the core component that enables learning, innovation, and honest communication in Agile teams.

Exam trap

PMI-ACP often tests whether candidates confuse psychological safety with general job satisfaction or team comfort—the trap is picking a plausible-sounding but unrelated factor like clear instructions or high pay.

How to eliminate wrong answers

Option A is wrong because clear instructions relate to task clarity and process definition, not the interpersonal risk-taking that defines psychological safety. Option C is wrong because a quiet environment is a physical workplace condition, unrelated to the team's emotional climate. Option D is wrong because high pay is a compensation factor (hygiene factor in Herzberg's theory) and does not create the trust and safety needed for candor.

Full explanation →

Multi-Selectmedium

Which TWO of the following indicate an 'agile' approach to documentation?

Select 2 answers

A.Writing documentation once and never reviewing it

B.Creating comprehensive documentation before starting any work

C.Mandating that all documents be signed by management

D.Writing only the documentation that is necessary

E.Ensuring documentation is kept up-to-date as the product evolves

AnswersD, E

Agile documentation is judged by value, not volume: producing only artefacts the team or stakeholders genuinely need satisfies the stem's 'agile' indicator, since unnecessary documents are waste. This contrasts with predictive approaches that mandate comprehensive upfront specifications regardless of whether they are read.

Why this answer

Option D is correct because agile documentation is intentionally 'just enough' — teams produce only the artifacts that deliver value, avoiding the waste of heavy, unused documents. Option E is correct because agile treats documentation as a living artifact that evolves with the product, so it is continuously reviewed and updated alongside changing requirements. Option A is wrong because never reviewing documentation contradicts agile's emphasis on continuous improvement and would let docs go stale.

Option B is wrong because writing comprehensive documentation upfront is a plan-driven, waterfall-style practice that agile replaces with iterative, incremental documentation. Option C is wrong because mandatory management sign-off adds heavyweight approval gates and bureaucracy, which is contrary to agile's lightweight, collaborative approach.

Exam trap

PMI-ACP often tests the false dichotomy that agile means no documentation, when the correct interpretation is 'just enough' documentation that is kept current.

Full explanation →

Multi-Selectmedium

Which TWO actions support a team in becoming more self-organizing? (Choose TWO)

Select 2 answers

A.Ignoring the team's issues to let them learn on their own.

B.Requiring all technical decisions to go through you.

C.Directing every step of the team's day-to-day work.

D.Allowing the team to choose how they complete their work.

E.Giving the team ownership over their own process improvements.

AnswersD, E

Letting the team decide how work is completed gives members autonomy over technical execution, which builds the shared accountability self-organisation depends on. This satisfies the stem's requirement by shifting method selection from manager to team.

Why this answer

Option D is correct because self-organizing teams are granted autonomy over how they accomplish their work, meaning the team—not an external manager—decides the technical approach, task breakdown, and execution methods within agreed boundaries. Option E is correct because true self-organization includes owning process improvements; when the team inspects and adapts its own way of working (for example, in a retrospective), it builds the accountability and shared ownership that self-organization requires. Options A, B, and C do not belong: ignoring the team's issues (A) is abdication rather than empowerment and removes the coaching/servant-leadership support a growing team needs, while requiring all technical decisions to go through you (B) and directing every step of day-to-day work (C) are command-and-control behaviors that strip the team of autonomy and decision-making authority, directly preventing self-organization.

Exam trap

PMI-ACP often tests the difference between empowerment and abdication — candidates pick 'ignoring issues' thinking it builds autonomy, but true self-organization requires active coaching, clear boundaries, and decision authority, not neglect.

Full explanation →

MCQmedium

Your team is failing to complete tasks due to frequent context switching. What is your role in resolving this?

A.Tell the team to just say 'no' to any incoming requests.

B.Instruct the team to work longer hours to finish.

C.Create a formal document requiring all requests to be approved by you.

D.Identify the sources of interruptions and coach the organization to protect the team's focus.

AnswerD

Context switching stems from external interruptions, so the agile practitioner's role is to surface those sources and coach the wider organisation to shield the team's focus, rather than simply telling the team to work faster.

Why this answer

The agile leader's role is to identify the root causes of context switching and then coach the broader organization to respect the team's focus, rather than imposing controls on the team. This addresses the systemic issue (external interruptions) while empowering the team. It aligns with servant leadership and continuous improvement.

Exam trap

PMI-ACP often tests the misconception that the agile leader should directly control the team (e.g., by imposing rules or telling them to say no) rather than coaching the organization and removing systemic impediments.

How to eliminate wrong answers

Option A is wrong because telling the team to 'just say no' is a simplistic, unsupported directive that ignores the organizational dynamics causing the interruptions and can damage stakeholder relationships. Option B is wrong because working longer hours treats the symptom (unfinished tasks) rather than the cause (context switching) and leads to burnout and reduced quality. Option C is wrong because creating a formal approval document adds bureaucracy and positions the leader as a gatekeeper, which contradicts agile principles of self-organization and trust.

Full explanation →

MCQhard

An agile team is using 'Story Points' for estimation. Why is this preferred over 'Hours' for backlog items?

A.It is required by the project management office.

B.It makes it easier to track individual performance.

C.It accounts for complexity, effort, and uncertainty without needing precise time forecasting.

D.It ensures that every story takes exactly the same amount of time.

AnswerC

Story points rate relative size using a non-linear scale that folds in complexity, effort and uncertainty, so estimates need no precise time forecasting. Hours imply false precision and decay as team velocity changes, which is why points suit backlog estimation better.

Why this answer

Story points are a relative, unitless measure that captures complexity, effort, and uncertainty together, which is why they are preferred over hours for backlog estimation. Because humans are better at comparing items than forecasting absolute durations, relative sizing produces more reliable estimates and avoids false precision. Story points also decouple estimation from individual time tracking, supporting team-based planning.

Exam trap

The trap is treating story points as a disguised time unit, so candidates pick options about individual performance tracking or uniform duration instead of the relative, uncertainty-aware nature of points.

How to eliminate wrong answers

Option A is wrong because story points are not a PMO mandate; they are an Agile practice chosen for their estimation benefits, and imposing them as a compliance requirement misses the point. Option B is wrong because story points are deliberately not tied to individual performance; using them to track individuals corrupts the estimates and undermines team collaboration. Option D is wrong because story points do not make every story take the same time — they express relative size, and actual duration still varies with team capacity and context.

Full explanation →

MCQhard

An enterprise organization is struggling to coordinate agile delivery across global time zones. What is the most effective approach?

A.Stop all collaboration.

B.Only work with teams in the same time zone.

C.Schedule core overlapping hours for synchronization and use asynchronous communication tools.

D.Force all teams to work the same hours.

AnswerC

Global time zones prevent full synchronous overlap, so scheduling a shared core window for critical synchronisation, combined with asynchronous tools for everything else, minimises coordination delay. This directly addresses the constraint of distributed time zones while preserving alignment across the enterprise.

Why this answer

In globally distributed agile teams, the most effective coordination strategy is to establish a shared window of overlapping working hours for synchronous ceremonies (daily standups, sprint planning, retrospectives) while relying on asynchronous tools (wikis, boards, recorded demos, chat threads) for the rest of the work. This preserves real-time collaboration where it adds the most value without forcing unsustainable schedules on any single region. It aligns with PMI-ACP principles of adaptive communication planning and team empowerment.

Exam trap

PMI-ACP often tests the misconception that co-location or identical working hours are prerequisites for agile success, luring candidates toward rigid options instead of adaptive, overlap-plus-async communication strategies.

How to eliminate wrong answers

Option A is wrong because halting collaboration destroys the transparency, inspection, and adaptation that agile delivery depends on and guarantees integration failures. Option B is wrong because restricting work to a single time zone defeats the purpose of a global enterprise, sacrifices talent and follow-the-sun capacity, and is not a viable scaling strategy. Option D is wrong because forcing all teams onto identical hours ignores legal, cultural, and personal constraints, increases attrition, and is a command-and-control approach incompatible with self-organizing agile teams.

Full explanation →

MCQhard

How can a practitioner best support a team that is feeling overwhelmed by 'agile ceremonies'?

A.Mandate attendance without explanation.

B.Increase the frequency of meetings.

C.Facilitate discussions to streamline and ensure the value of each ceremony is clear.

D.Cancel all ceremonies.

AnswerC

Facilitating a discussion lets the team examine each ceremony and remove or shorten those adding no value, directly addressing the overwhelm. This preserves agile principles while ensuring every ceremony's purpose is understood, satisfying the need to support the team without abandoning the framework.

Why this answer

The correct answer is C because the practitioner's role in agile is to serve the team, not to impose process. When a team feels overwhelmed by ceremonies, the root cause is usually that the ceremonies have lost their purpose or are poorly facilitated. Facilitating a discussion to streamline the ceremonies and clarify their value directly addresses the team's pain point while preserving the agile framework's intent.

This approach respects the team's autonomy and self-organization, which are core agile principles.

Exam trap

PMI-ACP often tests the distinction between servant leadership and traditional management; candidates may incorrectly choose to mandate or cancel ceremonies, missing that the agile practitioner should facilitate team-driven process improvement.

How to eliminate wrong answers

Option A is wrong because mandating attendance without explanation is a command-and-control approach that violates agile's emphasis on self-organizing teams and intrinsic motivation. Option B is wrong because increasing meeting frequency would exacerbate the overwhelm rather than alleviate it, and more meetings do not inherently add value. Option D is wrong because canceling all ceremonies removes the structural mechanisms (e.g., daily sync, retrospectives, planning) that enable transparency, inspection, and adaptation, which are essential to agile.

Full explanation →

MCQhard

The team's velocity is highly inconsistent, causing frustration for the Product Owner. How should you address this as a coach?

A.Mandate that the team increase their velocity by 20% next sprint.

B.Change the story point estimation technique to something faster.

C.Ask the team to stop using story points.

D.Facilitate a discussion on what factors are influencing the variance and how to manage them.

AnswerD

Coaching addresses inconsistent velocity by helping the team inspect the underlying causes — changing scope, blockers, estimation drift — rather than imposing a number. Facilitating that discussion satisfies the stem's constraint of improving the system collaboratively, which the Product Owner cannot fix unilaterally.

Why this answer

Velocity is a diagnostic metric, not a target. Inconsistent velocity usually signals underlying issues such as unclear requirements, changing priorities, technical debt, or team capacity fluctuations. As a coach, the correct approach is to help the team inspect and adapt by facilitating a discussion about the root causes of variance.

This aligns with the Agile principle of self-organizing teams and continuous improvement, rather than imposing external mandates or changing estimation techniques without understanding the problem.

Exam trap

PMI-ACP often tests the misconception that velocity should be maximized or that inconsistent velocity requires a technical fix, when the correct answer is always to facilitate team-driven root cause analysis and improvement.

How to eliminate wrong answers

Option A is wrong because mandating a velocity increase is a command-and-control approach that ignores the team's self-organization and can lead to gaming metrics or burnout. Option B is wrong because changing the estimation technique does not address the root causes of variance and may introduce further inconsistency. Option C is wrong because abandoning story points without understanding why velocity varies removes a useful planning tool and does not solve the underlying issues.

Full explanation →

Multi-Selecteasy

Which THREE items are typically discussed during a sprint retrospective?

Select 3 answers

A.Individual salary negotiations.

B.Product design details.

C.Action items for the next sprint.

D.What could be improved.

E.What went well.

AnswersC, D, E

Action items for the next sprint belong in the retrospective because the ceremony closes by converting identified improvements into owned, tracked commitments. This satisfies the stem's requirement for a typically discussed retrospective item, distinguishing it from sprint planning or daily standup content, where forward work is instead selected or coordinated.

Why this answer

The sprint retrospective is a Scrum ceremony focused on inspecting the team's process and identifying improvements, so option C (Action items for the next sprint) is correct because the retrospective concludes by producing concrete, owned improvement actions to carry into the next sprint. Option D (What could be improved) is correct because examining problems, impediments, and process weaknesses is a core purpose of the retrospective. Option E (What went well) is correct because recognizing successful practices and strengths helps the team reinforce what works.

Option A (Individual salary negotiations) is not part of any Scrum event and belongs to HR/management, and option B (Product design details) is a product/refinement concern handled in backlog refinement or design discussions, not the retrospective's process-improvement focus.

Exam trap

PMI-ACP often tests whether candidates confuse the retrospective (process improvement) with sprint review (product demo/inspection) or backlog refinement (product detail), so any option mentioning product design or compensation is a distractor.

Full explanation →

MCQmedium

A product vision has become outdated due to market shifts. How should the Product Owner proceed?

A.Allow developers to decide the new vision.

B.Collaborate with stakeholders to revise the product vision.

C.Wait until the end of the project to change the vision.

D.Ignore the shift and continue with the original plan.

AnswerB

Revising the vision with stakeholders directly addresses the market shift by revalidating value against current customer needs. This collaborative approach satisfies the Product Owner's accountability for maximising value, ensuring the updated vision reflects stakeholder input rather than one person's assumptions, and realigns the backlog and roadmap with the changed market.

Why this answer

The product vision is owned by the Product Owner but shaped with stakeholders, so when market shifts invalidate it, the Product Owner should collaborate with stakeholders to revise it. This keeps the vision aligned with business value and customer needs while preserving stakeholder buy-in. The Product Owner remains accountable for the vision, but revising it is a collaborative, not unilateral, act.

Exam trap

The trap is confusing ownership with unilateral authority, so candidates pick 'let developers decide' or 'wait until the end' instead of the collaborative stakeholder revision the Product Owner role actually requires.

How to eliminate wrong answers

Option A is wrong because developers do not own the product vision; delegating it to them abdicates the Product Owner's accountability and bypasses stakeholder alignment. Option C is wrong because waiting until the end of the project to change the vision guarantees the team builds something the market no longer wants, wasting the entire investment. Option D is wrong because ignoring the market shift and continuing the original plan is the classic failure to embrace change, producing a product with no market fit.

Full explanation →

100

MCQmedium

How can a leader best promote self-organization within an agile team?

A.Attend every technical meeting to provide guidance.

B.Require all decisions to be approved by the leadership team.

C.Create detailed task lists for every team member.

D.Define the objective and let the team decide how to achieve it.

AnswerD

Self-organisation grows when the leader sets the goal and boundaries but leaves method and task allocation to the team. This grants autonomy over how work is done, which is the mechanism that builds genuine self-organisation.

Why this answer

Self-organization means the team decides how to accomplish its work. A leader best promotes it by clearly defining the objective (the 'what' and 'why') and then delegating the 'how' to the team, giving them autonomy, mastery, and purpose. This shifts the leader's role from directing tasks to removing impediments and coaching.

Exam trap

The trap is equating 'leadership' with 'control' — candidates often pick options that sound helpful (attending meetings, providing guidance) but actually undermine the autonomy that self-organization requires.

How to eliminate wrong answers

Option A is wrong because attending every technical meeting to provide guidance undermines autonomy and creates dependency, preventing the team from owning technical decisions. Option B is wrong because requiring leadership approval for all decisions centralizes authority and directly contradicts self-organization. Option C is wrong because creating detailed task lists for every team member is micromanagement that removes the team's ownership of planning and execution.

Full explanation →

101

MCQmedium

Which action best demonstrates 'embracing change over following a plan'?

A.Updating the product backlog based on user feedback.

B.Rejecting all feedback until the next project phase.

C.Changing the team members every sprint.

D.Strictly following the initial project roadmap.

AnswerA

Updating the product backlog from user feedback directly enacts responding to change, letting emerging requirements reshape planned work rather than defending the original backlog. This satisfies the agile value of embracing change over rigid plan adherence, since the backlog is the living artefact through which priorities are continuously reprioritised.

Why this answer

Updating the product backlog based on user feedback best demonstrates 'embracing change over following a plan' because it shows the team is responsive to new information and willing to adjust priorities accordingly. This aligns with the Agile Manifesto principle of welcoming changing requirements, even late in development. It reflects a mindset that values customer value and adaptability over rigid adherence to an initial plan.

Exam trap

PMI-ACP often tests the misconception that embracing change means constantly changing team composition or ignoring plans entirely — the correct answer focuses on adapting the product backlog based on feedback while maintaining a stable team and iterative planning.

How to eliminate wrong answers

Option B is wrong because rejecting all feedback until the next project phase is the opposite of embracing change — it rigidly follows the plan and delays responsiveness, which can lead to building the wrong product. Option C is wrong because changing team members every sprint is disruptive and does not relate to embracing change in requirements; it undermines team stability and is not a demonstration of agile adaptability. Option D is wrong because strictly following the initial project roadmap ignores the Agile Manifesto's value of responding to change over following a plan, and it can result in delivering outdated or low-value features.

Full explanation →

102

MCQhard

A customer feedback session reveals a major flaw in the current product design. What is the first thing the Product Owner should do?

A.Ignore the feedback if the project budget is depleted.

B.Blame the development team for the flaw.

C.Immediately delete the feature from the product.

D.Analyze the feedback and update the backlog to address the issue.

AnswerD

The Product Owner owns backlog ordering, so the immediate action is to analyse the feedback and reflect the identified flaw as backlog items, enabling the team to prioritise a fix. This keeps the response within the Product Owner's authority rather than escalating or redesigning directly.

Why this answer

The Product Owner is the sole person accountable for managing and ordering the product backlog, so the correct first response to significant customer feedback is to analyze it and reflect the findings in the backlog. This keeps the product aligned with customer value and allows the team to re-plan in the next refinement or sprint planning session. Deleting, ignoring, or blaming are all reactive behaviors that violate the PO's responsibility to maximize product value.

Exam trap

PMI-ACP often tests the misconception that a Product Owner should shield the team from bad news or make unilateral scope decisions; the trap is choosing an emotional or expedient action (ignore, blame, delete) instead of the disciplined backlog-management response.

How to eliminate wrong answers

Option A is wrong because ignoring valid customer feedback due to budget pressure abandons the PO's duty to maximize value and hides a real product risk rather than managing it. Option B is wrong because blaming the development team is a command-and-control, non-agile behavior that destroys trust and self-organization, and the PO owns backlog content, not the team's blame. Option C is wrong because immediately deleting the feature is an impulsive, unanalyzed decision that skips impact assessment, stakeholder input, and backlog refinement.

Full explanation →

103

MCQhard

A team has high velocity but the customer reports the product is not meeting their needs. What is the most likely cause?

A.The product backlog is not prioritized based on customer value.

B.The sprint duration is too short.

C.The team is lacking a project manager.

D.The team is not using enough automated tests.

AnswerA

High velocity with poor customer outcomes points to effort being spent on low-value items. Prioritising the product backlog by customer value ensures the team delivers the most valuable features first, directly addressing the mismatch between throughput and customer needs.

Why this answer

High velocity with poor customer satisfaction most likely indicates that the team is building the wrong things—the product backlog is not prioritized based on customer value. Velocity measures output, not outcome. If the backlog is not aligned with customer needs, the team can efficiently deliver features that miss the mark.

Exam trap

The trap is equating high velocity with success, causing candidates to overlook that velocity is an output metric and customer value is the true measure of success.

How to eliminate wrong answers

Option B is wrong because sprint duration affects cadence, not the relevance of the work; shorter sprints can improve feedback but do not cause misalignment. Option C is wrong because lacking a project manager is not inherently a problem in Agile, where the Product Owner and Scrum Master handle those responsibilities. Option D is wrong because insufficient automated tests affect quality and speed, not whether the product meets customer needs.

Full explanation →

104

MCQeasy

The Product Owner wants to prioritize items based on the 'Cost of Delay'. What does this metric measure?

A.The potential revenue or value lost by delaying the delivery of a feature.

B.The total budget allocated to a specific feature.

C.The time taken to fix defects found during UAT.

D.The number of hours spent by developers waiting for requirements.

E.The penalty paid to vendors for late delivery.

AnswerA

Cost of Delay quantifies the value forfeited per unit of time a feature remains undelivered, combining revenue, time-criticality and risk reduction. The Product Owner uses it to sequence backlog items by economic impact, so delaying a high-CoD feature directly sacrifices measurable revenue or value.

Why this answer

Cost of Delay (CoD) quantifies the economic impact of not delivering a feature or capability at a given time — it is the revenue, value, or opportunity lost per unit of time that delivery is postponed. It is the numerator in WSJF (Weighted Shortest Job First), where CoD is divided by job duration to prioritize work. The correct answer captures this as potential revenue or value lost by delaying delivery.

Exam trap

PMI-ACP often tests the confusion between Cost of Delay (value lost over time) and project cost or budget — candidates pick the budget option because 'cost' appears in both, missing that CoD is about foregone value, not spend.

How to eliminate wrong answers

Option B is wrong because total budget allocated to a feature is a cost estimate, not a measure of delay impact; CoD is about value foregone over time, not the feature's cost. Option C is wrong because time to fix UAT defects is a quality/rework metric, unrelated to the economic cost of delaying a feature's release. Option D is wrong because developer wait time is a flow efficiency or blocker metric, not a measure of delayed value delivery.

Option E is wrong because vendor late-delivery penalties are a specific contractual cost, not the general economic value lost from delaying a feature to customers or the business.

Full explanation →

105

Multi-Selecthard

Which TWO aspects of team culture are most important for optimizing flow?

Select 2 answers

A.Psychological safety.

B.Collective ownership.

C.Individual competition.

D.Strict hierarchy.

E.High-pressure deadlines.

AnswersA, B

Psychological safety underpins flow by letting team members surface blockers, admit mistakes and challenge process decisions without fear of reprisal. That candour shortens feedback loops and prevents work stalling silently, directly satisfying the stem's requirement for a cultural aspect that optimises flow across the delivery pipeline.

Why this answer

Psychological safety (A) is correct because when team members feel safe to speak up, admit mistakes, and raise impediments without fear of blame, problems surface early and flow is not blocked by hidden issues or silent bottlenecks. Collective ownership (B) is correct because shared responsibility for the whole value stream, rather than hand-offs between siloed specialists, reduces wait times, rework, and the "not my job" gaps that interrupt the smooth, continuous delivery of work. By contrast, individual competition (C) incentivizes local optimization and knowledge hoarding, which creates queues and conflict rather than flow.

Strict hierarchy (D) slows decision-making and communication through approval layers, adding delays and hand-offs. High-pressure deadlines (E) push teams toward multitasking, shortcuts, and burnout, which increase work in progress and variability, all of which degrade flow.

Exam trap

The trap is selecting options that sound like 'strong management' — competition, hierarchy, and pressure deadlines may seem like drivers of performance, but they actively undermine the cultural foundations of flow.

Full explanation →

106

MCQmedium

A team member is consistently finishing their tasks early but other members are struggling. How should the team respond to optimize flow?

A.Assign them more tasks than anyone else.

B.Encourage the team member to assist others with their tasks.

C.Ignore the imbalance.

D.Ask them to start working on next sprint's items.

AnswerB

Pairing the early finisher with struggling members spreads capability across the team, reducing bottlenecks and balancing workload, which optimises flow. This satisfies the stem's goal of improving overall throughput rather than rewarding individual speed or reassigning work away from the team.

Why this answer

In Agile, the team's goal is to optimize flow and deliver value collectively, not to maximize individual utilization. When one member finishes early, the most Agile-aligned response is to have them swarm on other tasks or pair with struggling teammates, which balances WIP and reduces bottlenecks. This supports the self-organizing, cross-functional team principle and avoids creating a new bottleneck by overloading one person.

Exam trap

PMI-ACP often tests the misconception that individual productivity should be maximized by assigning more work to fast members, but Agile emphasizes team-level flow and collective ownership over individual utilization.

How to eliminate wrong answers

Option A is wrong because assigning more tasks to one person increases their WIP, creates a single point of failure, and ignores the team's collective ownership of the sprint goal. Option C is wrong because ignoring the imbalance allows the bottleneck to persist, which violates the principle of continuous improvement and will likely cause the sprint goal to be missed. Option D is wrong because pulling in next sprint's items violates the sprint timebox, disrupts the product backlog ordering, and bypasses the Product Owner's prioritization.

Full explanation →

107

Multi-Selecteasy

Which THREE artifacts are commonly used in agile delivery?

Select 3 answers

A.Burndown Chart.

B.Product Backlog.

C.Annual Financial Report.

D.Sprint Backlog.

E.Individual Performance Review.

AnswersA, B, D

A Burndown Chart plots remaining work against time within a sprint or release, giving teams visible progress tracking. It is a widely used agile artifact, satisfying the stem's requirement for artefacts commonly employed in agile delivery.

Why this answer

A Burndown Chart is correct because it is a standard agile artifact that tracks remaining work (typically story points or hours) against time within a sprint or release, giving the team daily visibility into progress toward the sprint goal. B Product Backlog is correct because it is the single, ordered, emergent list of all product requirements, features, and fixes owned by the Product Owner, serving as the primary source of work in Scrum and other agile methods. D Sprint Backlog is correct because it is the set of Product Backlog items selected for the sprint plus the plan for delivering them, owned by the Development Team and updated daily during the Daily Scrum.

C Annual Financial Report is not an agile delivery artifact; it is a statutory corporate accounting document produced on an annual cycle, unrelated to iterative product development. E Individual Performance Review is not an agile artifact either; it is an HR management process, and agile teams typically favor team-based metrics over individual performance appraisals.

Exam trap

PMI-ACP often tests whether candidates confuse corporate/HR documents (financial reports, performance reviews) with genuine agile artifacts that support transparency and empirical process control.

Full explanation →

108

Multi-Selecteasy

Which TWO methods are effective for gathering stakeholder feedback?

Select 2 answers

A.Observing users while they use the product.

B.Ignoring feedback to prevent scope creep.

C.Asking only one stakeholder for their opinion.

D.Conducting sprint reviews with stakeholders.

E.Sending a survey and never looking at the results.

AnswersA, D

Observation reveals actual usage patterns.

Why this answer

Option A is correct because direct observation of users interacting with the product (e.g., usability testing or contextual inquiry) yields firsthand, unbiased behavioral data about real pain points, workflows, and unmet needs that stakeholders may not articulate in words. Option D is correct because sprint reviews are a formal Scrum inspect-and-adapt event where the team demonstrates a potentially shippable Increment to stakeholders, who then provide structured feedback that feeds directly into the Product Backlog for the next Sprint. Option B is wrong because ignoring feedback does not prevent scope creep—it merely hides requirements and risks delivering a product that fails to meet stakeholder needs.

Option C is wrong because relying on a single stakeholder produces a biased, unrepresentative view and excludes other legitimate perspectives. Option E is wrong because collecting survey data without analyzing the results generates no actionable insight and wastes stakeholders' time.

Exam trap

PMI-ACP often tests the misconception that feedback can be gathered passively or from a single source, when effective feedback requires active engagement with multiple stakeholders through structured and observational methods.

Full explanation →

109

MCQhard

A project is mid-way, and stakeholders want to add a feature that was not in the original product roadmap. What is the appropriate response?

A.Evaluate the feature's value and impact on the backlog priority.

B.Reject the request because it was not in the roadmap.

C.Immediately add the feature to the current sprint.

D.Refer the request to the project manager for approval.

AnswerA

Agile teams handle unplanned requests by assessing the feature's business value and its effect on existing backlog priorities rather than automatically accepting or rejecting it. This lets the product owner reprioritise transparently, satisfying the stem's mid-project scope-change scenario.

Why this answer

In agile, the product backlog is emergent and can change as new information and stakeholder needs arise. The appropriate response to a mid-project feature request is to evaluate its value and impact on backlog priority, then let the product owner decide where it fits relative to existing items. This preserves the team's ability to deliver the highest-value work while remaining responsive to change.

Exam trap

PMI-ACP often tests the product owner's authority over backlog prioritization versus traditional project manager approval, so the trap is choosing 'refer to the project manager' or 'reject because not in roadmap' instead of evaluating value and re-prioritizing.

How to eliminate wrong answers

Option B is wrong because rejecting a request solely because it was not in the original roadmap contradicts agile's embrace of changing requirements and ignores the possibility that the feature adds significant value. Option C is wrong because immediately adding the feature to the current sprint bypasses backlog refinement, prioritization, and the team's capacity planning — it disrupts the sprint commitment and is not the product owner's decision alone. Option D is wrong because referring the request to a project manager for approval reflects a traditional command-and-control model; in agile, the product owner owns backlog prioritization and the team self-manages its work.

Full explanation →

110

Multi-Selecteasy

Which TWO actions should an agile leader take to foster a collaborative culture? (Choose TWO)

Select 2 answers

A.Implement individual performance rankings to encourage competition.

B.Limit the team size to improve focus.

C.Encourage shared responsibility for outcomes rather than individual tasks.

D.Promote transparent communication and information sharing across the team.

E.Centralize all decision-making to ensure consistency.

AnswersC, D

Shared ownership of outcomes shifts focus from individual task completion to collective delivery, which is the mechanism that builds collaborative culture. Team members coordinate and help each other because success is measured jointly, satisfying the agile leader's goal of fostering collaboration.

Why this answer

Option C is correct because encouraging shared responsibility for outcomes rather than individual tasks is a hallmark of agile collaboration: it shifts the team from a collection of specialists optimizing their own work to a self-organizing unit that owns the collective result, which builds trust and mutual accountability. Option D is correct because promoting transparent communication and information sharing across the team is essential to a collaborative culture; agile practices such as daily stand-ups, information radiators, and open backlogs depend on visibility so that impediments surface early and the team can swarm on problems together. The remaining options do not belong: A (individual performance rankings) fosters internal competition and undermines the psychological safety collaboration requires, B (limiting team size) is a structural/scaling consideration rather than a cultural action and does not by itself create collaboration, and E (centralizing decision-making) contradicts the agile principle of decentralized, team-level decision authority.

Exam trap

PMI-ACP often tests the distinction between leadership actions that build team cohesion versus traditional management tactics like ranking or centralizing control, which sound efficient but undermine agile collaboration.

Full explanation →

111

MCQeasy

Which of the following is a sign of a healthy team?

A.The team always completes 100% of the work.

B.Team members feel safe to voice concerns.

C.No one ever disagrees.

D.The team follows the manager's instructions.

AnswerB

Psychological safety is the defining marker of a healthy team: members can raise risks, dissent and bad news without fear of retribution. This directly satisfies the stem's criterion, since such openness surfaces problems early and underpins the trust, collaboration and continuous improvement that PMI-ACP promotes.

Why this answer

A healthy agile team is characterized by psychological safety — members feel safe to raise concerns, admit mistakes, and challenge ideas without fear of retribution. This is a prerequisite for transparency, continuous improvement, and self-organization, and it is a well-documented predictor of team performance. The other options describe compliance or perfection rather than health.

Exam trap

PMI-ACP often tests the misconception that a healthy team is one with no conflict or perfect delivery, tempting candidates toward options that actually describe dysfunction or compliance rather than psychological safety.

How to eliminate wrong answers

Option A is wrong because always completing 100% of work is neither realistic nor a sign of health; it often indicates sandbagging, scope reduction, or hidden technical debt rather than sustainable delivery. Option C is wrong because a team with no disagreement is likely suffering from groupthink or fear of conflict, which suppresses the diverse perspectives needed for good decisions. Option D is wrong because following the manager's instructions describes a command-and-control team, not a self-organizing agile team that owns its process and commitments.

Full explanation →

112

MCQeasy

What is the goal of a servant leader?

A.To report to the board on team failure.

B.To command and control the team.

C.To remove obstacles and empower the team.

D.To make all technical decisions.

AnswerC

Servant leadership inverts traditional authority: the leader's primary output is enabling others by clearing impediments and granting decision-making autonomy. Removing obstacles and empowering the team together define the role's purpose, distinguishing it from command-and-control management.

Why this answer

A servant leader's primary goal is to remove obstacles and empower the team to self-organize and deliver value. This leadership style inverts the traditional pyramid: the leader serves the team rather than the team serving the leader. By clearing impediments and fostering autonomy, the servant leader enables the team to reach high performance without direct command.

Exam trap

The trap is equating leadership with authority — candidates may pick 'command and control' or 'make all decisions' because those sound like strong leadership, when agile defines leadership as service and empowerment.

How to eliminate wrong answers

Option A is wrong because reporting team failures to the board is a punitive, blame-oriented activity that contradicts the supportive nature of servant leadership. Option B is wrong because command and control is the antithesis of servant leadership, which emphasizes empowerment over direction. Option D is wrong because making all technical decisions centralizes authority and prevents the team from developing technical ownership and self-organization.

Full explanation →

113

Multi-Selecteasy

Which TWO methods can a leader use to improve stakeholder engagement? (Choose TWO)

Select 2 answers

A.Provide regular, transparent updates on progress and risks.

B.Avoid interacting with stakeholders to minimize confusion.

C.Invite stakeholders to participate in sprint reviews and planning meetings.

D.Give stakeholders full control over the team's daily tasks.

E.Send stakeholders highly technical documents that they won't understand.

AnswersA, C

Regular, transparent updates on progress and risks build trust by keeping stakeholders informed before issues escalate, directly addressing the engagement gap. This satisfies the stem's requirement for a leadership method that improves stakeholder engagement through open, ongoing communication.

Why this answer

Option A is correct because providing regular, transparent updates on progress and risks builds trust and keeps stakeholders informed, which directly increases their engagement and ability to support the project. Option C is correct because inviting stakeholders to participate in sprint reviews and planning meetings gives them visibility into the team's work and a voice in shaping priorities, which strengthens collaboration and buy-in. Option B is incorrect because avoiding interaction reduces communication and trust, which decreases rather than improves engagement.

Option D is incorrect because giving stakeholders full control over the team's daily tasks undermines the team's self-management and is not a legitimate engagement technique. Option E is incorrect because sending highly technical documents stakeholders won't understand creates confusion and barriers rather than improving engagement.

Exam trap

The trap is choosing extremes—either isolating stakeholders or giving them too much control—rather than the balanced, transparent involvement that PMI-ACP advocates.

Full explanation →

114

Multi-Selecthard

An agile team you lead has consistently met its sprint commitments but has stopped challenging itself and avoids stretch goals. Which TWO actions best demonstrate servant leadership to foster a growth mindset? (Choose two.)

Select 2 answers

A.Share examples of how other teams have benefited from pursuing challenging work and offer to fund relevant training.

B.Set a mandatory stretch goal for the next sprint and track it as a key performance indicator.

C.Publicly compare the team's velocity to that of a higher-performing team to motivate them.

D.Assign each team member a specific stretch task based on your assessment of their weaknesses.

E.Ask the team to reflect on what skills they want to develop and how those align with upcoming product goals.

AnswersA, E

Offering to fund training and sharing success stories provides resources and inspiration without dictating the team's path. This is a classic servant-leader behavior: removing impediments and providing support. It encourages the team to explore stretch goals by reducing the risk associated with learning new skills, thereby nurturing a growth mindset through enablement rather than coercion.

Why this answer

The two actions that best demonstrate servant leadership are those that empower the team to self-identify growth opportunities and provide support through resources and inspiration. Asking the team to reflect on desired skills aligns development with product goals, while offering training and sharing examples removes barriers and encourages exploration. Both actions foster intrinsic motivation and a sustainable growth mindset.

Exam trap

The trap here is confusing servant leadership with permissive leadership or with directive motivation techniques such as mandatory goals or public comparisons.

Full explanation →

115

MCQmedium

A team is doing 'Agile in name only' (Water-Scrum-Fall). What is your first step?

A.Fire the team and start over.

B.Assess current practices against Agile principles.

C.Force them to adopt a specific framework.

D.Do nothing, as long as they deliver.

AnswerB

Assessing current practices against Agile principles establishes an evidence-based baseline before any change, exposing where ceremonies exist without the underlying mindset. This satisfies the need to diagnose Water-Scrum-Fall first, rather than prescribing new tools or ceremonies that would reinforce the existing dysfunction.

Why this answer

When a team is doing 'Agile in name only' (Water-Scrum-Fall), the first step is to assess current practices against Agile principles to identify gaps and understand the root causes. This diagnostic approach respects the team's context and avoids imposing changes without understanding the current state.

Exam trap

PMI-ACP often tests the misconception that the first step in Agile transformation is to impose a framework or replace the team, when the correct approach is to assess current practices against Agile principles first.

How to eliminate wrong answers

Option A is wrong because firing the team and starting over is destructive, ignores the value of existing team knowledge, and does not address the underlying issues. Option C is wrong because forcing a specific framework without assessment can lead to resistance and does not solve the cultural or process misalignments. Option D is wrong because doing nothing allows the dysfunction to persist and fails to deliver the benefits of true Agility.

Full explanation →

116

Multi-Selectmedium

Which TWO techniques are effective for managing cross-team dependencies in a scaled agile environment?

Select 2 answers

A.Adding more middle managers.

B.Scrum of Scrums.

C.Increasing sprint lengths.

D.Individual performance reviews.

E.Visual dependency mapping boards.

AnswersB, E

Scrum of Scrums brings representatives from each team together regularly to surface and resolve cross-team impediments, dependencies and integration issues. This creates a formal synchronisation mechanism that satisfies the coordination requirement in scaled agile environments where many teams must align.

Why this answer

Option B, Scrum of Scrums, is correct because it is a scaled-agile technique in which representatives (often called ambassadors) from multiple Scrum teams meet regularly to coordinate inter-team work, surface cross-team impediments, and synchronize deliveries, directly managing dependencies across teams. Option E, visual dependency mapping boards, is correct because making dependencies explicit on a shared board (physical or digital) lets teams see who depends on whom, sequence work, and resolve blockers before they cascade, which is a proven dependency-management practice in scaled agile. Option A, adding more middle managers, is not a recognized agile scaling technique and tends to add coordination overhead rather than empower teams to manage dependencies.

Option C, increasing sprint lengths, does not address cross-team dependencies and can reduce feedback frequency and adaptability. Option D, individual performance reviews, focuses on evaluating individuals rather than fostering the team-level collaboration and transparency needed to manage dependencies.

Exam trap

PMI-ACP often tests whether candidates will pick bureaucratic solutions (more managers, longer sprints, performance reviews) for coordination problems — the correct answer is always the lightweight, transparency-based Agile mechanism like Scrum of Scrums or visual dependency boards.

Full explanation →

117

Multi-Selectmedium

Which TWO factors are critical for an agile leader when resolving team conflicts? (Choose TWO)

Select 2 answers

A.Ensuring a safe environment where all parties feel heard.

B.Forcing the team to accept your solution to end the conflict quickly.

C.Reporting all conflicts to senior management immediately.

D.Ignoring the conflict until it reaches a critical point.

E.Maintaining a neutral, unbiased stance as a facilitator.

AnswersA, E

Psychological safety lets each party voice concerns without fear of retribution, which surfaces the real disagreement rather than suppressed positions. This satisfies the stem's conflict-resolution constraint, because unresolved conflict often stems from people feeling unheard rather than from the stated issue.

Why this answer

Option A is correct because an agile leader must create psychological safety so every party feels heard, which enables open dialogue and constructive resolution rather than suppressed dissent. Option E is correct because the leader should act as a neutral, unbiased facilitator who guides the team toward its own solution instead of imposing one, preserving the team's self-organization and ownership. Option B is wrong because forcing a solution is directive and undermines the team's autonomy and commitment.

Option C is wrong because escalating every conflict to senior management bypasses the team's ability to resolve issues and erodes trust. Option D is wrong because ignoring conflict allows it to escalate and damage collaboration and performance.

Exam trap

The trap is selecting options that seem efficient (forcing a solution, escalating) but violate agile principles of empowerment and safety; PMI-ACP emphasizes facilitation and neutrality.

Full explanation →

118

MCQmedium

A team has too many competing priorities. Which framework helps them focus?

A.First-come, first-served based on email timestamps.

B.MoSCoW prioritization.

C.Random selection of tasks.

D.The 80/20 rule of project management.

AnswerB

MoSCoW sorts requirements into Must, Should, Could and Won't, forcing the team to agree which items are mandatory for the current timebox. This directly resolves competing priorities by making explicit what can be deferred, rather than treating every request as equally urgent.

Why this answer

MoSCoW prioritization is a widely used agile technique that categorizes requirements into Must have, Should have, Could have, and Won't have. It helps teams focus by explicitly agreeing on what is essential for the current delivery and what can be deferred, thereby reducing competing priorities. In PMI-ACP, MoSCoW is recognized as a simple, effective method for managing scope and ensuring stakeholder alignment on priority.

Exam trap

PMI-ACP often tests the confusion between general heuristics (like the 80/20 rule) and structured prioritization frameworks (like MoSCoW), so candidates may pick the 80/20 rule thinking it is a prioritization technique when it is merely a principle.

How to eliminate wrong answers

Option A is wrong because first-come, first-served based on email timestamps is an arbitrary and reactive approach that does not consider business value or urgency, and can lead to constant context switching. Option C is wrong because random selection of tasks ignores all prioritization criteria and is not a recognized framework; it would exacerbate the problem of competing priorities. Option D is wrong because the 80/20 rule (Pareto principle) is a general heuristic, not a prioritization framework; while it can inform decisions, it does not provide the structured categories needed to resolve conflicting priorities among stakeholders.

Full explanation →

119

MCQhard

A stakeholder demands a significant change to the product scope mid-sprint. As an Agile practitioner, how do you handle this while respecting the team's commitment to the current Sprint Goal?

A.Discuss the change with the Product Owner to evaluate its impact on the Sprint Goal and potential trade-offs.

B.Ask the team to work overtime to accommodate the new requirement.

C.Immediately add the change to the current sprint backlog to satisfy the stakeholder.

D.Refuse the change entirely because the Sprint Plan is fixed.

AnswerA

Routing the request through the Product Owner respects backlog ownership and protects the Sprint Goal, since only the Product Owner may reorder or inject scope. Impact assessment and trade-off discussion let the team decide whether to swap equivalent work rather than silently expand commitment.

Why this answer

In Agile, the Product Owner owns the backlog and prioritization, while the team commits to the Sprint Goal. When a stakeholder demands a mid-sprint change, the correct approach is to discuss it with the Product Owner to assess impact on the Sprint Goal and consider trade-offs. This respects the team's commitment and allows the Product Owner to make an informed decision about whether to adjust scope or defer the change.

Exam trap

PMI-ACP often tests the balance between embracing change and protecting the sprint, and the trap is choosing to either blindly accept the change or outright refuse it, rather than involving the Product Owner.

How to eliminate wrong answers

Option B is wrong because asking the team to work overtime is unsustainable and violates Agile principles of sustainable pace; it also bypasses the Product Owner's authority. Option C is wrong because immediately adding the change to the sprint backlog undermines the Sprint Goal and the team's commitment, and it ignores proper backlog management. Option D is wrong because refusing the change entirely is inflexible; Agile embraces change, but through the proper channel of the Product Owner and backlog refinement.

Full explanation →

120

MCQmedium

A team has a high turnover rate. What should the servant leader focus on?

A.Replacing people faster.

B.Lowering the performance expectations.

C.Investigating the team culture and working conditions.

D.Hiring more senior developers.

AnswerC

High turnover signals systemic issues rather than individual failings. A servant leader removes impediments and improves the environment, so investigating culture and working conditions addresses the root causes driving people away, rather than blaming or replacing team members.

Why this answer

High turnover is a systemic signal, not a recruiting problem, so a servant leader must investigate the root causes in team culture and working conditions. Servant leadership means removing impediments and creating an environment where people can succeed, which starts with diagnosing why people are leaving. Only after understanding the drivers — workload, conflict, lack of autonomy, poor tooling — can the leader act effectively.

Exam trap

The trap is the instinct to solve a people problem with a staffing action, so candidates pick 'replace faster' or 'hire seniors' instead of diagnosing the environment the servant leader actually owns.

How to eliminate wrong answers

Option A is wrong because replacing people faster treats the symptom and accelerates the churn cycle, ignoring the underlying conditions that drive attrition. Option B is wrong because lowering performance expectations demoralizes the team and does not address why people are leaving, effectively rewarding a broken environment. Option D is wrong because hiring more senior developers does not fix cultural or working-condition problems and may increase friction if the environment remains toxic.

Full explanation →

121

Multi-Selecthard

Which TWO factors make a team 'self-organizing'?

Select 2 answers

A.The team takes collective responsibility for outcomes

B.The team is granted the autonomy to choose how to do their work

C.Each team member works in complete isolation

D.The manager makes all the decisions

E.Strict adherence to the original plan

AnswersA, B

Collective accountability means the whole team, rather than a single lead, owns delivery outcomes and commits to them jointly. This satisfies the self-organising criterion because shared ownership drives the team to plan, decide and adjust its own work without external direction.

Why this answer

Option A is correct because a self-organizing team owns its results collectively, meaning the whole team—not a single lead or manager—is accountable for delivering the outcome, which is a defining characteristic of self-organization. Option B is correct because self-organization requires genuine autonomy: the team itself decides how to approach, sequence, and execute the work rather than being told the method by an external authority. Together, collective ownership (A) plus autonomy over the 'how' (B) are the two factors that make a team self-organizing.

Option C is wrong because isolation is the opposite of a team; self-organizing teams collaborate and coordinate internally. Option D is wrong because a manager making all decisions describes a command-and-control structure, which removes the team's autonomy. Option E is wrong because rigid adherence to an original plan prevents the team from adapting its own approach, which self-organizing teams are expected to do.

Exam trap

PMI-ACP often tests the confusion between self-organization and isolation or lack of accountability — candidates may incorrectly think autonomy means working alone or having no shared responsibility.

Full explanation →

122

MCQeasy

What does the 'P' in INVEST stand for?

A.The question contains a trick; P is not part of INVEST.

B.Prioritized.

C.Precise.

D.Productive.

AnswerA

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small and Testable. The letter P appears nowhere in the acronym, so any option claiming P represents a genuine INVEST criterion is factually wrong. The stem's premise is therefore a deliberate trick.

Why this answer

INVEST is an acronym for Independent, Negotiable, Valuable, Estimable, Small, and Testable. The letter 'P' does not appear in INVEST, so the correct answer is that the question contains a trick. This is a knowledge-check question testing whether candidates actually know the acronym rather than guessing a plausible-sounding word.

Exam trap

PMI-ACP often tests acronym recall with distractor words that sound plausible — candidates who half-remember INVEST may pick 'Prioritized' or 'Precise' instead of recognizing the trick.

How to eliminate wrong answers

Option B is wrong because 'Prioritized' is not part of INVEST — prioritization is handled separately in backlog refinement, not in the story quality criteria. Option C is wrong because 'Precise' is not an INVEST criterion; stories should be negotiable, not overly precise upfront. Option D is wrong because 'Productive' is not part of INVEST — productivity is a team outcome, not a story attribute.

Full explanation →

123

MCQhard

An organization is moving from project-based to product-based funding. How should the agile practitioner advise the team to measure success?

A.Report primarily on task completion percentages from the Jira dashboard.

B.Utilize value-based metrics like Net Promoter Score (NPS) and Customer Acquisition Cost (CAC).

C.Track the number of features delivered per quarter.

D.Focus on budget adherence and total project spend.

AnswerB

Product-based funding shifts investment decisions to outcome delivery, so value-based metrics such as Net Promoter Score and Customer Acquisition Cost measure realised customer and business value rather than schedule or budget adherence, matching the stem's funding-model change.

Why this answer

Moving from project-based to product-based funding shifts the focus from output and budget adherence to delivered customer and business value. Value-based metrics such as Net Promoter Score and Customer Acquisition Cost directly measure whether the product is achieving meaningful outcomes for users and the business. This aligns with the product mindset's emphasis on outcomes over outputs.

Exam trap

PMI-ACP often tests the trap of equating productivity with output counts (features, tasks, budget) instead of recognizing that product funding demands outcome/value metrics like NPS and CAC.

How to eliminate wrong answers

Option A is wrong because task completion percentages are output metrics that say nothing about customer or business value delivered. Option C is wrong because counting features per quarter is a classic output vanity metric that can rise while value stagnates. Option D is wrong because budget adherence and total spend are project-accounting measures that reward spending discipline, not value creation, and are exactly what product funding moves away from.

Full explanation →

124

MCQeasy

What does a 'Definition of Done' ensure in an agile delivery?

A.That the project budget is not exceeded.

B.That the team is working the required number of hours.

C.That all requirements have been met regardless of effort.

D.A common understanding of quality and readiness criteria for increments.

AnswerD

The Definition of Done is a shared checklist of quality and completeness criteria applied to every increment, so 'done' means the same thing to developers, testers and the product owner. That shared understanding prevents incomplete work being counted as finished, which is precisely the readiness guarantee the stem asks about.

Why this answer

The Definition of Done (DoD) is a shared, explicit checklist that describes the quality attributes and completion criteria every increment must satisfy before it can be considered 'done.' It creates a common understanding across the team, PO, and stakeholders of what 'done' actually means, preventing the ambiguity that leads to hidden technical debt and rework.

Exam trap

PMI-ACP often tests the confusion between the Definition of Done (global quality gate) and acceptance criteria (item-specific functional conditions), so options about 'all requirements met' or 'budget' are classic distractors.

How to eliminate wrong answers

Option A is wrong because budget adherence is a project-management concern tracked via cost baselines and earned value, not the DoD. Option B is wrong because hours worked is a resource-utilization metric, and agile explicitly decouples effort from value. Option C is wrong because 'all requirements met regardless of effort' describes scope completion, not quality — the DoD is about quality and readiness, and it applies uniformly to every increment regardless of size.

Full explanation →

125

MCQhard

A team is struggling to maintain focus due to 'firefighting' requests from the business. How do you coach them?

A.Suggest the team work on these requests at night.

B.Work with the Product Owner to create a clear backlog policy for incoming requests and protect the sprint.

C.Ask the team to switch to a Kanban approach.

D.Tell the team to stop accepting any outside work.

AnswerB

Firefighting stems from unmanaged inbound work bypassing the backlog. Establishing an explicit policy with the Product Owner gives the team a agreed route for requests, letting them protect the sprint's commitment and sustain focus instead of reacting ad hoc.

Why this answer

Working with the Product Owner to establish a clear backlog policy for incoming requests and protecting the sprint is the correct coaching action because it addresses the root cause: unmanaged work entering the team's workflow. The Product Owner is responsible for backlog prioritization, so collaborating with them ensures that firefighting requests are evaluated against sprint goals rather than disrupting the team ad hoc. This preserves the team's focus and maintains the integrity of the sprint commitment.

Exam trap

PMI-ACP often tests the misconception that the team should simply work harder or that the Scrum Master should shield the team by rejecting all outside work — the correct answer always involves collaborating with the Product Owner to manage the backlog and protect the sprint.

How to eliminate wrong answers

Option A is wrong because working at night is unsustainable, violates agile principles of sustainable pace, and does not solve the underlying process problem — it merely masks it while increasing burnout risk. Option C is wrong because switching to Kanban is a process change that may not be warranted; the issue is not the framework but the lack of a policy for handling incoming requests, and Kanban still requires work-in-progress limits and prioritization. Option D is wrong because telling the team to stop accepting any outside work is unrealistic and ignores the need to balance stakeholder needs — the correct approach is to manage requests through the Product Owner, not to refuse them outright.

Full explanation →

126

MCQhard

Two developers are arguing about a design choice. How do you intervene?

A.Ask them to prototype both options to see which works best.

B.Force them to compromise on a sub-optimal design.

C.Choose the design you prefer.

D.Tell them to flip a coin.

AnswerA

Prototyping both designs converts an abstract disagreement into empirical evidence, letting the team compare working implementations against real constraints. This resolves the conflict through data rather than opinion, which suits an agile team empowered to make technical decisions collaboratively.

Why this answer

In Agile, empirical decision-making is preferred over opinion-based conflict resolution. Prototyping both options lets the team gather real data on feasibility, performance, and maintainability before committing, which aligns with the Agile principle of 'working software over comprehensive documentation' and short feedback loops. This converts a subjective argument into an evidence-based decision the whole team can support.

Exam trap

PMI-ACP often tests the instinct to 'resolve conflict quickly' — candidates pick compromise or authority-based answers, but Agile favors empirical, data-driven decisions that preserve team ownership.

How to eliminate wrong answers

Option B is wrong because forcing a compromise produces a design that satisfies neither developer and is often technically inferior, violating the principle of technical excellence. Option C is wrong because the Scrum Master/coach should not impose a personal design preference — that undermines team self-organization and ownership. Option D is wrong because random selection (coin flip) abandons empirical decision-making and wastes the opportunity to learn which design actually works.

Full explanation →

127

MCQmedium

Your team is failing to meet the sprint goal due to a lack of clear requirements. How should you facilitate?

A.Facilitate a session between the PO and the team to clarify the requirements and improve the refinement process.

B.Write the requirements yourself.

C.Ask the team to guess what the requirements are.

D.Cancel the sprint.

AnswerA

Clarifying requirements with the Product Owner directly addresses the unclear-requirements constraint causing missed sprint goals. The facilitated refinement session lets the team and PO jointly decompose and agree acceptance criteria, restoring shared understanding before the next sprint, rather than the Scrum Master unilaterally rewriting backlog items.

Why this answer

Facilitating a session between the Product Owner and the team (A) addresses the root cause — unclear requirements — by improving communication and refinement. The Scrum Master or agile leader should enable this conversation rather than solving it unilaterally. This approach also strengthens the refinement process so future sprints have clearer, better-understood backlog items.

Exam trap

The trap is choosing a directive action like writing requirements or canceling the sprint, when the agile leader's role is to facilitate collaboration between the PO and the team to fix the underlying process.

How to eliminate wrong answers

Option B is wrong because writing requirements yourself usurps the Product Owner's role and prevents the team from developing shared understanding. Option C is wrong because asking the team to guess requirements guarantees rework and defects, and it is not a facilitation strategy. Option D is wrong because canceling the sprint is a drastic action that should only occur when the sprint goal is obsolete, not when requirements need clarification.

Full explanation →

128

MCQmedium

A team is struggling with high levels of 'technical debt' that slow down new feature delivery. What should the team do?

A.Request a new budget to hire external experts.

B.Stop all new feature work for a year to fix everything.

C.Ignore the debt and continue adding features.

D.Allocate a percentage of each sprint's capacity to address technical debt.

AnswerD

Technical debt accumulates when refactoring is perpetually deferred, so dedicating a fixed slice of each sprint's capacity to remediation ensures it is addressed continuously rather than starved by feature work. This directly satisfies the stem's constraint of slowing feature delivery by making debt reduction a planned, sustainable commitment.

Why this answer

Allocating a percentage of each sprint's capacity to technical debt (D) is the balanced agile approach: it continuously reduces debt while still delivering new features. This prevents the debt from compounding and slowing delivery further.

Exam trap

PMI-ACP often tests the misconception that technical debt must be addressed either by a complete freeze or by ignoring it, when the correct agile approach is continuous, incremental allocation of capacity.

How to eliminate wrong answers

Option A is wrong because hiring external experts is a costly, one-off tactic that does not build the team's capability to manage debt sustainably and may not address the root causes. Option B is wrong because stopping all feature work for a year is an extreme, unrealistic freeze that ignores business needs and can be just as damaging as ignoring the debt. Option C is wrong because ignoring technical debt allows it to compound, increasing future rework and slowing delivery even more.

Full explanation →

129

MCQmedium

An agile team's burn-down chart has been flat for six iterations while the burn-up chart shows story points completing steadily. The product owner is confused because the release forecast slipped. Which action best resolves the discrepancy in the team's delivery metrics?

A.Recalculate the burn-down using only accepted stories and inspect whether story points are being counted at task completion rather than at acceptance.

B.Ask the Scrum Master to increase the team's velocity target so the burn-down line steepens.

C.Replace the burn-down chart with a cumulative flow diagram and stop tracking remaining work.

D.Switch the team from story points to ideal days and rebuild both charts on the new unit.

AnswerA

A flat burn-down alongside a rising burn-up indicates work is being counted before it meets the Definition of Done. Re-baselining the burn-down to accepted stories and confirming when points are awarded restores the metric's predictive value and gives the product owner an honest release forecast, which is exactly what the scenario requires.

Why this answer

When a burn-down stays flat while a burn-up rises, the usual cause is that story points are being awarded before stories satisfy the Definition of Done. Aligning the burn-down to accepted work and verifying the counting trigger corrects the data, restores the chart's forecasting ability, and gives the product owner a defensible release projection.

Exam trap

The trap here is assuming the two charts measure different things and that one should simply be discarded, rather than investigating the timing of when work is counted.

Full explanation →

130

MCQmedium

You are coaching a team that is moving from a traditional command-and-control environment to agile. A stakeholder keeps bypassing the Product Owner to assign tasks directly to developers. What is your best course of action?

A.Update the Scrum Guide to include strict penalties for stakeholders.

B.Discuss with the stakeholder how the Product Owner manages the backlog and why direct assignments disrupt flow.

C.Instruct the developers to ignore the stakeholder's requests.

D.Have the developers log the work as 'technical debt' to keep track of it.

AnswerB

The stakeholder bypasses the Product Owner, undermining backlog ownership and team flow. Coaching the stakeholder on how the Product Owner sequences and prioritises work addresses the root cause directly, restoring the agile role boundary without escalating or publicly confronting anyone, which satisfies the coaching stance expected of an agile practitioner.

Why this answer

The best agile-coaching response is to address the root cause through direct, respectful communication with the stakeholder, explaining how the Product Owner owns backlog prioritization and how bypassing that role disrupts team flow, WIP limits, and sprint commitments. This preserves the stakeholder relationship while reinforcing the agile operating model. It is a coaching and influencing action, not a punitive or avoidance one.

Exam trap

PMI-ACP often tests whether candidates choose collaborative coaching over punitive or avoidance tactics — the trap is picking 'instruct developers to ignore' because it seems to protect the team, but agile answers must preserve relationships and address the systemic cause.

How to eliminate wrong answers

Option A is wrong because the Scrum Guide is a framework document maintained by its authors — a team cannot 'update' it, and adding penalties is antithetical to agile's self-organizing, trust-based culture. Option C is wrong because instructing developers to ignore the stakeholder is a confrontational, passive-aggressive tactic that damages relationships, leaves the stakeholder uninformed, and does not address the systemic misunderstanding of roles. Option D is wrong because logging the work as 'technical debt' misclassifies unplanned stakeholder-driven work, hides the real problem (role confusion), and corrupts the backlog's integrity — technical debt has a specific meaning (deferred design/quality work), not 'work I didn't want to do.'

Full explanation →

131

Multi-Selecteasy

Which TWO of the following are benefits of maintaining a prioritized product backlog?

Select 2 answers

A.It allows the team to avoid all technical debt.

B.It guarantees that the project will finish on time.

C.It ensures the highest value items are addressed early.

D.It provides transparency to stakeholders on current priorities.

E.It eliminates the need for sprint planning.

AnswersC, D

Ordering the backlog by value places the highest-value items at the top, so the team delivers them in early iterations. This directly satisfies the benefit of addressing maximum business value first, rather than leaving valuable work until later sprints.

Why this answer

Option C is correct because a prioritized product backlog orders items by business value, risk, or dependency, so the highest-value work is pulled into early sprints and delivered sooner, maximizing return on investment. Option D is correct because the ordered backlog is a visible artifact that shows stakeholders exactly what the team plans to work on next and why, giving transparency into current priorities and enabling informed feedback. Options A, B, and E do not belong: a prioritized backlog cannot eliminate all technical debt (A), cannot guarantee on-time delivery since estimates and impediments still vary (B), and does not remove the need for sprint planning, where the team selects and decomposes backlog items into a sprint goal (E).

Exam trap

PMI-ACP often tests the difference between benefits and guarantees; the trap is selecting absolute claims like 'avoids all technical debt' or 'guarantees on-time delivery' instead of the realistic benefits of prioritization and transparency.

Full explanation →

132

MCQmedium

A stakeholder demands that a feature be completed by next week. The team identifies this as a high-risk task. What should the Product Owner do?

A.Discuss the risks with the stakeholder and negotiate the timeline or scope.

B.Force the team to work overtime to ensure completion.

C.Delegate the task to a junior developer to save costs.

D.Agree to the request to satisfy the stakeholder.

AnswerA

The Product Owner owns backlog prioritisation and value trade-offs, so addressing the stakeholder's fixed-date demand means surfacing the identified risk and negotiating either the timeline or the feature scope, rather than committing the team to an unachievable deadline.

Why this answer

When a stakeholder demands a high-risk feature on a tight timeline, the Product Owner should discuss the risks with the stakeholder and negotiate timeline or scope, because the PO is accountable for maximizing value while protecting the team's sustainable pace. This preserves transparency and allows informed trade-offs rather than committing to an unrealistic date. It also respects the team's self-management and the empirical nature of agile planning.

Exam trap

PMI-ACP often tests the misconception that a PO should always say yes to stakeholders; the trap is choosing compliance or heroics (overtime, delegation, blind agreement) instead of transparent negotiation and risk discussion.

How to eliminate wrong answers

Option B is wrong because forcing overtime violates sustainable pace, increases defect risk, and is a command-and-control response that undermines self-organization. Option C is wrong because delegating a high-risk task to a junior developer to save costs ignores skill fit and increases the likelihood of failure, which is poor risk management. Option D is wrong because agreeing to the request just to satisfy the stakeholder hides the risk, sets up the team for failure, and violates the PO's duty to be transparent about trade-offs.

Full explanation →

133

MCQmedium

A Scrum team is struggling with a recurring issue: during sprint reviews, stakeholders often point out that the increment does not meet their expectations, even though the team followed the acceptance criteria. The team wants to improve alignment with stakeholders. What is the most Agile-aligned action?

A.Have the team strictly adhere to the acceptance criteria and explain to stakeholders that the criteria were met, so expectations should align.

B.Invite stakeholders to participate in refinement sessions to clarify and evolve acceptance criteria collaboratively.

C.Schedule a separate meeting after each sprint review to gather feedback and update the backlog accordingly.

D.Ask the product owner to create more detailed acceptance criteria and distribute them to stakeholders for sign-off before each sprint.

AnswerB

This action aligns with Agile by fostering continuous collaboration with stakeholders, ensuring shared understanding of requirements. By involving stakeholders in refinement, the team can adapt acceptance criteria based on feedback, reducing the gap between expectations and delivery. It promotes transparency and early feedback, which are core to Agile principles and help prevent late-stage surprises.

Why this answer

The most Agile-aligned action is to involve stakeholders directly in refinement sessions to collaboratively define and evolve acceptance criteria. This fosters shared understanding, transparency, and continuous feedback, which are essential to delivering value that meets stakeholder expectations. It embodies the Agile principle of customer collaboration and responding to change.

Exam trap

The trap here is thinking that more detailed acceptance criteria or post-hoc feedback meetings will solve the alignment issue, when the real need is ongoing, direct collaboration with stakeholders during refinement.

Full explanation →

134

MCQmedium

A team is having difficulty estimating task sizes. What activity should the practitioner facilitate?

A.Individual guessing.

B.Expert estimation by the manager.

C.Using historical data from different projects.

D.Planning Poker.

AnswerD

Planning Poker applies wideband Delphi with simultaneous card revelation, so individual estimates are not anchored by senior voices. This directly addresses the team's difficulty sizing tasks by exposing divergent assumptions, forcing discussion until consensus, and producing faster relative estimates than open debate.

Why this answer

Planning Poker is a collaborative estimation technique where team members use cards (often Fibonacci numbers) to simultaneously estimate user story effort, discuss differences, and converge on a consensus estimate. It directly addresses estimation difficulty by leveraging team knowledge and reducing anchoring bias.

Exam trap

PMI-ACP often tests the misconception that estimation should be done by a manager or expert alone, when Agile promotes team-based collaborative estimation techniques like Planning Poker.

How to eliminate wrong answers

Option A is wrong because individual guessing lacks collaboration and does not leverage team expertise, leading to inaccurate estimates. Option B is wrong because expert estimation by a manager is a top-down approach that ignores the team's collective knowledge and violates Agile self-organization principles. Option C is wrong because using historical data from different projects may not be relevant to the current context and does not engage the team in the estimation process.

Full explanation →

135

MCQhard

A large agile project requires coordinating work across four teams. How should the practitioner handle dependency management?

A.Require all teams to participate in a daily Scrum of Scrums.

B.Stop all work until the dependencies are resolved.

C.Assign a single manager to direct all four teams.

D.Merge all teams into one large team to simplify communication.

AnswerA

A daily Scrum of Scrums gives cross-team representatives a recurring forum to surface, track and resolve inter-team dependencies before they block delivery. This provides the coordination cadence four teams need, which single-team events cannot supply.

Why this answer

For a large agile project with four teams, the standard scaling mechanism for dependency management is a Scrum of Scrums, where representatives from each team meet daily (or frequently) to coordinate cross-team dependencies, integrate work, and resolve impediments. This creates a communication network that surfaces and resolves dependencies without halting work or centralizing control.

Exam trap

PMI-ACP often tests the temptation to solve coordination problems with traditional management (single manager, merge teams) or blocking (stop work) — candidates must recognize that agile scaling favors lightweight coordination mechanisms like Scrum of Scrums.

How to eliminate wrong answers

Option B is wrong because stopping all work until dependencies are resolved is a blocking, non-agile approach that destroys flow and wastes capacity; dependencies should be managed continuously, not by halting delivery. Option C is wrong because assigning a single manager to direct all four teams reintroduces command-and-control management, undermining self-organization and the agile principle of team autonomy. Option D is wrong because merging all teams into one large team increases communication overhead (Brooks's Law) and reduces agility; scaling frameworks like Scrum of Scrums or SAFe exist precisely to coordinate multiple teams without merging them.

Full explanation →

136

MCQhard

You notice a high-performer is hoarding knowledge, creating a bottleneck. How do you handle this?

A.Quietly mentor the individual on the value of team collective ownership.

B.Fire the individual.

C.Ignore it since the individual is productive.

D.Promote the high-performer to a lead role.

AnswerA

Quietly mentoring the individual preserves their standing while addressing the bottleneck's root cause: knowledge hoarding. It reinforces collective ownership, which is the agile principle that sustains flow and reduces single-person dependency, rather than publicly shaming or escalating the behaviour.

Why this answer

The agile leader should address the behavior through private coaching, helping the high-performer understand the value of collective ownership and knowledge sharing. This preserves the individual's motivation while fixing the systemic bottleneck. It aligns with servant leadership and team empowerment.

Exam trap

PMI-ACP often tests the misconception that high individual productivity justifies ignoring team-level dysfunction, when the correct agile response is to coach the behavior and restore collective ownership.

How to eliminate wrong answers

Option B is wrong because firing a high-performer is a disproportionate, punitive response that destroys value and morale; the behavior, not the person, needs correction. Option C is wrong because ignoring the bottleneck allows it to persist and worsen, undermining team resilience and creating a single point of failure. Option D is wrong because promoting the high-performer to a lead role rewards the hoarding behavior and may amplify the bottleneck by giving them more influence without addressing the root cause.

Full explanation →

137

Multi-Selectmedium

An agile team is struggling with unpredictable delivery because work items vary greatly in size and complexity. The practitioner wants to improve flow and predictability. Which TWO actions should the practitioner recommend? (Choose two.)

Select 2 answers

A.Encourage the team to break down large work items into smaller, similarly sized pieces before starting them.

B.Use a cumulative flow diagram to visualize bottlenecks and adjust WIP limits accordingly.

C.Assign each large work item to a single specialist to ensure accountability.

D.Increase the sprint length to give the team more time to complete large items.

E.Implement a strict rule that no work item can exceed a predetermined maximum size.

AnswersA, B

Smaller, similarly sized work items reduce variability in cycle time and make flow more predictable. When items are too large or inconsistent in size, they clog the system and make forecasting difficult. Breaking them down enables smoother pull through the workflow and supports better WIP management, directly addressing the root cause of unpredictability.

Why this answer

To improve flow and predictability, the team should reduce variability by breaking down large items into smaller, similarly sized pieces, and use a cumulative flow diagram to visualize bottlenecks and adjust WIP limits. These actions address the root cause of unpredictable delivery by smoothing the flow of work and enabling data-driven adjustments, rather than imposing rigid rules, extending sprints, or creating specialist silos.

Exam trap

The trap here is thinking that a strict maximum size rule or longer sprints will solve unpredictability, when the real fix is reducing work item variability and using flow visualization to manage WIP.

Full explanation →

138

MCQeasy

A stakeholder is unhappy with the product's progress. How do you address this?

A.Invite them to the next sprint review to see the progress and discuss the product roadmap.

B.Show them a more optimistic report.

C.Stop the project.

D.Tell them the team is doing their best.

AnswerA

The sprint review gives the stakeholder direct visibility of the increment, replacing assumption with evidence, while roadmap discussion reframes progress against the longer-term plan. This addresses the dissatisfaction's root cause: an information gap, not necessarily actual delivery failure.

Why this answer

Inviting the stakeholder to the sprint review lets them see working product increment and discuss the roadmap directly with the team. This provides transparency, builds trust, and gives the stakeholder accurate information rather than filtered reports. It is the agile-correct way to address dissatisfaction with progress.

Exam trap

PMI-ACP often tests whether candidates choose transparency and stakeholder engagement over optimistic reporting or defensive responses; the trap is picking a 'manage perception' answer instead of an 'inspect and adapt' answer.

How to eliminate wrong answers

Option B is wrong because showing an optimistic report is dishonest, undermines transparency, and violates the agile principle of empirical process control — it hides reality instead of inspecting it. Option C is wrong because stopping the project is a drastic, unjustified action that does not address the stakeholder's concern and ignores the possibility of adapting scope or approach. Option D is wrong because telling them the team is doing their best is a defensive, non-actionable response that does not give the stakeholder visibility or a path to influence priorities.

Full explanation →

139

Multi-Selectmedium

Which THREE practices contribute to a healthy, continuous delivery pipeline?

Select 3 answers

A.Manual gatekeepers for every change.

B.Automated deployment.

C.Working without documentation.

D.Continuous integration.

E.Automated testing.

AnswersB, D, E

Automated deployment moves validated builds into environments without manual intervention, removing handoff delays and human error. This keeps the pipeline flowing continuously from commit to release, satisfying the requirement for a healthy, continuous delivery pipeline.

Why this answer

Automated deployment (B) is correct because it removes manual, error-prone release steps and lets validated builds be promoted to environments repeatably and quickly, which is essential for a continuous delivery pipeline. Continuous integration (D) is correct because developers frequently merge code into a shared mainline where each commit triggers an automated build and test cycle, catching integration defects early and keeping the codebase always releasable. Automated testing (E) is correct because a pipeline needs fast, reliable, repeatable verification (unit, integration, and other test suites) to gate each change without human bottlenecks, enabling safe frequent releases.

The unmarked options do not belong: manual gatekeepers for every change (A) introduce delays and human bottlenecks that break the flow and speed of continuous delivery, and working without documentation (C) undermines maintainability, onboarding, and operational reliability rather than contributing to pipeline health.

Exam trap

PMI-ACP often tests the confusion between continuous delivery and continuous deployment, and candidates may wrongly select 'manual gatekeepers' thinking human oversight is a quality practice rather than a pipeline anti-pattern.

Full explanation →

140

Multi-Selectmedium

Which THREE of the following are key to the Agile mindset?

Select 3 answers

A.Preference for command-and-control management

B.Commitment to empirical process control (inspect and adapt)

C.Valuing team self-organization over individual direction

D.Relentless focus on delivering value to the customer

E.Strict avoidance of any project documentation

AnswersB, C, D

Empirical process control means transparency, inspection and adaptation underpin decisions, with short cycles generating feedback that corrects direction. This inspect-and-adapt loop is central to the Agile mindset, satisfying the stem's requirement for a key principle rather than a mere practise.

Why this answer

Option B is correct because the Agile mindset rests on empirical process control: work proceeds in short iterations where transparency, inspection, and adaptation let teams adjust plans based on real results rather than rigid upfront predictions. Option C is correct because Agile favors self-organizing, cross-functional teams that decide how to accomplish their work, rather than managers directing each individual's tasks. Option D is correct because Agile's core purpose is to deliver value to the customer continuously and early, prioritizing working outcomes that satisfy customer needs over internal process ceremony.

Option A is not part of the Agile mindset, since command-and-control management contradicts self-organization and empirical adaptation. Option E is also wrong because Agile values documentation that adds real value; it does not demand strict avoidance of all documentation, only a preference for working software over comprehensive documentation.

Exam trap

PMI-ACP often tests whether candidates can distinguish the Agile mindset from Agile ceremonies — options that sound disciplined or efficient (command-and-control, no documentation) are tempting but contradict the underlying values.

Full explanation →

141

MCQeasy

An agile team is coordinating tasks across multiple cross-functional teams. Which meeting is most effective for synchronizing dependencies?

A.Sprint Retrospective.

B.Daily Stand-up.

C.Scrum of Scrums.

D.Sprint Planning.

AnswerC

Scrum of Scrums directly addresses cross-team dependency synchronisation by having each team's representative report progress, impediments and upcoming inter-team dependencies. This satisfies the stem's multi-team coordination constraint, unlike single-team ceremonies such as daily stand-ups, which cannot surface or resolve dependencies spanning several cross-functional teams.

Why this answer

The Scrum of Scrums is a scaled-agile ceremony where representatives (usually one per team) from multiple Scrum teams meet regularly to coordinate cross-team dependencies, integration points, and impediments. It is specifically designed to synchronize work across teams that share a product or delivery goal. Daily Stand-ups synchronize work within a single team, not across teams.

Exam trap

PMI-ACP often tests the boundary between intra-team and cross-team ceremonies — candidates pick Daily Stand-up because it sounds like 'synchronizing,' but only Scrum of Scrums is designed for multi-team dependency coordination.

How to eliminate wrong answers

Option A is wrong because the Sprint Retrospective is an intra-team ceremony focused on inspecting and adapting the team's own process at the end of a sprint — it does not address cross-team dependency coordination. Option B is wrong because the Daily Stand-up is a 15-minute intra-team sync where members share progress, plans, and blockers; it does not include other teams' representatives and is not designed for cross-team dependency management. Option D is wrong because Sprint Planning is where a single team selects backlog items and plans the sprint's work — it is a planning event, not an ongoing synchronization mechanism for dependencies across multiple teams.

Full explanation →

142

Multi-Selectmedium

Which THREE activities are part of product backlog refinement?

Select 3 answers

A.Conducting the daily stand-up meeting.

B.Re-ordering items based on current priorities.

C.Defining the product's annual budget.

D.Estimating the size of backlog items.

E.Adding detail to user stories.

AnswersB, D, E

Refinement continuously grooms the backlog, and re-ordering items by current business value or priority keeps the highest-value work at the top, ready for the next iteration. This is a core refinement activity alongside detailing and estimating.

Why this answer

Backlog refinement is the ongoing activity of reviewing and improving the product backlog, and re-ordering items based on current priorities (B) is a core part of it because the Product Owner continuously reprioritizes items so the most valuable work sits at the top for upcoming sprints. Estimating the size of backlog items (D) is also part of refinement, since the team assigns relative estimates (e.g., story points) to items so they can be planned and forecast effectively. Adding detail to user stories (E) is likewise correct, as refinement involves clarifying, splitting, and elaborating items with acceptance criteria so they are ready for a future sprint.

The daily stand-up (A) is a separate Scrum event for inspecting progress toward the sprint goal, not a refinement activity, and defining the product's annual budget (C) is a financial/portfolio activity outside the scope of backlog refinement.

Exam trap

PMI-ACP often tests the confusion between backlog refinement and other Scrum events — candidates incorrectly include the Daily Stand-up or Sprint Planning activities as refinement tasks.

Full explanation →

143

MCQhard

A newly formed Agile team is co-located but has members from three different departments with different reporting managers. During the first retrospective, several members express confusion about who decides priorities and how work should be assigned. As the PMI-ACP practitioner, which action best aligns with an Agile mindset?

A.Facilitate a team working agreement session to clarify how the team will make decisions and pull work.

B.Escalate to the program manager to define a single prioritization owner and task allocation process.

C.Create a RACI chart that assigns decision rights and task ownership for all team activities.

D.Ask each department manager to assign tasks to their people so accountability is clear.

AnswerA

A working agreement is a lightweight, team-owned mechanism that lets the team define its own decision-making and work-pull norms. Facilitating this session directly addresses the confusion while preserving self-organization, which is central to the Agile mindset. It also creates shared ownership across departments rather than imposing an external structure, helping the team mature into a true cross-functional unit.

Why this answer

The Agile mindset expects the team itself to establish how it will work together, including decision-making and work-pull norms. Facilitating a working agreement session directly empowers the team to resolve its confusion while preserving self-organization. RACI charts, manager-driven task assignment, and escalation all impose external control, which conflicts with the principle that self-organizing teams produce the best architectures, requirements, and designs.

Exam trap

The trap here is thinking that role confusion must be fixed by a formal governance artifact or escalation, when the Agile-aligned response is to let the team define its own working agreement.

Full explanation →

144

Multi-Selecthard

Which TWO techniques help a leader address 'groupthink' in a team? (Choose TWO)

Select 2 answers

A.Use anonymous polling to gather honest input before group discussion.

B.Require the most senior person to speak first.

C.Ask the team to ignore outside opinions.

D.Tell the team they must reach a consensus immediately.

E.Encourage 'devil's advocate' roles during discussions.

AnswersA, E

Anonymous polling collects each member's view privately before open discussion, removing the social pressure that drives self-censorship. This directly counters groupthink's illusion of unanimity, satisfying the stem's requirement for a technique that surfaces honest dissent within the team.

Why this answer

Option A is correct because anonymous polling collects each member's independent judgment before the group can converge on a dominant view, removing social pressure and status effects that suppress dissent and thereby preventing premature consensus. Option E is correct because assigning a devil's advocate role institutionalizes constructive dissent, forcing the team to test assumptions and surface counterarguments rather than self-censoring to preserve harmony. The remaining options do not belong: B worsens groupthink by letting the most senior person anchor the discussion and discourage challenge, C isolates the team from external perspectives that break insular thinking, and D pressures the team toward immediate unanimity, which is precisely the symptom groupthink produces.

Exam trap

PMI-ACP often tests the misconception that strong leadership means the senior person should lead discussions or that consensus must be reached quickly — both of which actually worsen groupthink.

Full explanation →

145

MCQhard

A team is struggling to keep their backlog refined. What is a sign of poor backlog refinement?

A.The team finishes all stories in the sprint.

B.The backlog is sorted by priority.

C.The product owner is involved in refinement.

D.The team frequently asks for clarification during the sprint.

AnswerD

Frequent mid-sprint clarification requests signal that stories lacked sufficient detail, acceptance criteria, or shared understanding when pulled. Effective refinement produces ready, unambiguous items, so recurring questions during the sprint indicate the backlog is not being adequately prepared ahead of time.

Why this answer

Frequent mid-sprint clarification requests signal that stories were not sufficiently refined—lacking clear acceptance criteria, dependencies, or shared understanding—before entering the sprint. Effective backlog refinement (grooming) ensures the team understands the 'what' and 'why' of upcoming stories, typically through the Definition of Ready. When the team constantly interrupts the PO during the sprint, it indicates refinement was superficial or skipped.

Exam trap

The trap is selecting an obviously positive-sounding option (A, B, or C) as the 'sign of poor refinement' because the question asks for a negative indicator—candidates must recognize that the correct answer describes a dysfunction, not a best practice.

How to eliminate wrong answers

Option A is wrong because finishing all stories in the sprint is a positive outcome and a sign of good planning and refinement, not a problem. Option B is wrong because a priority-sorted backlog is a best practice and evidence of healthy refinement. Option C is wrong because PO involvement in refinement is essential and expected, not a sign of poor refinement.

Full explanation →

146

MCQmedium

A team member is consistently late to the daily stand-up, disrupting the meeting. How do you handle this?

A.Issue a formal warning to the team member.

B.Encourage the team to discuss the impact of lateness on their collaboration during a retrospective.

C.Change the stand-up time to suit that member's schedule.

D.Stop the stand-up whenever they are late.

AnswerB

Retrospectives let the team own collaboration norms, satisfying the PMI-ACP preference for self-organising teams. Rather than the Scrum Master imposing a fix, the team surfaces how lateness harms stand-up value and agrees its own working agreement, addressing the disruptive behaviour at its root.

Why this answer

Agile favors team-level, self-correcting conversations over managerial discipline. Raising the issue in a retrospective lets the team discuss how lateness affects collaboration, stand-up effectiveness, and mutual respect, and lets them own the solution. This aligns with the principle of self-organizing teams and continuous improvement.

Exam trap

The trap is choosing a directive or punitive action (warning, stopping the meeting) when the agile-correct answer is to let the team address the behavior through inspection and adaptation.

How to eliminate wrong answers

Option A is wrong because a formal warning is a command-and-control HR action that damages psychological safety and bypasses the team's ability to self-manage. Option C is wrong because changing the stand-up time to accommodate one person's schedule puts individual convenience above the team's agreed cadence and may disrupt others. Option D is wrong because stopping the stand-up whenever someone is late punishes the whole team, wastes the meeting's purpose, and avoids addressing the root cause.

Full explanation →

147

Multi-Selecthard

Which TWO of the following are effective ways to handle 'change'?

Select 2 answers

A.Communicate the change impact to stakeholders transparently

B.Assess the impact on the current iteration

C.Always say yes to every change requested

D.Implement the change silently without telling the team

E.Reject all changes to protect the original plan

AnswersA, B

Transparent communication of change impact lets stakeholders adjust plans and priorities early, directly satisfying the agile principle of embracing change. Concealing impact delays feedback and erodes trust, so openly sharing consequences keeps the team responsive rather than defensive.

Why this answer

Option A is correct because transparently communicating the change impact to stakeholders ensures everyone understands the consequences, maintains trust, and allows informed decisions about priorities and trade-offs. Option B is correct because assessing the impact on the current iteration determines whether the change can be absorbed without jeopardizing the sprint goal or requires re-planning, which is essential for effective change management. Option C is incorrect because accepting every change unconditionally leads to scope creep, destabilizes the iteration, and undermines planning discipline.

Option D is incorrect because implementing changes silently without informing the team creates misalignment, hidden work, and risks quality and delivery. Option E is incorrect because rejecting all changes ignores legitimate feedback and market shifts, making the process rigid and unresponsive.

Exam trap

PMI-ACP often tests the misconception that Agile means accepting all changes at any time, when in fact Agile change management requires assessing impact and communicating transparently to make informed trade-offs.

Full explanation →

148

MCQhard

An organization is transitioning to agile but struggles with siloed teams. Which approach best optimizes the end-to-end flow of delivery?

A.Standardize all software tools across the organization.

B.Reorganize into cross-functional teams aligned to value streams.

C.Implement a waterfall project plan to force coordination.

D.Increase the number of status reporting meetings.

AnswerB

Cross-functional teams aligned to value streams own a complete slice of delivery, removing handoffs and queueing between silos. This directly optimises end-to-end flow because dependencies and wait states shrink, letting work move continuously from idea to customer rather than pausing at departmental boundaries.

Why this answer

Reorganizing into cross-functional teams aligned to value streams optimizes end-to-end flow by breaking down silos and ensuring that all skills needed to deliver value are within the team. This reduces handoffs and delays, enabling faster delivery and better collaboration.

Exam trap

PMI-ACP often tests the misconception that tools or meetings can solve silo issues, but the core solution is structural reorganization around value streams.

How to eliminate wrong answers

Option A is wrong because standardizing tools does not address organizational silos or improve flow; it may even create resistance. Option C is wrong because implementing a waterfall plan contradicts agile principles and does not optimize flow in an agile transition. Option D is wrong because increasing status meetings adds overhead without improving delivery flow; it may even slow down work.

Full explanation →

149

MCQmedium

A stakeholder keeps asking for a detailed project plan for the next six months. How do you respond?

A.Ask them to provide their own plan.

B.Explain that Agile planning is iterative and focus on the upcoming release goals.

C.Tell them to wait for the final product.

D.Create a detailed plan to satisfy them.

AnswerB

Agile planning is iterative and rolling-wave, so a fixed six-month plan contradicts empirical delivery. Explaining this and focusing on upcoming release goals satisfies the stakeholder's need for visibility while preserving the team's ability to adapt scope each iteration.

Why this answer

Agile planning is iterative and emergent; detailed six-month plans contradict the empirical nature of Scrum and Kanban. The correct response is to educate the stakeholder on rolling-wave planning, focusing on release goals and near-term iterations while acknowledging that long-term detail will be refined as knowledge grows. This maintains transparency and manages expectations without reverting to predictive planning.

Exam trap

The trap is choosing the accommodating answer (D) because it seems to satisfy the stakeholder, but PMI-ACP consistently rewards Agile-correct behavior (educating on iterative planning) over people-pleasing that violates core principles.

How to eliminate wrong answers

Option A is wrong because deflecting the request back to the stakeholder is unprofessional and fails to address their legitimate need for visibility. Option C is wrong because telling them to wait for the final product is dismissive and ignores the stakeholder's need for planning information. Option D is wrong because creating a detailed six-month plan violates Agile principles, creates false precision, and sets up the team for failure when reality diverges from the plan.

Full explanation →

150

Multi-Selecteasy

Which THREE items are typically included in a user story?

Select 3 answers

A.Business value/benefit.

B.User role.

C.Complete database schema.

D.Desired functionality.

E.The full source code of the feature.

AnswersA, B, D

Business value states the benefit a story delivers, letting the team prioritise by customer impact rather than technical effort. It satisfies the stem's requirement for a typical user story component, alongside the role and goal. This makes it a standard element in PMI-ACP story formatting.

Why this answer

A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, so it typically includes the user role (option B), which identifies who wants the functionality (e.g., 'As a [role]'). It also includes the desired functionality (option D), which states what the user wants to accomplish (e.g., 'I want [feature]'), and the business value/benefit (option A), which explains why the feature matters (e.g., 'so that [benefit]'). These three elements form the classic 'As a <role>, I want <functionality>, so that <benefit>' template.

Options C and E are not part of a user story: a complete database schema is a technical design artifact, and full source code is an implementation detail, both of which are far too detailed and belong to later development phases, not to the user story itself.

Exam trap

PMI-ACP often tests the distinction between user stories and technical specifications, so candidates may mistakenly select database schema or source code as part of a user story, confusing requirements with design artifacts.

Full explanation →

PMI Agile Certified Practitioner (PMI-ACP), 2024-revamped exam outline (PMI-ACP) (PMI-ACP) — Questions 76–150