PMI Agile Certified Practitioner (PMI-ACP), 2024-revamped exam outline (PMI-ACP) PMI-ACP Questions 151–225 | Page 3/4

151

MCQmedium

A Scrum team has been delivering increments every two weeks, but stakeholders report that the features released do not solve their actual business problems. The team consistently meets its sprint commitments and passes all acceptance tests. As the agile practitioner, what should you do FIRST to address this gap?

A.Review and refine the Definition of Done to include business outcome criteria.

B.Increase the frequency of sprint reviews so stakeholders can provide more feedback on each increment.

C.Facilitate a session with stakeholders to clarify and validate the desired business outcomes, then adjust the product backlog accordingly.

D.Ask the team to add more detailed acceptance criteria to each user story.

AnswerC

The gap stems from building the wrong thing, not from poor execution. By bringing stakeholders together to articulate the outcomes they need, the team can re-align the backlog to deliver value rather than output. This directly addresses the root cause and ensures future increments are measured against business results, not just acceptance tests.

Why this answer

The team is delivering output efficiently but not achieving meaningful outcomes. The first step is to engage stakeholders to define and validate the business outcomes they seek, then realign the backlog to deliver those outcomes. This addresses the root cause before changing quality gates, review cadence, or acceptance criteria, which would not resolve the underlying misalignment.

Exam trap

The trap here is assuming that meeting sprint commitments and passing acceptance tests means the team is delivering value, when in fact the gap is about outcome alignment, not execution quality.

Full explanation →

152

MCQhard

Your team has high technical skill but lacks collaboration, with members working in silos. Which technique is most effective to foster a collaborative culture?

A.Set up a shared document repository for everyone to read.

B.Implement individual performance bonuses for the fastest developers.

C.Introduce mob programming sessions for complex stories.

D.Require daily status reports from every developer.

AnswerC

Mob programming forces the whole team onto one keyboard, one screen and one problem, so knowledge and decisions are shared continuously rather than hoarded in silos. This directly attacks the collaboration gap, which technical skill alone cannot fix.

Why this answer

Mob programming is a collaborative technique where the entire team works together on the same code at the same time, often with one driver and others navigating. This forces communication, knowledge sharing, and collective ownership, which directly breaks down silos and fosters collaboration. It is especially effective for complex stories where diverse perspectives are needed.

Exam trap

The trap is choosing options that seem like they improve communication (e.g., shared documents, status reports) but are actually one-way or monitoring tools that do not foster true collaboration; the exam expects you to recognize that active, synchronous collaboration techniques like mob programming are most effective.

How to eliminate wrong answers

Option A is wrong because a shared document repository is a passive tool that does not actively promote collaboration; it may even reinforce silos if team members continue to work independently. Option B is wrong because individual performance bonuses for the fastest developers incentivize competition rather than collaboration, which can worsen silos. Option D is wrong because requiring daily status reports is a command-and-control practice that does not build trust or collaboration; it focuses on reporting rather than working together.

Full explanation →

153

MCQmedium

A user story lacks specific acceptance criteria. What is the risk to the development team?

A.The team will not know when the story meets requirements.

B.The sprint will end earlier than expected.

C.The velocity will artificially increase.

D.The story will be too small to estimate.

AnswerA

Without acceptance criteria, the team cannot verify completion, so the story's definition of done stays ambiguous. This directly satisfies the stem's constraint: absent testable conditions, developers cannot determine whether the increment meets the product owner's requirements, risking rework, scope creep and disputed sign-off during the iteration review.

Why this answer

Acceptance criteria define the conditions a story must satisfy to be considered done, so without them the team has no objective way to know when the work is complete or whether it meets the user's needs. This ambiguity leads to rework, scope disputes, and stories that pass code review but fail acceptance because 'done' was never defined.

Exam trap

The trap is picking an answer about velocity or sprint duration — PMI-ACP wants candidates to recognize that acceptance criteria are about defining 'done' and preventing rework, not about estimation or sprint mechanics.

How to eliminate wrong answers

Option B is wrong because missing acceptance criteria don't shorten a sprint — they typically extend it through rework and clarification cycles, not truncate it. Option C is wrong because velocity doesn't artificially increase from missing criteria; if anything, it becomes unreliable because 'done' is undefined and stories may be counted as complete prematurely. Option D is wrong because acceptance criteria are about defining completion, not about story size — a story can be small and still lack clear criteria, and size is estimated separately using story points or similar techniques.

Full explanation →

154

MCQeasy

Which persona is primarily responsible for ensuring the product backlog reflects the needs of the stakeholders and customers?

A.The Project Sponsor.

B.The Scrum Master.

C.The Product Owner.

D.The Lead Developer.

AnswerC

The Product Owner owns and orders the product backlog, translating stakeholder and customer needs into prioritised items the team delivers. This makes that persona primarily accountable for ensuring the backlog reflects those needs, as the stem requires.

Why this answer

The Product Owner is the single persona accountable for maximizing product value and ensuring the product backlog reflects stakeholder and customer needs. In Scrum and agile practice, the PO owns backlog content, ordering, and refinement. This role is explicitly defined in the Scrum Guide and PMI-ACP materials as the voice of the customer.

Exam trap

PMI-ACP often tests role confusion, tempting candidates to assign backlog ownership to the Scrum Master or Sponsor instead of the Product Owner.

How to eliminate wrong answers

Option A is wrong because the Project Sponsor provides funding and high-level support but does not own or shape the product backlog. Option B is wrong because the Scrum Master is a servant leader who facilitates process and removes impediments, not the owner of backlog content. Option D is wrong because the Lead Developer contributes technical input but does not have accountability for representing stakeholder and customer needs in the backlog.

Full explanation →

155

MCQmedium

During a sprint planning session, the team realizes a user story is too large to complete in one sprint. What is the most effective approach to handle this?

A.Decompose the story into smaller, independently deliverable user stories.

B.Mark the story as blocked and move to the next sprint.

C.Extend the sprint duration to accommodate the story size.

D.Ask the developers to work overtime to finish it.

AnswerA

Splitting the oversized story into smaller, independently deliverable slices lets the team finish work within a single sprint, satisfying the sprint timebox constraint. Each slice can be estimated, prioritised and accepted separately, preserving incremental value delivery rather than carrying an incomplete story across sprints.

Why this answer

Decomposing the story into smaller, independently deliverable user stories is correct because it allows the team to complete valuable increments within the sprint, maintains flow, and adheres to the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). This approach enables continuous delivery and reduces batch size, which is a core Agile principle.

Exam trap

PMI-ACP often tests the misconception that large stories should be deferred or that overtime is acceptable; the correct answer is almost always to split the story into smaller, valuable increments.

How to eliminate wrong answers

Option B is wrong because marking the story as blocked and moving it to the next sprint delays value delivery and ignores the opportunity to split the work into manageable pieces. Option C is wrong because extending the sprint duration violates the timebox principle and disrupts cadence and predictability. Option D is wrong because asking developers to work overtime is unsustainable, reduces quality, and contradicts Agile's emphasis on sustainable pace.

Full explanation →

156

MCQmedium

A product team is six sprints into a new product. The Product Owner has been ordering the product backlog strictly by business value, but the team keeps discovering late that some high-value features are technically infeasible. What should the Product Owner do to improve the ordering of the product backlog?

A.Move all technically complex items to the bottom of the backlog permanently so the team only works on simple, low-risk features.

B.Ask the team to stop raising feasibility concerns and commit to the highest-value items first, since the Product Owner owns backlog ordering.

C.Include the team's technical feasibility assessment and effort estimates when ordering the backlog, balancing value against risk and cost of delay.

D.Have the team create a separate technical backlog that the Product Owner is not allowed to see or prioritize.

AnswerC

Ordering the product backlog is a Product Owner accountability, but it should not be done on business value alone. Incorporating the team's technical feasibility input and relative effort estimates lets the Product Owner weigh value against risk and cost of delay, so high-value but infeasible items are surfaced early rather than discovered late in a sprint.

Why this answer

Product backlog ordering is a Product Owner accountability, but effective ordering requires collaboration with the team that provides feasibility and effort information. By combining business value with technical risk and cost of delay, the Product Owner can sequence items so that uncertain or infeasible high-value features are explored early. This reduces late surprises and keeps the backlog a living, transparent artifact that reflects both value and technical reality.

Exam trap

The trap here is assuming that because the Product Owner owns backlog ordering, value alone should drive the sequence and the team's technical input is optional.

Full explanation →

157

MCQmedium

A new developer is struggling to adopt the team's pairing practices. What is the most appropriate action?

A.Report the developer to HR.

B.Force the developer to pair against their will.

C.Ask them to work alone until they are more comfortable.

D.Coach the developer on the benefits of knowledge sharing.

AnswerD

Coaching directly addresses the developer's difficulty adopting pairing by building understanding of knowledge sharing's value, satisfying the PMI-ACP servant-leadership stance. Unlike mandating or reassigning, coaching targets the underlying reluctance rather than the symptom, fostering voluntary buy-in and sustainable team collaboration.

Why this answer

In Agile, the Scrum Master or Agile coach serves the team by removing impediments and fostering collaboration, not by escalating or coercing. Coaching the developer on the benefits of knowledge sharing addresses the root cause—resistance often stems from misunderstanding or lack of psychological safety—and aligns with the servant-leadership principle. Pairing is a voluntary, collaborative practice; the coach's role is to help the developer see its value, not to mandate it.

Exam trap

PMI-ACP often tests the distinction between coaching/mentoring (the Agile-appropriate response) and command-and-control or punitive actions (HR, forcing), which are almost always wrong in Agile scenarios.

How to eliminate wrong answers

Option A is wrong because reporting the developer to HR is a punitive escalation that destroys trust and is inappropriate for a skill-adoption issue, not a policy violation. Option B is wrong because forcing pairing violates the voluntary nature of Agile practices and psychological safety, likely increasing resistance. Option C is wrong because isolating the developer until they are 'comfortable' avoids the problem, prevents knowledge transfer, and allows the anti-pattern to persist.

Full explanation →

158

MCQmedium

A team has been consistently delivering high-quality software, but stakeholders complain that the features delivered are not the most valuable for the current market. What should the team do to align better with organizational priorities?

A.Ignore stakeholder feedback and continue working on the current roadmap.

B.Increase the frequency of deployments to deliver more features faster.

C.Work with the Product Owner to re-evaluate the product backlog against the current business value and ROI criteria.

D.Implement a new automated testing suite to improve quality.

E.Request a larger budget from management to cover more features.

AnswerC

Re-evaluating the backlog with the Product Owner against current business value and ROI criteria reorders work by present market worth, not historical momentum. This directly corrects the mismatch between delivered features and organisational priorities, satisfying the stem's alignment constraint.

Why this answer

When stakeholders say the delivered features are not the most valuable, the team should work with the Product Owner to re-evaluate the product backlog against current business value and ROI criteria. This ensures the team is building the right thing, not just building things right. The Product Owner owns backlog prioritization, so collaboration is essential.

Exam trap

PMI-ACP often tests the misconception that delivering more features faster or improving quality solves a value-alignment problem, when the real fix is re-prioritizing the backlog with the Product Owner based on business value.

How to eliminate wrong answers

Option A is wrong because ignoring stakeholder feedback perpetuates the misalignment and violates Agile's emphasis on customer collaboration and responding to change. Option B is wrong because increasing deployment frequency delivers more features faster but does not address whether those features are the most valuable — it accelerates the wrong work. Option D is wrong because improving quality via automated testing does not fix a value/prioritization problem; it addresses a different concern.

Option E is wrong because requesting more budget to cover more features does not re-prioritize based on value and may waste resources on low-value work.

Full explanation →

159

MCQeasy

What is the importance of 'transparency' in Agile?

A.To satisfy auditors.

B.To make the team work harder.

C.To enable empirical process control.

D.So everyone knows who to blame.

AnswerC

Transparency makes the process, progress and impediments visible to everyone, giving inspectable facts rather than assumptions. This visibility is what allows decisions to be based on observed reality, enabling empirical process control through the inspect-and-adapt cycle.

Why this answer

Transparency in Agile enables empirical process control — the ability to inspect and adapt based on accurate, visible information. Without transparency, inspections are misleading and adaptations are ineffective, undermining the three pillars of Scrum (transparency, inspection, adaptation).

Exam trap

PMI-ACP often tests the purpose of transparency as enabling empirical process control, so the trap is selecting a superficial or punitive rationale (auditors, harder work, blame) instead of the inspect-and-adapt foundation.

How to eliminate wrong answers

Option A is wrong because satisfying auditors is a compliance byproduct, not the purpose of transparency; Agile transparency is about enabling informed decisions, not external reporting. Option B is wrong because making the team work harder is a productivity goal, not the reason for transparency, and transparency often reveals the need to work smarter, not harder. Option D is wrong because transparency is not about assigning blame; it fosters shared accountability and learning, and blame cultures destroy psychological safety.

Full explanation →

160

MCQeasy

What is the primary purpose of a sprint review?

A.To discuss team conflicts.

B.To calculate velocity.

C.To inspect the product and adapt the backlog based on stakeholder feedback.

D.To plan the next sprint.

AnswerC

The sprint review inspects the completed increment with stakeholders, then adapts the product backlog based on their feedback. This satisfies the empirical inspect-and-adapt requirement at the product level, distinct from the retrospective's focus on process.

Why this answer

The sprint review is an empirical inspection-and-adaptation event held at the end of the sprint where the Scrum Team and stakeholders examine the Increment and collaborate on what to do next. Its core output is an adapted Product Backlog informed by stakeholder feedback and changing market conditions. It is not a status report or a planning session — it is a working session to validate the product direction.

Exam trap

PMI-ACP often tests the distinction between the sprint review (product inspection and backlog adaptation) and the sprint retrospective (process and team improvement), causing candidates to confuse the two events.

How to eliminate wrong answers

Option A is wrong because team conflicts and interpersonal dynamics are addressed in retrospectives or dedicated coaching sessions, not in the sprint review, which focuses on the product Increment. Option B is wrong because velocity is a planning metric calculated from completed work over time, typically reviewed during sprint planning or retrospectives, not the purpose of the review. Option D is wrong because planning the next sprint is the explicit purpose of sprint planning, a separate event that follows the review and retrospective.

Full explanation →

161

MCQhard

A team is working on a legacy product. How should the Product Owner balance new feature requests with maintenance?

A.Devote 100% of capacity to new features.

B.Allocate a fixed percentage of capacity to maintenance and technical debt.

C.Only perform maintenance during the weekends.

D.Only prioritize maintenance when the system fails.

AnswerB

Allocating a fixed percentage of capacity to maintenance and technical debt ensures the legacy product remains stable while new features progress. This directly satisfies the constraint of balancing both demands sustainably, preventing technical debt from overwhelming future delivery. The Product Owner reserves capacity each iteration, making maintenance a predictable, ongoing commitment rather than a reactive afterthought.

Why this answer

On a legacy product, the Product Owner should explicitly reserve a portion of each iteration's capacity for maintenance and technical debt so the system remains stable and evolvable while new features are delivered. This is a deliberate, transparent trade-off rather than an all-or-nothing choice. It reflects the agile principle of sustainable pace and the reality that technical debt compounds if ignored.

Exam trap

PMI-ACP often tests the false dichotomy that a PO must choose between features and maintenance; the trap is selecting an extreme option (100% features, weekends only, or fix-on-failure) instead of the balanced, planned capacity allocation that agile economics recommends.

How to eliminate wrong answers

Option A is wrong because devoting 100% of capacity to new features starves maintenance, causing technical debt to accumulate until the legacy system becomes unstable or unmaintainable. Option C is wrong because restricting maintenance to weekends violates sustainable pace, creates burnout, and treats maintenance as an afterthought rather than planned work. Option D is wrong because only reacting when the system fails is purely reactive firefighting, which is far more costly and risky than proactively allocating capacity to known maintenance needs.

Full explanation →

162

Multi-Selecteasy

Which THREE of the following are examples of servant leadership?

Select 3 answers

A.Coaching team members to reach their full potential

B.Taking all the credit for the team's successes

C.Removing obstacles that hinder the team's progress

D.Directing the team on exactly which tasks to do

E.Modeling the values and behaviors you expect from the team

AnswersA, C, E

Coaching team members to reach their full potential embodies servant leadership by prioritising followers' growth over the leader's authority, satisfying the stem's requirement for a servant leadership example. The leader removes impediments and develops people, rather than directing tasks, which aligns with the agile principle of enabling self-organising teams.

Why this answer

Servant leadership focuses on putting the needs of the team first and helping others grow, so option A is correct because coaching team members to reach their full potential is a core servant-leadership behavior that develops people rather than commanding them. Option C is correct because removing obstacles that hinder the team's progress is a classic servant-leadership practice of clearing the path so the team can succeed. Option E is correct because modeling the values and behaviors you expect from the team demonstrates servant leadership through leading by example and setting a consistent ethical standard.

Option B is not correct because taking all the credit for the team's successes is self-serving and the opposite of servant leadership, which shares credit and elevates others. Option D is not correct because directing the team on exactly which tasks to do is autocratic, task-centered leadership rather than the empowering, supportive approach of servant leadership.

Exam trap

PMI-ACP often tests the misconception that servant leadership means being passive or letting the team do whatever they want — in reality it is an active, supportive role that includes coaching, obstacle removal, and modeling values.

Full explanation →

163

MCQhard

A product team is using a Kanban board to manage a continuous flow of feature requests. The Product Owner wants to limit work in progress (WIP) to improve cycle time but is unsure which column should have the strictest WIP limit. The team's workflow is: Backlog -> Analysis -> Development -> Testing -> Done. Where should the strictest WIP limit typically be applied, and why?

A.Backlog, because too many items waiting creates unrealistic expectations.

B.Testing, because it is often the bottleneck where work accumulates and limits flow.

C.Development, because it is usually the longest and most resource-intensive stage.

D.Done, because completed items should be removed quickly to free capacity.

AnswerB

This is correct because WIP limits should be strictest at the bottleneck to prevent excessive queue buildup and improve flow. In many software teams, Testing becomes the constraint due to specialized skills or environment constraints. By capping Testing WIP, the team exposes the bottleneck, encourages swarming, and reduces cycle time. The limit is not arbitrary but based on observed flow.

Why this answer

In Kanban, WIP limits are most effective when applied to the bottleneck to prevent queue buildup and improve flow. Testing is frequently the bottleneck in software teams due to environment setup, specialized testers, or rework. A strict WIP limit there forces the team to swarm on testing, reduces multitasking, and shortens cycle time.

The correct answer reflects the flow-based principle of managing the constraint.

Exam trap

The trap here is assuming a fixed stage always needs the strictest limit, rather than identifying the actual bottleneck through flow metrics.

Full explanation →

164

MCQmedium

A team is consistently missing sprint goals because they over-commit. What is the most Agile-aligned response?

A.Stop doing retrospectives to save time for coding.

B.Assign tasks to members by seniority to ensure speed.

C.Increase the sprint length to provide more time.

D.Use historical velocity to guide future capacity planning.

AnswerD

Historical velocity provides an empirical, team-derived baseline for how much work fits a sprint, replacing optimistic guesswork with data. This directly addresses the over-commitment constraint while preserving Agile self-management, unlike imposing external estimates or extending sprint length.

Why this answer

The most Agile-aligned response to over-commitment is to use empirical data—specifically historical velocity—to forecast capacity and adjust the amount of work pulled into the sprint. Velocity provides a reliable, team-driven baseline for how much backlog can be completed in a sprint, enabling more accurate commitment. This supports the Agile principles of empirical process control and continuous improvement.

Exam trap

PMI-ACP often tests the confusion between velocity as a planning tool versus a performance metric; candidates may incorrectly think increasing sprint length or assigning by seniority solves over-commitment, but Agile emphasizes empirical capacity planning.

How to eliminate wrong answers

Option A is wrong because stopping retrospectives removes the team's primary mechanism for inspecting and adapting their process, which is essential for fixing the over-commitment root cause. Option B is wrong because assigning tasks by seniority undermines self-organization and ignores that velocity is a team-level metric, not an individual one. Option C is wrong because increasing sprint length merely masks the over-commitment problem, delays feedback, and does not address the team's capacity planning accuracy.

Full explanation →

165

MCQmedium

How do you handle a scenario where two teams have a dependency that is slowing both of them down?

A.Merge the two teams into one large team.

B.Assign a single manager to oversee both teams.

C.Facilitate a joint session for the two teams to map the dependency and negotiate a timeline for resolution.

D.Tell the teams to stop relying on each other.

AnswerC

A facilitated joint session lets both teams visualise the dependency, agree ownership and negotiate a resolution timeline, addressing the shared slowdown at its source. This collaborative approach satisfies the stem's need to unblock two interdependent teams.

Why this answer

When two teams have a dependency that slows both down, the agile approach is to make the dependency visible and let the teams jointly solve it. Facilitating a joint session allows both teams to map the dependency, understand each other's constraints, and negotiate a timeline for resolution. This preserves team autonomy while removing the impediment collaboratively, which is the core of servant-leadership in agile.

Exam trap

PMI-ACP often tests the instinct to escalate or restructure (merge teams, add a manager) when the agile-correct answer is to facilitate collaboration and let the teams self-organize around the dependency.

How to eliminate wrong answers

Option A is wrong because merging teams destroys the existing team structure and autonomy, and it does not address the underlying dependency — it just hides it inside a larger team. Option B is wrong because assigning a single manager adds command-and-control overhead without resolving the technical or process dependency, and it contradicts agile self-organization. Option D is wrong because telling teams to stop relying on each other ignores the real dependency and is not actionable — dependencies must be managed, not wished away.

Full explanation →

166

MCQhard

During a sprint, a developer tells the Scrum Master that a critical integration with a third-party API is failing intermittently, causing unpredictable delays. The team has already committed to delivering the feature this sprint. What is the MOST appropriate action for the agile practitioner?

A.Advise the team to ignore the intermittent failure and continue with other sprint work until the API stabilizes.

B.Help the team make the impediment visible, assess its impact, and facilitate a decision on whether to adjust scope or seek expert help.

C.Instruct the developer to work overtime to resolve the integration issue before the sprint ends.

D.Immediately escalate to senior management to request additional resources for the integration.

AnswerB

The practitioner's role is to remove impediments and enable the team to self-organize. By making the issue transparent and guiding the team through impact assessment, the team can decide whether to descope, spike, or escalate. This preserves commitment realism and sustainable pace while addressing the technical problem collaboratively.

Why this answer

The agile practitioner should facilitate transparency and team self-organization. Making the impediment visible and helping the team evaluate its impact allows them to decide whether to adjust scope, run a spike, or seek expert assistance. This approach respects the team's autonomy and maintains sustainable pace, rather than imposing overtime, escalating prematurely, or ignoring the problem.

Exam trap

The trap here is thinking the practitioner should immediately solve the technical problem or escalate, when the correct agile response is to make the impediment visible and let the team decide how to respond.

Full explanation →

167

Multi-Selecteasy

Which TWO roles are fundamental to the success of an agile team?

Select 2 answers

A.External Auditor.

B.Scrum Master or Team Facilitator.

C.Marketing Manager.

D.Product Owner.

E.Chief Financial Officer.

AnswersB, D

The Scrum Master serves the team by removing impediments, coaching agile practises and shielding it from external disruption, directly enabling self-organisation. This facilitation role is fundamental because without it the team's process discipline and continuous improvement stall, undermining the collaborative cadence the scenario demands.

Why this answer

Option B (Scrum Master or Team Facilitator) is correct because this role is fundamental to an agile team: the Scrum Master serves the team by removing impediments, facilitating Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), coaching the team in agile practices, and shielding it from external distractions, which directly enables self-organization and continuous improvement. Option D (Product Owner) is correct because the Product Owner is accountable for maximizing the value delivered by the team, owning and ordering the Product Backlog, defining and refining backlog items, and acting as the single point of contact for stakeholder requirements and priorities, which keeps the team building the right thing. Option A (External Auditor) is not a core agile team role; auditing is a governance/compliance function performed outside the team and is not required for agile team success.

Option C (Marketing Manager) is a business function that may interact with the Product Owner as a stakeholder but is not a fundamental agile team role. Option E (Chief Financial Officer) is an executive finance role concerned with budgeting and financial control, not a role defined within an agile team's structure.

Exam trap

The trap is confusing stakeholders (Marketing, Finance, Audit) with core Agile team roles — candidates may pick a business function that seems important but is not part of the Scrum accountability structure.

Full explanation →

168

MCQhard

The organization is pressuring the team to commit to a date for a major release that the team feels is impossible. What is your role?

A.Help the team explain the trade-offs (scope, quality, or time) based on their current velocity to the stakeholders.

B.Tell management that the team will work hard to make it happen.

C.Tell the team to stop providing estimates to management.

D.Accept the date to avoid conflict with management.

AnswerA

Velocity data makes the constraint tangible: the team cannot add scope without extending time or reducing quality. Presenting these trade-offs to stakeholders shifts the conversation from an impossible date to an informed scope decision, satisfying the stem's demand for a realistic release commitment.

Why this answer

The Scrum Master/Agile coach's role is to help the team and stakeholders make trade-offs transparent using empirical data such as velocity and historical throughput. Rather than accepting an impossible date or hiding behind optimism, you facilitate a conversation where scope, quality, and time are explicitly balanced. This preserves transparency and lets the business make an informed decision.

Exam trap

PMI-ACP often tests the instinct to please management — candidates pick 'accept the date' or 'work harder,' but Agile favors transparency and data-driven trade-off conversations over heroics.

How to eliminate wrong answers

Option B is wrong because promising to 'work hard' without data is a commitment the team cannot support — it violates transparency and sets up failure. Option C is wrong because withholding estimates from management destroys stakeholder trust and violates the principle of openness; estimates are a communication tool, not a weapon. Option D is wrong because accepting an impossible date to avoid conflict is a failure of the servant-leader role — it sacrifices team sustainability and product quality for short-term harmony.

Full explanation →

169

Multi-Selecteasy

Which TWO of the following behaviors best demonstrate the Agile mindset regarding 'Customer Collaboration over Contract Negotiation'?

Select 2 answers

A.Inviting customers to provide feedback during sprint reviews.

B.Treating the customer as a partner to solve problems together.

C.Outsourcing all communication to the legal department.

D.Strictly adhering to the original contract to avoid extra work.

E.Limiting customer interaction to prevent scope creep.

AnswersA, B

Sprint reviews create a recurring feedback loop, letting the customer steer the product backlog directly rather than fixing scope through upfront contractual terms. This embodies collaboration over negotiation by making the customer an active participant throughout delivery.

Why this answer

Option A is correct because inviting customers to provide feedback during sprint reviews embodies collaboration: the sprint review is the inspect-and-adapt event where the team demonstrates the increment and works with the customer to shape the backlog, rather than hiding behind contractual deliverables. Option B is correct because treating the customer as a partner to solve problems together directly reflects the Agile value of collaboration over negotiation—shared ownership of outcomes replaces adversarial bargaining. Option C is not correct because outsourcing communication to legal makes the relationship transactional and contract-centric, the opposite of collaboration.

Option D is not correct because rigidly adhering to the original contract to avoid extra work prioritizes the contract over responding to customer needs. Option E is not correct because limiting customer interaction to prevent scope creep reduces collaboration and treats the customer as an adversary rather than a partner.

Exam trap

PMI-ACP often tests the misconception that 'collaboration over contract negotiation' means contracts are unnecessary, when it actually means collaboration should take precedence while contracts still provide a safety net.

Full explanation →

170

MCQeasy

A team member is consistently negative during meetings. As a leader, what is your first step?

A.Ignore the behavior, as it will resolve itself.

B.Discuss the behavior with them privately to understand the root cause.

C.Call them out during the daily stand-up.

D.Ask the team to vote on whether to keep them in the squad.

AnswerB

Addressing the negativity privately first uncovers the root cause, whether personal stress, unresolved conflict or genuine technical concern. This preserves psychological safety and avoids public confrontation, letting the leader respond to the actual driver rather than merely suppressing the visible behaviour during meetings.

Why this answer

Negativity in meetings is usually a symptom of an underlying issue — unclear priorities, unresolved conflict, burnout, or feeling unheard — so the leader's first step is a private conversation to understand the root cause before taking any corrective action. Addressing it privately preserves the team member's dignity and gives the leader real information rather than reacting to surface behavior.

Exam trap

The trap is choosing a public or punitive response — PMI-ACP consistently rewards the servant-leader move of private, empathetic investigation over public correction or escalation.

How to eliminate wrong answers

Option A is wrong because ignoring the behavior allows it to fester and spread, damaging team morale and psychological safety — negativity rarely resolves itself without intervention. Option C is wrong because calling them out during the daily stand-up is a public shaming that destroys trust, escalates defensiveness, and turns a private issue into a team-wide spectacle. Option D is wrong because asking the team to vote on whether to keep a member is a popularity contest that violates any reasonable HR process and destroys psychological safety for everyone, not just the individual.

Full explanation →

171

MCQmedium

A team's automated test suite passes locally but frequently fails in the continuous integration pipeline, and deployments are being delayed while developers investigate. Which action most directly improves delivery reliability?

A.Reduce the test suite to only the tests that pass reliably in the pipeline.

B.Allow the pipeline to continue past failing tests and report results at the end of the iteration.

C.Make the pipeline environment match the local development environment and treat pipeline failures as stop-the-line events.

D.Require developers to run the full suite manually before every commit and sign off on the pipeline result.

AnswerC

Divergence between local and pipeline environments is the leading cause of this pattern. Aligning them removes the environmental variable, and treating failures as stop-the-line prevents broken builds from accumulating. Together these make the pipeline a trustworthy signal, which is what shortens the delay between commit and deployable increment.

Why this answer

When tests pass locally but fail in continuous integration, the environment is the usual culprit, often along with tests that depend on order or shared state. Aligning the pipeline environment with development and refusing to let a red build stand restores trust in the pipeline and shortens the path from commit to deployable increment.

Exam trap

The trap here is treating a flaky pipeline as a testing problem to be worked around by reducing tests or adding manual gates, rather than as an environment and feedback-loop problem to be fixed.

Full explanation →

172

MCQmedium

During sprint planning, the team discovers they cannot complete a high-priority feature due to a technical blocker. What should the practitioner do?

A.Extend the sprint to accommodate the blocker.

B.Remove the feature from the product backlog entirely.

C.Ignore the blocker and hope the team finishes.

D.Facilitate a discussion to find an alternative or escalate if needed.

AnswerD

A technical blocker preventing a high-priority feature needs the practitioner to facilitate team discussion of alternatives, escalating only if the team cannot resolve it. This keeps ownership with the team while ensuring impediments are surfaced, satisfying the sprint planning constraint.

Why this answer

When a technical blocker prevents completing a high-priority feature, the practitioner should facilitate a discussion to explore alternatives — such as re-scoping, finding a workaround, or bringing in expertise — and escalate if the blocker cannot be resolved within the team. This aligns with agile's emphasis on transparency, collaboration, and servant leadership. The team and Product Owner jointly decide how to adapt the sprint.

Exam trap

PMI-ACP often tests the misconception that blockers justify extending the sprint or dropping work entirely, when the agile response is to facilitate collaboration, adapt scope, and escalate only when necessary.

How to eliminate wrong answers

Option A is wrong because extending the sprint violates the timebox principle; sprints have fixed durations to maintain cadence and predictability, and scope should be adjusted instead. Option B is wrong because removing the feature from the product backlog entirely discards potentially valuable work; it may be deferred or re-prioritized, not deleted. Option C is wrong because ignoring the blocker and hoping for completion is passive and unprofessional, guaranteeing missed commitments and hidden risk.

Full explanation →

173

Multi-Selecteasy

Which THREE behaviors signal that a team is becoming self-organized? (Choose THREE)

Select 3 answers

A.The team feels comfortable asking for help when they are stuck.

B.The team adjusts their own working agreements based on retrospective findings.

C.The team proactively identifies and addresses process blockers.

D.The team only communicates through the Scrum Master.

E.The team waits for management to tell them which tasks to do next.

AnswersA, B, C

Openly asking for help shows the team trusts collective ownership over individual image, a hallmark of self-organisation. This behaviour satisfies the question's signal because members prioritise delivering value over appearing self-sufficient, enabling work to flow without manager intervention.

Why this answer

Option A is correct because self-organizing teams exhibit psychological safety, where members openly admit impediments and ask peers for help rather than hiding problems or escalating everything to a manager. Option B is correct because self-organization includes owning and evolving the team's working agreements; acting on retrospective findings by adjusting their own norms demonstrates autonomy over how they work. Option C is correct because proactively identifying and resolving process blockers shows the team takes initiative for its own workflow instead of waiting for external direction.

Option D is not correct because routing all communication through the Scrum Master creates a bottleneck and dependency, which is the opposite of self-organization. Option E is not correct because waiting for management to assign tasks reflects a command-and-control, directed team rather than a self-managing one.

Exam trap

The trap here is confusing self-organization with independence — candidates may reject 'asking for help' as a sign of dependency, when in agile it actually signals a healthy, self-aware team.

Full explanation →

174

MCQhard

During a retrospective, two senior team members disagree on the technical architecture for a new feature, leading to a standstill. How should you facilitate this?

A.Make the decision yourself to prevent further delay.

B.Ask the product owner to decide the architecture.

C.Vote on the approaches and go with the majority.

D.Suggest a time-boxed experiment to test both approaches and compare outcomes.

AnswerD

A time-boxed experiment converts an opinion-based standstill into empirical comparison: both architectures are tested against agreed criteria, and the team decides on evidence. This satisfies the retrospective constraint by resolving the disagreement without escalation or seniority-based override, preserving team ownership.

Why this answer

In agile coaching, when two senior members reach a technical standstill, the facilitator should avoid imposing a decision and instead enable the team to resolve it empirically. A time-boxed experiment (spike) lets both approaches be tested against real outcomes, turning an opinion-based debate into a data-driven decision. This preserves team ownership and aligns with agile's empirical, inspect-and-adapt mindset.

Exam trap

PMI-ACP often tests the misconception that the agile lead should 'make the call' to unblock the team — in agile, the team owns technical decisions, and the coach facilitates rather than decides.

How to eliminate wrong answers

Option A is wrong because the Scrum Master/agile lead making the technical decision undermines self-organization and takes ownership away from the team. Option B is wrong because the product owner owns the 'what' and 'why' (value, priority), not the 'how' (technical architecture) — delegating architecture to the PO violates role boundaries. Option C is wrong because majority voting on architecture can produce a technically inferior choice and doesn't resolve the underlying disagreement; it's a popularity contest, not an engineering decision.

Full explanation →

175

Multi-Selecthard

Which THREE of the following foster psychological safety?

Select 3 answers

A.Encouraging members to challenge ideas

B.Supporting experimentation and learning

C.Admitting mistakes as a leader

D.Creating a strict hierarchy of authority

E.Publicly blaming those who make errors

AnswersA, B, C

Inviting challenge normalises dissent, so members speak up without fear of retribution. This directly builds the shared belief that raising concerns or contradicting senior voices is safe, which is the core of psychological safety in agile teams.

Why this answer

Option A is correct because encouraging members to challenge ideas signals that dissent and constructive debate are welcome, which is a core behavioral driver of psychological safety in teams. Option B is correct because supporting experimentation and learning reframes failure as a source of information rather than punishment, which reduces interpersonal risk and promotes speaking up. Option C is correct because a leader who openly admits mistakes models vulnerability and fallibility, giving team members permission to do the same without fear of retribution.

Option D is not correct because a strict hierarchy of authority suppresses open communication and increases fear of speaking up, which erodes psychological safety. Option E is not correct because publicly blaming those who make errors punishes candor and risk-taking, directly undermining the trust and safety needed for teams to learn and innovate.

Exam trap

PMI-ACP often tests whether candidates recognize that psychological safety requires flattening hierarchy and removing blame; the trap is choosing answers that sound like 'strong leadership' but actually suppress openness.

Full explanation →

176

MCQmedium

A servant leader notices that team members are hesitant to share mistakes during the retrospective. What is the most effective way to foster psychological safety in this environment?

A.Require team members to submit anonymous reports about other members' performance.

B.Implement a public performance tracking dashboard to identify who makes the most errors.

C.Acknowledge the team's successes and publicly share a personal failure to normalize learning from mistakes.

D.Schedule individual meetings to discipline those who caused the project delays.

AnswerC

Modelling vulnerability by admitting his own mistake signals that error disclosure carries no penalty, which is the mechanism that builds psychological safety. Public acknowledgement of successes alone does not address the fear driving the team's silence during retrospectives.

Why this answer

Psychological safety is built when leaders model vulnerability and reframe mistakes as learning opportunities. Publicly sharing a personal failure while acknowledging successes (C) signals that fallibility is acceptable and that the team will not be punished for candor. This directly addresses the hesitation to speak up in retrospectives by changing the perceived consequences of honesty.

Exam trap

The trap is confusing accountability with punishment, so candidates pick surveillance or discipline options that feel like 'taking action' but actually destroy the psychological safety the question asks to build.

How to eliminate wrong answers

Option A is wrong because anonymous reports about peers create surveillance and distrust, which destroys safety rather than building it. Option B is wrong because a public error dashboard shames individuals and incentivizes hiding mistakes, the opposite of a learning culture. Option D is wrong because disciplining people for delays punishes transparency and guarantees that future problems will be concealed until they become crises.

Full explanation →

177

MCQmedium

A project is failing to deliver value because the features are too large. What is the recommended strategy?

A.Stop the project.

B.Decompose epics into smaller, investable user stories.

C.Hire more testers.

D.Keep the features large to avoid complexity.

AnswerB

Large features delay feedback and obscure value delivery. Splitting epics into smaller, investable user stories shortens the feedback loop, letting the team deliver and validate increments frequently, directly addressing the stem's root cause of oversized features.

Why this answer

When features are too large to deliver value, the recommended agile strategy is to decompose epics into smaller, investable user stories that can be completed and delivered incrementally. Smaller stories enable faster feedback, reduce risk, and allow the team to deliver value continuously rather than in large, infrequent batches.

Exam trap

PMI-ACP often tests the misconception that large features are acceptable if the team works harder or adds resources, when the agile-correct answer is to decompose them into smaller, value-delivering increments.

How to eliminate wrong answers

Option A is wrong because stopping the project is a drastic, premature action that abandons potential value — the problem is feature size, not project viability. Option C is wrong because hiring more testers does not address the root cause (large features); it adds cost without improving delivery flow. Option D is wrong because keeping features large to 'avoid complexity' is the opposite of the recommended approach — large features increase complexity, risk, and delay.

Full explanation →

178

MCQhard

A team is using a WIP (Work In Progress) limit of 3 on their 'Testing' column. A developer moves a fourth item into 'Testing' because the current items are blocked by a third party. What is the most agile way to handle this?

A.Move the blocked items back to the 'Development' column.

B.Stop starting new work and assist the testers or address the block with the third party.

C.Increase the WIP limit to 4 to accommodate the new item.

D.Ask the Product Owner to prioritize the next task for the developer.

E.Allow the fourth item to move into testing to keep developers busy.

AnswerB

Respecting the WIP limit means the fourth item should not enter 'Testing'. Rather than idle, the developer should swarm on the blocked work or resolve the third-party dependency, restoring flow and preventing the bottleneck from worsening.

Why this answer

When a WIP limit is reached and items are blocked, the agile response is to stop starting new work and swarm on the blockage — either helping testers or resolving the third-party dependency. This respects the WIP limit, exposes the impediment, and improves flow rather than hiding the problem.

Exam trap

PMI-ACP often tests whether candidates will relax or bypass WIP limits under pressure, when the agile answer is always to respect the limit and address the impediment.

How to eliminate wrong answers

Option A is wrong because moving blocked items backward does not resolve the blockage and disrupts the workflow; it merely relocates the problem. Option C is wrong because raising the WIP limit to accommodate a new item defeats the purpose of the limit and hides the bottleneck instead of addressing it. Option D is wrong because asking the Product Owner for new work ignores the blocked items and violates the pull principle.

Option E is wrong because allowing a fourth item into Testing to keep developers busy is exactly the behavior WIP limits are designed to prevent.

Full explanation →

179

MCQmedium

A cross-functional team is struggling with siloed behavior. What is the best way to encourage an Agile mindset of shared responsibility?

A.Require team members to work on their specific areas of expertise only.

B.Encourage the team to swarm on blockers and share the responsibility for the Sprint Goal.

C.Compare the individual performance metrics of each team member during the retrospective.

D.Assign specific tasks to individual team members and monitor their progress separately.

AnswerB

Swarming on blockers spreads work across specialisms, dissolving silos and making the Sprint Goal a collective commitment rather than a hand-off. Shared ownership of the goal directly builds the cross-functional, self-organising behaviour the team currently lacks.

Why this answer

To break down silos and encourage shared responsibility, the best approach is to have the team swarm on blockers and collectively own the Sprint Goal. Swarming means multiple team members collaborate on a single item to finish it faster, which promotes knowledge sharing and reduces handoffs. This directly fosters a cross-functional, shared-responsibility mindset.

Exam trap

The trap is selecting options that sound like accountability (individual metrics, task assignment) but actually reinforce silos, whereas Agile emphasizes collective ownership and swarming.

How to eliminate wrong answers

Option A is wrong because restricting members to their expertise reinforces silos and prevents cross-training. Option C is wrong because comparing individual performance metrics in a retrospective undermines team cohesion and encourages competition rather than collaboration. Option D is wrong because assigning tasks to individuals and monitoring them separately promotes individual accountability over collective ownership, which is contrary to Agile team dynamics.

Full explanation →

180

MCQeasy

When writing user stories, which criteria ensure the story is ready for the development team to estimate?

A.The story must be at least 10 pages long.

B.The story must meet the Definition of Ready.

C.The story must be approved by the CEO.

D.The story must be assigned to a specific developer.

AnswerB

The Definition of Ready is the agreed checklist confirming a story is sufficiently refined, estimated and understood before sprint planning. Meeting it signals the team has enough detail to size the work, which is the criterion the question asks for.

Why this answer

The Definition of Ready (DoR) is an agile team's explicit checklist that a user story must satisfy before it can be pulled into a sprint for estimation and development. It typically covers INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable), acceptance criteria being defined, dependencies identified, and the story being small enough to complete in one iteration. Meeting the DoR is the agreed signal that the team has enough shared understanding to size the work reliably.

Exam trap

PMI-ACP often tests the confusion between traditional gatekeeping (management approval, detailed documentation, individual assignment) and agile readiness signals like the Definition of Ready, so candidates who default to command-and-control assumptions pick C or D.

How to eliminate wrong answers

Option A is wrong because user stories are intentionally short, conversational descriptions of value — length is not a readiness criterion, and a 10-page document contradicts the agile principle of 'working software over comprehensive documentation.' Option C is wrong because executive approval is not part of any agile readiness framework; the Product Owner prioritizes the backlog, and the team self-manages estimation, so CEO sign-off would create a bottleneck and violate self-organization. Option D is wrong because assigning a story to a specific developer before estimation undermines collective ownership and team-based estimation; in Scrum and most agile methods, work is pulled by the team, not pre-assigned to individuals.

Full explanation →

181

Multi-Selecthard

Which THREE of the following demonstrate psychological safety?

Select 3 answers

A.Team members always agree with the majority opinion

B.Team members remain silent to keep the peace

C.Team members feel comfortable taking calculated risks

D.Team members speak up even when they disagree with the leader

E.Team members admit mistakes without fear of retribution

AnswersC, D, E

Feeling safe to take calculated risks is a core behavioural marker of psychological safety, satisfying the stem's requirement for demonstrated safety. In Edmondson's framing, it reflects shared belief that interpersonal risk-taking is tolerated, enabling members to propose uncertain ideas or challenge assumptions without fear of humiliation or punishment.

Why this answer

Psychological safety is the shared belief that a team is safe for interpersonal risk-taking, so option C is correct because feeling comfortable taking calculated risks shows members trust that experimentation and potential failure will not be punished. Option D is correct because speaking up against a leader's view demonstrates that dissent is welcomed and that rank does not suppress honest input. Option E is correct because admitting mistakes without fear of retribution is the clearest sign that errors are treated as learning opportunities rather than grounds for blame.

Options A and B do not belong: always agreeing with the majority and staying silent to keep the peace reflect conformity, conflict avoidance, and fear of speaking up, which are the opposite of psychological safety.

Exam trap

PMI-ACP often tests the misconception that psychological safety means being nice or avoiding conflict — in reality, it means creating an environment where candid, sometimes uncomfortable, conversations are welcomed.

Full explanation →

182

MCQhard

A team member is consistently late for meetings. How do you address this?

A.Do nothing.

B.Discuss the impact on the team with them privately.

C.Start the meeting without them every time.

D.Bring it up in the daily stand-up.

AnswerB

Addressing lateness privately lets the team member explain underlying causes without public embarrassment, while making the impact on the team's commitments explicit. This preserves psychological safety and trust, which an agile practitioner prioritises over escalation or group confrontation.

Why this answer

The correct approach is to address the behavior privately with the team member, focusing on the impact their lateness has on the team's collaboration and productivity. This aligns with PMI-ACP principles of servant leadership, emotional intelligence, and direct, respectful communication. By discussing the issue one-on-one, you avoid public embarrassment and create a safe space for the team member to explain any underlying issues, while still holding them accountable.

This approach fosters trust and maintains team morale, which are critical for agile team success.

Exam trap

PMI-ACP often tests the misconception that public accountability (e.g., calling out behavior in a stand-up) is acceptable in agile, when in fact agile values psychological safety and private, respectful conflict resolution.

How to eliminate wrong answers

Option A is wrong because ignoring the behavior allows it to persist, eroding team discipline and setting a precedent that punctuality is unimportant, which undermines agile ceremonies. Option C is wrong because starting without the member may exclude them from critical discussions and decisions, leading to information silos and reduced team cohesion, and it does not address the root cause. Option D is wrong because bringing it up in the daily stand-up publicly shames the individual, violates the principle of addressing conflicts privately, and can damage trust and psychological safety within the team.

Full explanation →

183

MCQeasy

Which of the following is an effective way to prioritize a product backlog based on organizational goals?

A.First come, first served.

B.Random selection.

C.MoSCoW method.

D.Assigning tasks by individual preference.

AnswerC

MoSCoW sorts backlog items into Must, Should, Could and Won't categories, forcing explicit trade-offs against organisational goals. Must-haves map to non-negotiable business objectives, so prioritisation reflects value and constraints rather than arbitrary ordering, satisfying the requirement to align the backlog with organisational goals.

Why this answer

The MoSCoW method (Must have, Should have, Could have, Won't have) is a structured prioritization technique that aligns backlog items with organizational goals by categorizing requirements by business value and necessity. It is explicitly recognized in Agile practice as an effective way to prioritize based on stakeholder and organizational priorities.

Exam trap

PMI-ACP often tests recognition of established prioritization techniques (MoSCoW, WSJF, Kano) versus non-techniques (first-come-first-served, random, personal preference), so the trap is picking an intuitive but value-blind method.

How to eliminate wrong answers

Option A is wrong because first-come, first-served ignores business value and dependencies, leading to a backlog that reflects arrival order rather than organizational goals. Option B is wrong because random selection has no basis in value, risk, or strategy and is not a prioritization technique at all. Option D is wrong because assigning tasks by individual preference prioritizes personal comfort over team and organizational objectives, which contradicts Agile's value-driven delivery.

Full explanation →

184

MCQmedium

Which of the following is an effective technique for eliciting requirements from stakeholders?

A.Building the entire product first and asking for feedback later.

B.Guessing the requirements based on past projects.

C.Waiting for the stakeholders to send an email.

D.Conducting user interviews or focus groups.

AnswerD

User interviews and focus groups elicit requirements directly from stakeholders, capturing needs, expectations, and context that documents alone miss. This satisfies the stem's requirement for an effective elicitation technique by enabling dialogue, clarification, and immediate follow-up questioning.

Why this answer

Conducting user interviews or focus groups is a direct, interactive elicitation technique that draws requirements straight from stakeholders through structured conversation, allowing the analyst to probe, clarify, and uncover latent needs. PMI-ACP and the Agile Manifesto emphasize 'individuals and interactions over processes and tools,' so face-to-face techniques like interviews and focus groups align with agile values. These methods produce rich, high-quality information that can be validated immediately with the stakeholder.

Exam trap

PMI-ACP often tests the distinction between active elicitation techniques (interviews, focus groups, workshops) and passive or deferred approaches (waiting for emails, building first, guessing), so candidates must recognize that agile values proactive collaboration.

How to eliminate wrong answers

Option A is wrong because building the entire product before gathering feedback is the antithesis of iterative development and guarantees expensive rework when requirements are wrong. Option B is wrong because guessing requirements from past projects ignores the current stakeholders' unique context and violates the principle of customer collaboration. Option C is wrong because passively waiting for an email is a push-based, reactive approach that does not actively elicit requirements and often yields incomplete or ambiguous information.

Full explanation →

185

MCQhard

A team is struggling with 'groupthink' during planning. How can you facilitate better decision-making?

A.Tell the team to be more vocal.

B.Use techniques like 'Silent Brainstorming' (e.g., 1-2-4-All) to gather diverse perspectives.

C.Ask the team to vote by a show of hands.

D.Call on each person one by one to give their opinion.

AnswerB

Silent Brainstorming via 1-2-4-All gathers input individually before group discussion, so each member forms independent judgements first. This directly counters groupthink, where conformity pressure suppresses dissent and alternative views. The technique satisfies the stem's need for diverse perspectives during planning by preventing dominant voices from anchoring the team prematurely.

Why this answer

Groupthink occurs when the desire for harmony suppresses dissenting views. Silent Brainstorming techniques like 1-2-4-All gather input independently before discussion, which prevents dominant voices from anchoring the group and surfaces diverse perspectives. Option B directly addresses the root cause of groupthink.

Exam trap

PMI-ACP often tests facilitation techniques by presenting plausible-sounding but structurally weak options — voting or calling on people feels inclusive but actually increases conformity pressure, which is the opposite of what reduces groupthink.

How to eliminate wrong answers

Option A is wrong because telling the team to 'be more vocal' does not change the structural dynamics that cause groupthink — it puts the burden on individuals rather than the facilitator. Option C is wrong because a show-of-hands vote is a public, synchronous act that increases conformity pressure and can amplify groupthink rather than reduce it. Option D is wrong because calling on each person one by one still happens in a group setting where people hear prior answers and may conform; it does not create the independent-thinking space that silent techniques provide.

Full explanation →

186

Multi-Selecthard

Which THREE techniques help minimize context switching?

Select 3 answers

A.Strict WIP limits.

B.Increasing the number of meetings.

C.Focusing on one feature at a time.

D.Scheduling dedicated time for deep work.

E.Assigning multiple tasks to each person.

AnswersA, C, D

Strict WIP limits cap concurrent work per person or column, forcing completion before pulling new items. This directly reduces context switching by preventing the multi-tasking that fragments focus, satisfying the stem's constraint of minimising task-switching overhead across the team.

Why this answer

Strict WIP limits (A) are correct because capping the amount of work in progress forces the team to finish items before starting new ones, reducing the number of parallel tasks that pull attention in different directions and thus cutting context switching. Focusing on one feature at a time (C) is correct because single-piece flow keeps a person's cognitive effort on a single work item, eliminating the reload cost incurred when switching between features. Scheduling dedicated time for deep work (D) is correct because uninterrupted blocks allow sustained concentration on one task, preventing the frequent task-switching caused by fragmented calendars.

Increasing the number of meetings (B) is not correct because more meetings fragment the day and create additional interruptions that increase context switching. Assigning multiple tasks to each person (E) is not correct because it multiplies concurrent work items per individual, which is precisely what raises context-switching overhead.

Exam trap

PMI-ACP often tests the difference between practices that increase multitasking versus those that reduce it; candidates may incorrectly think that assigning multiple tasks or more meetings improves productivity.

Full explanation →

187

Multi-Selecthard

Which THREE metrics should a practitioner focus on to measure end-to-end delivery performance?

Select 3 answers

A.Number of coffee breaks taken.

B.Cycle Time.

C.Throughput.

D.Lead Time.

E.Employee age.

AnswersB, C, D

Measures the time to complete a single unit of work.

Why this answer

Cycle Time (B) is correct because it measures the elapsed time from when work actually starts on an item until it is completed, capturing the efficiency of the delivery process itself. Throughput (C) is correct because it quantifies the number of work items completed per unit of time, directly reflecting the delivery rate of the team or system. Lead Time (D) is correct because it measures the total elapsed time from when a request is made (or an item enters the backlog) until it is delivered to the customer, which is the definitive end-to-end delivery performance metric.

The unmarked options do not belong: the number of coffee breaks (A) is an irrelevant personal habit with no bearing on delivery flow, and employee age (E) is a demographic attribute that has no causal or measurable relationship to end-to-end delivery performance.

Exam trap

PMI-ACP often tests whether candidates can distinguish Lead Time (customer request to delivery, includes wait) from Cycle Time (work start to done) — candidates frequently pick one when both are correct, or confuse Throughput with velocity.

Full explanation →

188

Multi-Selectmedium

Which TWO actions demonstrate servant leadership?

Select 2 answers

A.Protecting the team from external interruptions

B.Removing impediments for the team

C.Assigning tasks to team members

D.Requiring status reports every hour

E.Dictating exactly how tasks should be done

AnswersA, B

Servant leaders shield the team from external distractions so members retain focus on delivering value. This removes a barrier the team cannot control itself, directly demonstrating the servant leadership principle of putting the team's needs first rather than the leader's authority.

Why this answer

Servant leadership in agile/Scrum contexts means the leader's primary role is to serve the team by clearing obstacles and shielding it from distractions so members can self-organize and deliver value. Option A (Protecting the team from external interruptions) is correct because a servant leader acts as a buffer, absorbing outside demands and noise so the team can maintain focus and flow. Option B (Removing impediments for the team) is correct because eliminating blockers is the canonical servant-leader behavior, enabling continuous progress rather than directing the work.

Option C (Assigning tasks to team members) is not servant leadership because self-organizing teams pull work themselves; assignment is a command-and-control practice. Option D (Requiring status reports every hour) is not servant leadership because it imposes controlling, trust-eroding oversight rather than supporting the team. Option E (Dictating exactly how tasks should be done) is not servant leadership because it removes autonomy and micromanages instead of empowering the team.

Exam trap

PMI-ACP often tests the confusion between servant leadership and traditional management—candidates may pick task assignment or status reporting as 'leadership' when those are actually directive behaviors.

Full explanation →

189

MCQeasy

A team is transitioning from a traditional project management approach to an Agile framework. The project manager wants to ensure the team embraces the core value of 'Individuals and Interactions over Processes and Tools'. Which action best demonstrates this shift?

A.Mandate that all team communication occurs exclusively through the issue tracking system.

B.Strictly enforce the use of standardized status report templates for every update.

C.Encourage daily stand-up meetings to be conducted in person or via video to foster real-time collaboration.

D.Focus on automating all project reports before addressing team dependencies.

AnswerC

Stand-ups conducted in person or by video create real-time, face-to-face dialogue, directly embodying individuals and interactions over processes and tools. This satisfies the stem's constraint by prioritising human collaboration rather than relying on tooling or documented procedure.

Why this answer

Encouraging daily stand-ups in person or via video to foster real-time collaboration directly demonstrates 'Individuals and Interactions over Processes and Tools' because it prioritizes synchronous human communication over rigid tooling or documentation. This aligns with the Agile Manifesto's first value, emphasizing that effective collaboration and conversation are more valuable than standardized processes or systems.

Exam trap

PMI-ACP often tests the four Agile values by presenting options that sound efficient or modern (automation, standardized templates) but actually prioritize tools/processes over people; candidates must recognize the value hierarchy.

How to eliminate wrong answers

Option A is wrong because mandating exclusive communication through an issue tracking system prioritizes tools over individuals, directly contradicting the Agile value. Option B is wrong because strictly enforcing standardized status report templates prioritizes processes and documentation over interactions. Option D is wrong because focusing on automating reports before addressing team dependencies prioritizes tools and processes over the human collaboration needed to resolve impediments.

Full explanation →

190

MCQeasy

During a sprint planning session, the team realizes that the current sprint backlog contains items with significantly higher effort than the team's historical average velocity. What is the most appropriate action for the Scrum Master to facilitate?

A.Remove the items from the backlog entirely until the team's velocity improves.

B.Encourage the Product Owner to split the large backlog items into smaller, INVEST-compliant user stories.

C.Assign the large items to senior developers only to ensure completion.

D.Increase the sprint duration to accommodate the large items.

AnswerB

Oversized items break the sprint's forecast reliability, so splitting them into smaller INVEST-compliant stories restores estimability and flow. The Scrum Master facilitates this by coaching the Product Owner to decompose work, keeping each slice independently valuable and completable within the sprint, matching historical velocity.

Why this answer

When sprint backlog items are significantly larger than the team's historical velocity can absorb, the root problem is item size, not team capability. The Scrum Master should facilitate splitting oversized items into smaller, INVEST-compliant user stories so the team can deliver incrementally within the sprint and maintain a sustainable pace. This preserves flow and predictability.

Exam trap

PMI-ACP often tests whether candidates reach for structural fixes (extend sprint, reassign to seniors) instead of the agile-correct response of splitting work to fit the team's demonstrated capacity.

How to eliminate wrong answers

Option A is wrong because removing items entirely abandons value delivery and doesn't solve the sizing problem — the work still needs to be done eventually. Option C is wrong because assigning work to senior developers only violates self-organization and creates a single point of failure, plus it doesn't reduce item size. Option D is wrong because extending the sprint duration breaks the cadence, invalidates velocity baselines, and is a Scrum anti-pattern — sprint length should remain consistent to enable reliable forecasting.

Full explanation →

191

Multi-Selectmedium

A Product Owner is preparing a product roadmap for a new SaaS platform. Stakeholders have conflicting priorities: sales wants custom features for a large client, while engineering wants to reduce technical debt. Which TWO actions best align with agile product management principles to balance these competing demands? (Choose two.)

Select 2 answers

A.Ask the engineering team to work overtime for several sprints to deliver both custom features and technical debt fixes.

B.Commit to delivering all custom features for the large client in the next sprint to secure the contract.

C.Escalate the conflict to senior management and ask them to decide the priority order for the Product Owner.

D.Prioritize backlog items based on customer value, risk, and dependency, and make the prioritization transparent to stakeholders.

E.Allocate a fixed percentage of each sprint's capacity to technical debt reduction, and treat it as a first-class backlog item.

AnswersD, E

This is correct because agile product management emphasizes value-driven prioritization that considers multiple factors. Making the process transparent helps stakeholders understand trade-offs and reduces conflict. It also allows the Product Owner to justify decisions with data rather than politics. This approach aligns with the PMI-ACP principle of delivering value continuously while managing stakeholder expectations.

Why this answer

Balancing competing demands requires value-based prioritization and explicit capacity allocation for technical debt. Transparent prioritization helps stakeholders see trade-offs, while dedicating capacity to debt prevents its accumulation. Together, these actions align with agile principles of delivering value sustainably and managing stakeholders collaboratively.

They also empower the Product Owner to make informed decisions without overcommitting the team.

Exam trap

The trap here is thinking that satisfying the loudest stakeholder immediately or escalating every conflict is effective product management, rather than using transparent value-based trade-offs.

Full explanation →

192

Multi-Selecthard

Which TWO actions should a practitioner take when the team is consistently failing to meet the Definition of Done?

Select 2 answers

A.Fire the team.

B.Review and potentially refine the Definition of Done to ensure it is achievable and clear.

C.Facilitate a retrospective to identify the root cause of the failures.

D.Lower the standards to match current output.

E.Publicly shame the team.

AnswersB, C

If the team repeatedly misses the Definition of Done, the criterion itself may be unrealistic or ambiguous, so reviewing and refining it addresses the root constraint. This keeps the standard meaningful while making it achievable, directly resolving the consistent failure described in the stem.

Why this answer

Option B is correct because when a team consistently misses the Definition of Done, the DoD itself may be ambiguous, overly ambitious, or misaligned with the team's actual capabilities, so reviewing and refining it to be clear and achievable is a legitimate corrective action. Option C is correct because a retrospective is the standard agile ceremony for inspecting the team's process and identifying the root cause of repeated failures, enabling data-driven improvement rather than blame. Option A is wrong because firing the team is punitive and does nothing to diagnose or fix the underlying process problem.

Option D is wrong because lowering standards to match poor output degrades quality and undermines the purpose of the Definition of Done rather than addressing the cause. Option E is wrong because public shaming is destructive, unprofessional, and counterproductive to team psychological safety and continuous improvement.

Exam trap

PMI-ACP often tests the instinct to lower standards or blame individuals, but the Agile response is always to inspect and adapt through retrospectives and collaborative refinement of the Definition of Done.

Full explanation →

193

MCQhard

The team is stuck in a 'blame game' after a failed release. How do you facilitate a transition to an Agile mindset?

A.Facilitate a blame-free post-mortem focused on process gaps.

B.Disband the team and create new ones.

C.Identify the individual responsible for the failure.

D.Ask the manager to provide disciplinary actions.

AnswerA

A blame-free post-mortem redirects attention from individual fault to systemic process gaps, which is the specific mechanism that shifts the team toward Agile's empirical, improvement-driven mindset. Addressing the root causes of the failed release satisfies the stem's need to break the blame cycle and restore psychological safety.

Why this answer

Facilitating a blame-free post-mortem focused on process gaps transitions the team to an agile mindset by emphasizing systemic improvement over individual fault. This aligns with agile values of respect, courage, and continuous learning.

Exam trap

The trap is selecting punitive or structural options (blame, disband, discipline) that seem to address failure but actually undermine the agile principle of safe, continuous improvement.

How to eliminate wrong answers

Option B is wrong because disbanding the team destroys accumulated knowledge and does not address the underlying issues. Option C is wrong because identifying an individual to blame fosters fear and defensiveness, which inhibits learning. Option D is wrong because disciplinary actions are punitive and counter to psychological safety, which is essential for agile teams.

Full explanation →

194

MCQmedium

A team is feeling 'sprint fatigue'. What should you do?

A.Push them to work harder.

B.Suggest they all take a vacation at once.

C.Discuss how to maintain a more sustainable pace in the next retrospective.

D.Cancel the next sprint.

AnswerC

Raising sustainable pace in the retrospective lets the team inspect the fatigue's causes and adapt its process collaboratively. It satisfies the agile principle of maintaining a constant, sustainable pace, rather than imposing overtime or ignoring the team's morale signal.

Why this answer

Sprint fatigue signals an unsustainable pace, and the Agile response is to address it through the team's own inspect-and-adapt mechanism. Discussing a more sustainable pace in the next retrospective (C) lets the team identify the causes — overcommitment, technical debt, lack of slack — and adjust. This aligns with the Agile principle that teams should work at a sustainable pace indefinitely.

Exam trap

The trap is the reflexive productivity response, so candidates pick 'push harder' or a quick-fix vacation instead of the Agile move of addressing pace systemically in the retrospective.

How to eliminate wrong answers

Option A is wrong because pushing a fatigued team to work harder accelerates burnout and reduces quality, directly violating the sustainable-pace principle. Option B is wrong because a simultaneous team vacation halts delivery and does not fix the systemic causes of fatigue, which will recur on return. Option D is wrong because cancelling the next sprint removes the cadence and transparency the team needs, and it does not address the underlying pace problem.

Full explanation →

195

MCQhard

Your organization is transitioning to Agile. Some managers are resisting. How do you handle this?

A.Engage the managers in conversations about the benefits and address their concerns.

B.Ignore the managers and proceed with the team.

C.Escalate to the CEO.

D.Wait for them to retire.

AnswerA

Resistance usually stems from unaddressed fears about roles, metrics and control. Engaging managers directly, explaining Agile benefits and listening to their concerns builds ownership and converts sceptics into sponsors, which sustains the transition far better than mandating compliance.

Why this answer

Resistance to Agile transformation is best addressed through engagement, education, and empathy — understanding managers' concerns (e.g., loss of control, unclear metrics) and demonstrating benefits with data. This aligns with the Agile principle of building trust and collaboration across the organization. Ignoring, escalating, or waiting out resistance are passive or coercive approaches that undermine sustainable change.

Exam trap

The trap is choosing a fast, forceful resolution (escalate, ignore, wait) — candidates underestimate the need for stakeholder engagement and cultural change in Agile transformations.

How to eliminate wrong answers

Option B is wrong because ignoring managers creates organizational silos and ensures the transformation stalls at the team level — Agile requires organizational alignment. Option C is wrong because escalating to the CEO is a coercive, top-down move that breeds resentment and does not address the root cause of resistance. Option D is wrong because waiting for resistors to retire is passive and unrealistic — it delays value delivery and allows resistance to entrench.

Full explanation →

196

MCQeasy

Which document acts as the single source of truth for all work to be performed by the development team?

A.The sprint burndown chart.

B.The communication plan.

C.The project charter.

D.The product backlog.

AnswerD

The product backlog is the single source of truth for all work the development team performs, holding every feature, enhancement and fix in priority order. It satisfies the stem's requirement by centralising scope that the team pulls into sprints.

Why this answer

The product backlog is the single source of truth for all work the development team may perform. It is a prioritized, ordered list of everything that might be needed in the product, owned by the Product Owner and refined continuously. In Scrum and most Agile frameworks, the sprint backlog is derived from the product backlog, and no work should be done that is not represented there.

Exam trap

PMI-ACP often tests the distinction between the product backlog (all potential work) and the sprint backlog (committed work for one sprint), causing candidates to confuse the two or pick the charter as the overarching document.

How to eliminate wrong answers

Option A is wrong because the sprint burndown chart is a visualization of remaining work within a single sprint, not a comprehensive list of all work to be performed. Option B is wrong because the communication plan describes how information will be shared among stakeholders, not what work the team will do. Option C is wrong because the project charter authorizes the project and defines high-level scope and objectives, but it is not the working list of deliverables the team pulls from.

Full explanation →

197

Multi-Selecteasy

Which TWO strategies can a leader use to promote psychological safety? (Choose TWO)

Select 2 answers

A.Encouraging team members to speak up, even if their opinion is unpopular.

B.Publicly criticizing team members for their errors.

C.Demanding total conformity to the team's existing views.

D.Treating mistakes as opportunities for the team to learn.

E.Rewarding only the team members who never make mistakes.

AnswersA, D

Actively inviting dissenting or unpopular views signals that challenging the majority is safe, so members voice concerns instead of self-censoring. This directly cultivates the shared belief that speaking up carries no penalty, which is the psychological safety the stem requires.

Why this answer

Option A is correct because psychological safety is built when leaders actively invite dissenting and unpopular viewpoints, signaling that speaking up will not be punished; this is the core behavior of a psychologically safe environment. Option D is correct because framing mistakes as learning opportunities normalizes error reporting and experimentation, which reduces fear and encourages transparency, a key pillar of psychological safety. Option B is incorrect because public criticism of errors increases interpersonal risk and shuts down open communication.

Option C is incorrect because demanding conformity suppresses the diverse input and candor that psychological safety requires. Option E is incorrect because rewarding only those who never err creates a blame culture and discourages honesty about mistakes.

Exam trap

PMI-ACP often tests whether candidates can distinguish psychological safety from mere niceness or from accountability — options that sound like strong leadership (public criticism, rewarding perfection) actually destroy the safety needed for high performance.

Full explanation →

198

Multi-Selectmedium

Which THREE traits are characteristic of a servant leader in an Agile team?

Select 3 answers

A.Removing impediments that prevent the team from achieving their goals.

B.Directing the team on exactly how to perform their daily technical tasks.

C.Focusing on the personal and professional development of team members.

D.Acting as a shield to protect the team from external interruptions.

E.Making all final decisions regarding the product architecture.

AnswersA, C, D

Removing impediments directly satisfies the servant leader's duty to shield the team from blockers, enabling self-organisation and flow. Unlike command-and-control direction, this trait places the leader in a supporting role, clearing obstacles so the team retains ownership of delivery decisions and maintains sustainable pace.

Why this answer

Option A is correct because a servant leader's core duty is to clear obstacles and blockers so the team can meet its goals, which is the essence of removing impediments. Option C is correct because servant leadership prioritizes growing people, so investing in team members' personal and professional development is a defining trait. Option D is correct because shielding the team from external interruptions and distractions preserves their focus and autonomy, a hallmark of servant leadership.

Option B is not correct because dictating exactly how team members perform daily technical tasks is directive, command-and-control management, the opposite of servant leadership. Option E is not correct because unilaterally making all product architecture decisions concentrates authority in the leader rather than empowering the self-organizing team.

Exam trap

PMI-ACP often tests the confusion between servant leadership and technical leadership — candidates may incorrectly select options where the leader directs technical tasks or makes architecture decisions, which are not servant-leadership behaviors.

Full explanation →

199

MCQeasy

A Product Owner notices that the product backlog has grown significantly, making it difficult to find relevant work items. Which action should the Product Owner take to improve visibility?

A.Group related user stories under larger epics.

B.Archive the entire backlog and start a new one.

C.Increase the number of items per page in the tool.

D.Delete all old user stories to clear the clutter.

AnswerA

Grouping related user stories under larger epics reduces backlog clutter by creating a hierarchical structure, so the Product Owner can navigate themes rather than scanning every item. This directly satisfies the stem's visibility constraint, since epics act as parent containers that collapse detailed stories, making relevant work items easier to locate as the backlog grows.

Why this answer

Grouping related user stories under larger epics improves backlog visibility by creating a hierarchical structure that reduces clutter while preserving detail at the story level. This is a standard backlog refinement technique that helps the Product Owner and team navigate large backlogs. It maintains traceability from high-level themes to granular work items.

Exam trap

PMI-ACP often tests the misconception that backlog problems are solved by tool settings or wholesale deletion; the trap is choosing a destructive or cosmetic action instead of the structural refinement technique of grouping stories under epics.

How to eliminate wrong answers

Option B is wrong because archiving the entire backlog and starting a new one destroys historical context, traceability, and potentially valuable deferred work, and it does not solve the underlying organization problem. Option C is wrong because increasing items per page is a cosmetic UI change that does not improve logical structure or findability of relevant work. Option D is wrong because deleting old user stories removes potentially valuable backlog items and loses the rationale and history that support future prioritization decisions.

Full explanation →

200

MCQeasy

A stakeholder asks you to prioritize a feature for the next release. What is your response?

A.Refer the stakeholder to the Product Owner to discuss priority.

B.Tell the stakeholder that you are the decision-maker for features.

C.Ask the team to add it to the current sprint.

D.Agree to add the feature if it seems simple.

AnswerA

Referring the stakeholder to the Product Owner respects the Product Owner's authority over backlog prioritisation, which is the core constraint here. In Agile, the Product Owner alone sequences work to maximise value; team members must not accept priority requests directly, or scope and priorities fragment. This keeps a single, accountable voice for the backlog.

Why this answer

In agile, the Product Owner is the single voice of the customer and the sole authority for backlog prioritization. When a stakeholder requests a feature, the correct response is to route them to the Product Owner, who can weigh the request against existing priorities, value, and release goals. This preserves a single prioritization funnel and prevents the team from being pulled in multiple directions.

Exam trap

PMI-ACP often tests the misconception that a project manager or team lead can make prioritization decisions, when in agile the Product Owner is the exclusive authority for backlog ordering.

How to eliminate wrong answers

Option B is wrong because claiming to be the decision-maker for features usurps the Product Owner's role and creates conflicting sources of truth for priorities. Option C is wrong because asking the team to add it to the current sprint bypasses both the Product Owner and sprint planning, violating the sprint commitment and enabling scope creep. Option D is wrong because agreeing to add a feature simply because it 'seems simple' ignores value-based prioritization and the Product Owner's authority, and 'simple' features often carry hidden complexity.

Full explanation →

201

MCQeasy

A team feels that their daily stand-up is a waste of time. What should you do?

A.Start asking all the questions yourself.

B.Tell them they have to do it because it is required.

C.Facilitate a discussion on how to make it more valuable for them.

D.Cancel the stand-up.

AnswerC

A retrospective-style discussion lets the team diagnose why the stand-up feels wasteful and redesign its format themselves. This satisfies the Agile principle of self-organising teams, producing a purpose-driven daily sync rather than imposing a fix the team resists.

Why this answer

When a team finds the daily stand-up wasteful, the servant leader should facilitate a conversation about its purpose and format rather than impose or abandon it. The stand-up exists to enable daily inspection and adaptation, so the team should own how it is run. Facilitating a discussion (C) respects self-organization and lets the team redesign the ceremony to deliver value.

Exam trap

The trap is treating the stand-up as a mandatory ritual, so candidates pick 'tell them it is required' or 'cancel it' instead of the Agile response of facilitating team-owned improvement.

How to eliminate wrong answers

Option A is wrong because the Scrum Master or leader asking all the questions turns the stand-up into a status report to management, reinforcing the exact dysfunction the team is complaining about. Option B is wrong because mandating attendance 'because it is required' is command-and-control coercion that destroys intrinsic motivation and does not fix the ceremony's value. Option D is wrong because cancelling the stand-up removes a core inspect-and-adapt event and eliminates the transparency the team needs, rather than improving it.

Full explanation →

202

MCQmedium

A Scrum team is building a mobile banking app. The Product Owner has a product backlog with 120 items, but the team often complains that the highest-priority items are too vague to estimate. Which action best applies the principle of progressive elaboration to improve the backlog?

A.Break down the top 10-15 backlog items into smaller, detailed stories with acceptance criteria, while leaving lower-priority items coarse.

B.Ask the team to estimate all 120 items in a single two-day estimation workshop to create a complete baseline.

C.Delegate all backlog refinement to a business analyst and have the team only review finalized stories at sprint planning.

D.Create a detailed Gantt chart mapping all 120 backlog items to specific sprints over the next 18 months.

AnswerA

This is correct because progressive elaboration means adding detail to backlog items just in time, based on priority. The team needs enough clarity for near-term work, so refining the top items into smaller stories with clear acceptance criteria directly addresses their complaint. Lower-priority items can remain coarse until they move up, avoiding wasted effort. This balances planning with agility.

Why this answer

Progressive elaboration means elaborating backlog items at the last responsible moment, focusing detail on what is near-term. Refining the top items into smaller stories with acceptance criteria gives the team enough information to estimate and plan upcoming sprints. Leaving lower-priority items coarse avoids wasted analysis.

This approach directly resolves the team's complaint while preserving agility.

Exam trap

The trap here is confusing progressive elaboration with upfront detailed planning of the entire backlog, which feels thorough but undermines agility.

Full explanation →

203

MCQeasy

Which metric is most useful for measuring the team's ability to deliver consistent value per iteration?

A.Individual task duration.

B.Velocity.

C.Team morale survey scores.

D.Number of meetings attended.

AnswerB

Velocity measures story points completed per iteration, directly quantifying the team's throughput. For assessing consistency of value delivery across iterations, its iteration-by-iteration trend reveals variability that cumulative metrics hide. PMI-ACP treats velocity as the standard empirical measure of predictable delivery capacity, satisfying the stem's requirement for per-iteration consistency.

Why this answer

Velocity measures the amount of work (typically in story points) a team completes per iteration, making it the standard metric for gauging consistent value delivery across sprints. Tracking velocity over time reveals whether the team's throughput is stable, improving, or erratic, which directly reflects their ability to deliver predictably each iteration. It is a team-level metric, not an individual one, aligning with agile principles.

Exam trap

PMI-ACP often tests the misconception that velocity is an individual performance metric or a target to maximize, when it is actually a team-level planning and forecasting tool.

How to eliminate wrong answers

Option A is wrong because individual task duration measures personal efficiency on discrete tasks, not the team's collective delivery of value per iteration, and it encourages counterproductive individual tracking. Option C is wrong because morale survey scores reflect team health and engagement, which are important but do not quantify value delivered per iteration. Option D is wrong because the number of meetings attended is an activity metric with no relationship to value output or delivery consistency.

Full explanation →

204

MCQhard

A team is having difficulty with the 'Definition of Done'. How do you facilitate?

A.Define the 'Definition of Done' for them.

B.Ignore the 'Definition of Done' and focus on finishing features.

C.Copy a 'Definition of Done' from another team.

D.Facilitate a workshop to help the team agree on quality standards and criteria for completion.

AnswerD

A shared workshop lets the team itself define quality standards and completion criteria, directly resolving the ambiguity causing the difficulty. Collective agreement builds ownership, so the Definition of Done reflects the team's actual context rather than being imposed, satisfying the need for a workable, understood definition.

Why this answer

Facilitating a workshop (D) lets the team collaboratively define what 'done' means for their context, building shared ownership and clarity. The Definition of Done must be created by the team, not imposed, because it reflects their quality standards and working agreements. A workshop format ensures all voices are heard and the resulting criteria are realistic and agreed upon.

Exam trap

PMI-ACP often tests whether candidates know the Definition of Done must be team-owned and context-specific, not copied from another team or dictated by the leader.

How to eliminate wrong answers

Option A is wrong because defining the Definition of Done for the team removes their ownership and likely produces criteria they do not fully understand or commit to. Option B is wrong because ignoring the Definition of Done leads to inconsistent quality and unclear completion criteria, which is the exact problem the team is facing. Option C is wrong because copying another team's Definition of Done ignores context — different teams have different technologies, compliance needs, and quality expectations.

Full explanation →

205

MCQhard

A distributed agile team has been missing sprint goals for three consecutive sprints. During a retrospective, the team identifies that they lack a shared understanding of the definition of done and that handoffs between two sub-teams are causing delays. As the agile leader, what is the most effective action to take?

A.Escalate the missed sprint goals to the product owner and recommend that they reprioritize the backlog to reduce complexity.

B.Facilitate a workshop to establish a single, explicit definition of done and visualize the value stream to expose handoff delays.

C.Add a buffer to each sprint to account for the delays and set more conservative sprint goals until the team stabilizes.

D.Instruct the two sub-teams to merge into a single cross-functional team immediately to eliminate handoffs.

AnswerB

This action addresses both root causes the team identified: ambiguity about done and handoff delays. A workshop to co-create a definition of done builds shared understanding, while value stream mapping makes the handoffs and their delays visible. This enables the team to design improvements themselves. It is a systems-thinking approach that respects the team's ownership of their process while providing the structure they need to move forward.

Why this answer

The team has identified two systemic issues: no shared definition of done and handoff delays between sub-teams. The most effective leadership action is to facilitate a workshop where the team co-creates a definition of done and maps the value stream to make handoffs visible. This builds shared understanding and enables the team to design their own improvements.

Buffering, escalating, or mandating structural change do not address the root causes and may undermine team ownership.

Exam trap

The trap here is choosing a structural reorganization or a schedule buffer as a quick fix, when the real need is to help the team clarify its shared standards and visualize its workflow.

Full explanation →

206

Multi-Selecthard

A Product Owner is refining a product backlog and wants to apply good agile product management practices to maximize value delivery. Which TWO actions best support effective product backlog management? (Choose two.)

Select 2 answers

A.Assign every backlog item a fixed delivery date at the start of the product and refuse to reorder regardless of new learning.

B.Continuously order backlog items by value, risk, dependencies, and cost of delay rather than freezing the sequence at project start.

C.Collaborate with the team during refinement to add detail, estimate effort, and split large items just in time for upcoming work.

D.Fully detail every backlog item to the same depth at the start of the product so the team never needs to refine again.

E.Keep the product backlog private to the Product Owner so the team and stakeholders cannot see items that may change.

AnswersB, C

Effective product backlog management requires continuous ordering that reflects current value, risk, dependencies, and cost of delay. Freezing the sequence at project start ignores learning and market change, so the backlog becomes stale. Revisiting the order frequently keeps the team working on the most economically important items and lets the Product Owner respond to new information as the product evolves.

Why this answer

Effective product backlog management rests on continuous ordering that reflects value, risk, dependencies, and cost of delay, combined with just-in-time collaborative refinement. Together these practices keep the most important items ready and economically sequenced while avoiding wasted upfront detail. Transparency and willingness to reorder based on learning are implicit in both actions, ensuring the backlog remains a living tool for maximizing product value.

Exam trap

The trap here is assuming thorough upfront detail and fixed sequencing make backlog management rigorous, when they actually destroy agility and waste effort.

Full explanation →

207

MCQeasy

A team is struggling to maintain a consistent cadence due to external dependencies. Which action best aligns with optimizing end-to-end flow?

A.Switch to Kanban to eliminate the need for sprint planning.

B.Lengthen the sprint duration to allow more time for external teams to respond.

C.Assign a dedicated project manager to track dependency status manually.

D.Implement a formal dependency board to visualize blockers and upstream/downstream impacts.

AnswerD

A dependency board makes upstream and downstream blockers visible, so the team can sequence work around external constraints instead of absorbing idle time. Visualising impacts enables earlier escalation and pull-based coordination, restoring the consistent cadence that external dependencies had disrupted.

Why this answer

A dependency board makes external blockers and their upstream/downstream impacts visible to the whole team, which is the core mechanism for optimizing end-to-end flow in Kanban/agile practice. Visualizing dependencies lets the team swarm on blockers, re-sequence work, and escalate early rather than discovering delays at sprint review. This directly addresses the root cause (unmanaged external dependencies) without changing the team's cadence.

Exam trap

PMI-ACP often tests the misconception that changing the framework (e.g., switching to Kanban) or adding a coordinator solves flow problems, when the agile answer is almost always to make work and impediments visible.

How to eliminate wrong answers

Option A is wrong because switching to Kanban does not eliminate sprint planning—Kanban still requires replenishment/planning activities and does not by itself resolve external dependencies. Option B is wrong because lengthening the sprint merely hides the dependency problem and delays feedback, violating the agile principle of short feedback loops. Option C is wrong because assigning a project manager to manually track dependencies centralizes information and creates a bottleneck rather than making flow visible to the team.

Full explanation →

208

Multi-Selectmedium

Which THREE characteristics of a servant leader are most effective for an agile coach? (Choose THREE)

Select 3 answers

A.Rigidity to ensure the process is followed exactly as written.

B.Stewardship to act in the best interests of the team and the organization.

C.Active listening to understand the team's needs.

D.Empathy to build strong relationships and trust.

E.Dominance to ensure the team follows instructions.

AnswersB, C, D

Stewardship means holding the team's and organisation's longer-term interests above personal gain, so the coach protects the team's growth rather than chasing credit. This satisfies the stem's requirement for a servant-leadership characteristic that balances both team and organisational benefit.

Why this answer

Servant leadership in agile coaching centers on putting the team's growth and needs first, so option B (stewardship) is correct because acting in the best interests of both the team and the organization aligns with the coach's responsibility to nurture sustainable, value-driven outcomes. Option C (active listening) is correct because an agile coach must genuinely hear and understand the team's concerns, impediments, and perspectives before offering guidance, which is foundational to effective coaching. Option D (empathy) is correct because building strong relationships and trust enables psychological safety, which is essential for teams to self-organize, experiment, and improve.

Options A (rigidity) and E (dominance) do not belong because they contradict servant leadership and agile principles: rigid process enforcement and top-down control undermine self-management, empowerment, and continuous improvement, which an agile coach should foster rather than suppress.

Exam trap

The trap is selecting characteristics that sound like strong leadership (e.g., rigidity, dominance) but are actually antithetical to servant leadership; the exam tests your understanding that servant leadership is about serving and empowering the team, not controlling it.

Full explanation →

209

MCQhard

A regulated organization requires documented evidence that each increment was independently verified before release. The team wants to keep delivering every two weeks. Which approach best satisfies the compliance requirement while preserving agile delivery?

A.Ask the compliance team to accept the team's existing manual test records without change.

B.Move verification to a separate stage after the final iteration, immediately before release.

C.Automate the verification evidence as part of the Definition of Done and the continuous integration pipeline.

D.Extend iterations to six weeks so verification activities can complete within each iteration.

AnswerC

Embedding verification into the Definition of Done and generating evidence automatically makes compliance a byproduct of normal work rather than a separate phase. The team keeps its two-week cadence, the regulator receives consistent auditable records, and verification becomes faster and more reliable than a manual end-of-cycle review would be.

Why this answer

Compliance and agility are compatible when verification is built into the Definition of Done and evidence is generated automatically by the pipeline. This produces auditable records continuously, keeps the team's two-week cadence intact, and avoids the risk concentration and delay that a separate verification phase would introduce.

Exam trap

The trap here is assuming that regulatory verification must be a separate phase after development, rather than a condition of done that can be automated into the delivery pipeline.

Full explanation →

210

Multi-Selectmedium

Which TWO strategies are recommended for managing a product backlog that has grown too large?

Select 2 answers

A.Archive or remove low-priority items that are unlikely to be built.

B.Delete the entire backlog.

C.Increase the sprint size to finish it all.

D.Assign all items to developers.

E.Regularly refine and prioritize the backlog with the Product Owner.

AnswersA, E

Archiving or deleting low-priority items that are unlikely to be built shrinks the backlog to a manageable, decision-ready size. It removes stale entries that distort prioritisation and inflate refinement effort, keeping the remaining items ordered and genuinely actionable.

Why this answer

Option A is correct because archiving or removing low-priority items that are unlikely to be built directly reduces the backlog's size, keeping it focused on work that delivers value and preventing it from becoming an unmanageable wish list. Option E is correct because regularly refining and prioritizing the backlog with the Product Owner ensures the most valuable items rise to the top, keeps the backlog current, and prevents uncontrolled growth through continuous grooming. Option B is wrong because deleting the entire backlog discards potentially valuable requirements and destroys the product's strategic direction.

Option C is wrong because increasing sprint size does not reduce backlog size and violates the principle of keeping sprints short and time-boxed. Option D is wrong because assigning all items to developers does not shrink or prioritize the backlog and ignores capacity and value-based ordering.

Exam trap

PMI-ACP often tests the misconception that a large backlog should be handled by expanding capacity or deleting it wholesale, when the correct agile response is disciplined pruning and continuous refinement.

Full explanation →

211

MCQmedium

You are the agile leader of a distributed team. During Sprint Review, a key stakeholder loudly challenges the team's estimates, causing a junior developer to stop contributing for the rest of the meeting. What is your best action?

A.Tell the stakeholder that estimates are not up for discussion and continue the review without addressing the challenge.

B.Ask the junior developer to explain the estimates in detail to the stakeholder immediately, so the team can defend its position.

C.End the Sprint Review early and reschedule it for a later date when the stakeholder is calmer.

D.Pause the review, acknowledge the concern, and invite the stakeholder to discuss estimates in a separate session so the team can finish presenting.

AnswerD

This action protects the team's psychological safety while still respecting the stakeholder's concern. By separating the estimate debate from the review, the leader keeps the ceremony focused on product feedback and ensures the junior developer can continue contributing without feeling attacked, which supports the collaborative and safe environment essential for agile teams.

Why this answer

The correct action balances respect for the stakeholder with protection of the team's psychological safety. By pausing to acknowledge the concern and moving the estimate debate to a separate session, the leader keeps the Sprint Review focused on product inspection and adaptation, while ensuring the junior developer is not marginalized. This models servant leadership and maintains a safe, collaborative environment.

Exam trap

The trap here is assuming that the leader must either fully defend the team by silencing the stakeholder or fully accommodate the stakeholder by forcing the team to justify estimates on the spot.

Full explanation →

212

Multi-Selectmedium

Which THREE of the following reflect 'embracing change'?

Select 3 answers

A.Ignoring customer feedback to stay on track

B.Sticking to the original project plan at all costs

C.Pivoting the strategy after a failed experiment

D.Refining requirements iteratively throughout the project

E.Prioritizing the product backlog based on new market trends

AnswersC, D, E

Pivoting strategy after a failed experiment treats failure as validated learning rather than a setback, redirecting effort toward what the evidence supports. This embodies embracing change by letting empirical outcomes, not the original plan, drive the next decision.

Why this answer

Option C is correct because pivoting the strategy after a failed experiment demonstrates a willingness to learn from outcomes and adapt direction rather than clinging to a failing approach, which is central to embracing change. Option D is correct because refining requirements iteratively throughout the project accepts that needs will evolve and incorporates feedback continuously instead of freezing scope upfront. Option E is correct because prioritizing the product backlog based on new market trends shows responsiveness to external shifts, allowing value delivery to stay aligned with current conditions.

Options A and B are incorrect because ignoring customer feedback and rigidly sticking to the original plan both resist change and reject the adaptive, feedback-driven mindset that embracing change requires.

Exam trap

PMI-ACP often tests the false dichotomy that embracing change means abandoning all planning, so candidates reject iterative refinement or backlog re-prioritization as 'not really change' and pick rigid options instead.

Full explanation →

213

MCQmedium

A team is struggling with meeting their sprint goals. What is the best strategy to improve delivery reliability?

A.Increase velocity targets arbitrarily.

B.Focus on improving estimation accuracy and managing capacity effectively.

C.Force the team to work weekends.

D.Decrease the quality standards.

AnswerB

Improving estimation accuracy and actively managing capacity addresses the root cause of missed sprint goals: unreliable forecasts and overcommitment. By calibrating estimates against historical velocity and limiting work in progress to true available capacity, the team commits to achievable goals and delivery reliability rises.

Why this answer

Sprint goal reliability improves when the team's forecasts match its actual capacity. Focusing on estimation accuracy (e.g., through story point calibration, reference stories, and historical data) and actively managing capacity (accounting for leave, ceremonies, and support work) directly addresses the root causes of missed goals. This is the empirical, sustainable path.

Exam trap

PMI-ACP often tests the temptation to 'motivate' teams by raising targets or working longer hours, versus the agile-correct response of improving estimation and capacity management.

How to eliminate wrong answers

Option A is wrong because arbitrarily raising velocity targets is a management fiction — velocity is a measured output, not a target to be dictated, and inflating it guarantees missed goals. Option C is wrong because forcing weekend work is unsustainable, degrades quality, and violates agile's sustainable-pace principle. Option D is wrong because lowering quality standards trades short-term appearance of delivery for long-term technical debt and rework, which further erodes reliability.

Full explanation →

214

Multi-Selecteasy

Which TWO of the following reflect the Agile focus on quality?

Select 2 answers

A.Avoiding testing to speed up delivery

B.Lowering standards to meet deadlines

C.Quality is checked only at the very end of the project

D.Continuous feedback loops to improve the product

E.Quality is built into the product from the start

AnswersD, E

Short feedback loops — daily stand-ups, sprint reviews, retrospectives and automated tests — surface defects and mismatches early, when correction is cheapest. This continuous cycle of inspect-and-adapt is how Agile teams improve both product quality and process quality throughout delivery.

Why this answer

Option D is correct because Agile quality relies on continuous feedback loops—short iterations, frequent demos, and retrospectives—that let teams detect defects and adjust requirements early, rather than waiting for a final inspection. Option E is correct because Agile builds quality into the product from the start through practices such as test-driven development, definition of done, continuous integration, and refactoring, so defects are prevented rather than merely detected later. Options A and B are incorrect because skipping testing or lowering standards directly undermines quality and contradicts Agile values of sustainable pace and technical excellence.

Option C is incorrect because deferring all quality checks to the very end reflects a waterfall-style phase-gate approach, whereas Agile verifies quality continuously throughout each iteration.

Exam trap

PMI-ACP often tests the misconception that Agile prioritizes speed over quality, leading candidates to select options that sacrifice testing or defer quality checks, when in fact Agile embeds quality throughout the lifecycle.

Full explanation →

215

MCQmedium

A stakeholder requests a major change to the sprint backlog mid-sprint. How do you respond as an agile leader?

A.Ask the developers to work overtime to accommodate the request.

B.Reject the request immediately as it violates the sprint commitment.

C.Ask the Product Owner to discuss the impact with the stakeholder and evaluate if the goal can still be met.

D.Add the work to the sprint backlog immediately.

AnswerC

The Product Owner owns backlog ordering and stakeholder negotiation, so routing the mid-sprint change request through them preserves the sprint goal. They assess impact against committed work and decide whether the goal remains achievable, satisfying the stem's constraint of protecting the sprint.

Why this answer

In agile, the Product Owner owns the backlog and is the single point of contact for stakeholder requests. The correct response is to route the change through the Product Owner, who can assess impact against the sprint goal and negotiate scope with the stakeholder. This preserves the team's focus while respecting the empirical nature of sprint planning.

Exam trap

PMI-ACP often tests whether candidates bypass the Product Owner or violate sustainable pace; the trap is choosing an action that seems responsive but undermines the PO's authority or the team's self-management.

How to eliminate wrong answers

Option A is wrong because asking developers to work overtime is unsustainable, violates agile's emphasis on a sustainable pace, and bypasses the Product Owner's authority. Option B is wrong because an immediate blanket rejection ignores the possibility that the change is valuable and that the sprint goal may still be achievable — agile embraces responding to change. Option D is wrong because unilaterally adding work to the sprint backlog undermines the team's self-management and the Product Owner's ownership of the backlog, and it risks breaking the sprint goal.

Full explanation →

216

MCQeasy

Midway through an iteration, a team discovers that a third-party payment gateway it depends on will not be available for integration testing until two weeks after the iteration ends. The team has already built the integration code. What should the practitioner do first?

A.Escalate to the vendor's account manager and pause all other team work until the gateway is available.

B.Make the dependency visible on the team's impediment board and explore a stub or contract test to validate the integration logic now.

C.Cancel the iteration and re-plan the release once the vendor confirms a firm date.

D.Add the integration testing to the next iteration and mark the current stories as complete.

AnswerB

Surfacing the impediment makes it transparent and actionable, while a stub or contract test lets the team verify its own integration logic without the live gateway. This preserves flow, keeps the increment potentially shippable, and positions the team to swap in the real endpoint quickly once the vendor is ready, which is the smallest effective first step.

Why this answer

The most effective first move combines transparency with mitigation: make the blocker visible so it can be managed, and use stubs or contract tests so the team's own integration logic can still be verified. This keeps the increment honest against the Definition of Done while avoiding both idle capacity and false completion claims.

Exam trap

The trap here is treating an external dependency as a reason to stop the iteration or to declare work done, instead of decoupling the team's own logic and keeping the impediment visible.

Full explanation →

217

MCQhard

The organization wants to move from monthly releases to continuous delivery. What is the most important technical requirement for this transition?

A.Hire more developers.

B.Implement automated build and testing pipelines.

C.Lower the security standards.

D.Stop all documentation.

AnswerB

Automated build and testing pipelines remove the manual verification bottleneck that makes monthly releases feasible, enabling code to be validated and deployed on demand. This directly satisfies the continuous delivery constraint: every change must be releasable to production at any time, which requires repeatable, automated quality gates rather than scheduled manual testing cycles.

Why this answer

Continuous delivery requires that every code change can be automatically built, tested, and deployed to production-like environments with confidence. Automated build and testing pipelines (CI/CD) are the foundational technical enabler — without them, frequent releases introduce unacceptable risk and manual error. This is the core technical prerequisite for moving from monthly to continuous delivery.

Exam trap

The trap is confusing continuous delivery with continuous deployment — CD requires automation, but candidates sometimes pick 'hire more people' thinking scale solves the problem, when the real bottleneck is manual process.

How to eliminate wrong answers

Option A is wrong because adding developers without automation increases coordination overhead and does not address the release bottleneck — it can even slow delivery (Brooks's Law). Option C is wrong because lowering security standards is never an acceptable trade-off; continuous delivery actually requires stronger automated security checks (DevSecOps). Option D is wrong because documentation is still valuable in Agile — stopping it entirely creates knowledge silos and compliance risk; the goal is lightweight, automated documentation where possible.

Full explanation →

218

Multi-Selecthard

Which TWO leadership actions help resolve a conflict regarding technical architecture? (Choose TWO)

Select 2 answers

A.Encouraging the team to experiment with both options in a time-boxed sprint.

B.Asking the highest-paid person to make the decision.

C.Facilitating a data-driven evaluation of the proposed architectures.

D.Imposing your own preferred architecture to end the debate.

E.Letting the conflict continue until one side gives up.

AnswersA, C

A time-boxed experiment lets the team generate real evidence about each architecture's trade-offs instead of debating opinions. It satisfies the conflict constraint by converting an abstract disagreement into observable results, after which the team can decide on demonstrated behaviour rather than seniority or persuasion.

Why this answer

Option A is correct because encouraging the team to experiment with both options in a time-boxed sprint creates empirical evidence about each architecture's trade-offs (performance, complexity, integration effort) rather than relying on opinion, which is a constructive, leadership-driven way to resolve technical conflict. Option C is correct because facilitating a data-driven evaluation—using agreed criteria such as scalability, latency, cost, security, and maintainability—gives the team an objective basis for consensus and removes the conflict from personal preference. Option B is not appropriate because deferring to the highest-paid person substitutes authority for technical merit and does not resolve the underlying architectural disagreement.

Option D is not appropriate because imposing a preferred architecture ends debate by fiat, damaging trust and ownership. Option E is not appropriate because letting the conflict continue until one side gives up allows unresolved technical risk and team dysfunction to persist.

Exam trap

PMI-ACP often tests the distinction between Agile servant leadership and traditional command-and-control; candidates may incorrectly choose B or D because they confuse 'resolving conflict' with making a quick decision by authority, rather than facilitating team collaboration and empirical decision-making.

Full explanation →

219

MCQeasy

Which visual tool is best suited for identifying bottlenecks in a team's workflow?

A.Budget report.

B.Gantt chart.

C.Pie chart of tasks.

D.Kanban board.

AnswerD

A Kanban board maps each workflow stage as a column, exposing where work items accumulate and stall. By applying work-in-progress limits per column, it directly reveals the bottleneck stage constraining throughput, satisfying the need to identify flow constraints visually rather than tracking effort or dependencies.

Why this answer

A Kanban board is the visual management tool specifically designed to expose workflow states and surface bottlenecks. By displaying work items as cards moving through columns representing process stages, it makes accumulation of work-in-progress (WIP) at any stage immediately visible. When cards pile up in one column, that column is the bottleneck, enabling the team to apply WIP limits or swarm to resolve it.

Exam trap

The trap here is confusing general project-visualization tools (Gantt, pie charts) with flow-based tools; PMI-ACP often tests whether candidates recognize that bottleneck identification requires a workflow-state view, not a schedule or financial view.

How to eliminate wrong answers

Option A is wrong because a budget report tracks financial expenditure against plan and provides no visibility into workflow flow or process stages. Option B is wrong because a Gantt chart shows schedule dependencies and task durations over time, which is a predictive/planning view rather than a flow-based bottleneck detector. Option C is wrong because a pie chart of tasks only shows proportional distribution of task categories or counts, not the movement or accumulation of work through a process.

Full explanation →

220

MCQeasy

A team is struggling with frequent interpersonal conflict during daily stand-ups. As an agile leader, what is your primary role in facilitating this?

A.Cancel the daily stand-up until the team matures.

B.Facilitate a session to help the team establish team norms and communication protocols.

C.Report the conflict to the functional manager to handle disciplinary action.

D.Force the individuals to move to different squads.

AnswerB

Establishing team norms and communication protocols gives the team shared, explicit expectations for stand-up behaviour, addressing the root cause of recurring interpersonal friction rather than suppressing individual incidents. The agile leader facilitates this agreement; the team owns and enforces it.

Why this answer

As an agile leader, the primary role is to facilitate the team's self-organization by helping them establish team norms and communication protocols. This addresses the root cause of conflict and builds a healthier team dynamic. It empowers the team to resolve issues collaboratively rather than relying on external authority.

Exam trap

PMI-ACP often tests the misconception that agile leaders should resolve conflicts by escalating or making decisions for the team, when they should instead facilitate team self-organization and norm-setting.

How to eliminate wrong answers

Option A is wrong because canceling the daily stand-up avoids the problem and deprives the team of a key inspection and synchronization event, which is contrary to agile principles. Option C is wrong because escalating to a functional manager for disciplinary action undermines team self-management and treats a systemic issue as an individual problem. Option D is wrong because forcing individuals to move squads is a punitive, top-down action that does not address the underlying conflict and disrupts team stability.

Full explanation →

221

MCQmedium

A team is using cumulative flow diagrams to identify bottlenecks. The chart shows a widening gap between the 'In Progress' and 'Done' states. What does this indicate?

A.The team is highly efficient.

B.The sprint is ahead of schedule.

C.There is a bottleneck preventing work from moving to 'Done'.

D.The team has stopped working.

AnswerC

A widening band between 'In Progress' and 'Done' on a cumulative flow diagram directly signals accumulating work-in-progress, meaning items enter the active state faster than they exit. This vertical expansion of the in-progress band is the standard CFD indicator of a downstream bottleneck constraining throughput, exactly the constraint the stem describes.

Why this answer

A cumulative flow diagram (CFD) plots the count of work items in each workflow state over time. When the band representing 'In Progress' widens while 'Done' stays flat or grows slowly, work is entering the active state faster than it is being completed. This accumulation of work-in-progress (WIP) is the classic visual signature of a bottleneck downstream of 'In Progress' — typically in review, testing, or deployment — that is throttling the flow of items into 'Done'.

Exam trap

PMI-ACP often tests whether candidates can read CFD band geometry — the trap is confusing a widening band (WIP accumulation/bottleneck) with a rising top line (scope growth) or flat lines (work stoppage).

How to eliminate wrong answers

Option A is wrong because high efficiency would show all bands moving in parallel with 'Done' growing at the same rate as 'In Progress', not a widening gap. Option B is wrong because being ahead of schedule would mean 'Done' is accumulating faster than planned, which is the opposite of a widening In Progress band. Option D is wrong because a stopped team would show flat horizontal lines across all bands, not a widening In Progress band with continued intake.

Full explanation →

222

MCQeasy

A stakeholder is providing feedback directly to the developers, bypassing the PO. What should you do?

A.Coach the stakeholder on the importance of the PO's role and redirect them to the PO.

B.Encourage the developers to follow the stakeholder's instructions.

C.Tell the developers to ignore the stakeholder entirely.

D.Ask the developers to report the stakeholder to HR.

AnswerA

Redirecting feedback through the Product Owner preserves the single backlog-prioritisation channel and prevents developers receiving conflicting direction. Coaching the stakeholder explains why the PO owns value ordering, protecting the team's focus. This addresses the bypass directly rather than escalating or ignoring the behaviour.

Why this answer

The Product Owner is the single point of accountability for the product backlog and its prioritization, so feedback that bypasses the PO undermines that role and risks the team building unprioritized work. Coaching the stakeholder on why the PO exists and redirecting them preserves the PO's authority while keeping the stakeholder engaged through the correct channel.

Exam trap

The trap here is the instinct to 'protect' the team by telling developers to ignore the stakeholder — PMI-ACP wants the servant-leader response of coaching and redirecting to the PO, not shutting the stakeholder out.

How to eliminate wrong answers

Option B is wrong because telling developers to follow the stakeholder's instructions directly creates competing sources of priority, destroys the PO's ability to sequence the backlog, and leads to scope creep and conflicting work. Option C is wrong because telling developers to ignore the stakeholder entirely is dismissive and damages the relationship — the stakeholder's input may be valid, it just needs to flow through the PO. Option D is wrong because escalating to HR treats a process/role-clarity issue as a personnel matter, which is disproportionate and would poison the working relationship rather than fix the channel.

Full explanation →

223

Multi-Selecthard

Which THREE strategies can a leader use to empower a self-organizing team? (Choose THREE)

Select 3 answers

A.Trust the team to make their own technical and process decisions.

B.Dictate the team's schedule and daily working hours.

C.Set clear objectives and constraints, then let the team decide how to meet them.

D.Provide the necessary resources and remove organizational impediments.

E.Approve every task assignment to ensure it is handled correctly.

AnswersA, C, D

Trusting the team to make their own technical and process decisions directly enables self-organisation, satisfying the stem's empowerment requirement. Authority over both technical and process choices shifts from leader to team, which is the defining mechanism of self-organising teams in agile practise. Without delegated decision rights, empowerment remains nominal.

Why this answer

Option A is correct because empowering a self-organizing team requires the leader to trust the team to make their own technical and process decisions, which builds ownership and autonomy rather than dependence on the leader. Option C is correct because setting clear objectives and constraints while letting the team decide how to meet them gives direction without prescribing the method, which is the essence of empowerment in self-organizing teams. Option D is correct because providing necessary resources and removing organizational impediments creates the supportive environment the team needs to self-organize effectively, a core servant-leadership behavior.

Option B is incorrect because dictating schedule and daily working hours imposes control and reduces the team's autonomy. Option E is incorrect because approving every task assignment is micromanagement that undermines self-organization and team ownership.

Exam trap

PMI-ACP often tests the boundary between supportive leadership and micromanagement, tempting candidates to select answers that retain control under the guise of ensuring quality.

Full explanation →

224

MCQmedium

A stakeholder wants to change the project priority halfway through the project. What is the practitioner's role?

A.Help the Product Owner assess the impact and update the product backlog.

B.Immediately implement the change.

C.Refuse the change.

D.Tell the stakeholder to wait until the project ends.

AnswerA

The practitioner's role is to surface the impact of the priority shift, not to accept or reject it. Helping the Product Owner assess consequences and reorder the product backlog keeps prioritisation with the PO, satisfying the constraint that scope decisions remain a product-ownership responsibility rather than a team or stakeholder one.

Why this answer

In Agile, the Product Owner owns the product backlog and its prioritization. When a stakeholder requests a priority change, the practitioner's role is to help the Product Owner assess the impact (on scope, schedule, value) and update the backlog accordingly, preserving the PO's authority and the team's focus.

Exam trap

PMI-ACP often tests the boundary between stakeholder requests and Product Owner authority, so the trap is selecting 'implement immediately' (appearing responsive) instead of routing through the PO with impact analysis.

How to eliminate wrong answers

Option B is wrong because immediately implementing the change bypasses the Product Owner's ownership of the backlog and ignores impact analysis, risking disruption to the sprint goal. Option C is wrong because refusing the change outright is inflexible and contradicts Agile's embrace of changing requirements for competitive advantage. Option D is wrong because telling the stakeholder to wait until the project ends ignores the value of iterative delivery and may forfeit a legitimate business opportunity.

Full explanation →

225

Multi-Selecthard

A product owner keeps adding new backlog items mid-iteration, and the team's cycle time has doubled over three iterations even though capacity is unchanged. Which two actions should the practitioner take to improve delivery flow? (Choose two.)

Select 2 answers

A.Establish and enforce a clear iteration scope agreement so the team finishes committed work before pulling new items.

B.Remove the iteration boundary and let the team continuously pull items as the product owner prioritizes them.

C.Ask the team to work overtime temporarily to absorb the additional backlog items.

D.Make the impact of mid-iteration scope changes visible by tracking cycle time and work in progress on a cumulative flow diagram.

E.Increase the team's story point estimates so the added items fit within the iteration.

AnswersA, D

Mid-iteration scope injection is a classic source of flow degradation because it forces context switching and leaves multiple items partially done. Agreeing that the team completes its committed work before accepting new items limits work in progress, shortens cycle time, and gives the product owner a predictable channel for new requests in the next planning event.

Why this answer

Cycle time doubling with stable capacity points to too much work entering the system at once. Limiting mid-iteration injections and making the resulting work-in-progress buildup visible with a cumulative flow diagram both reduce multitasking and give the product owner evidence to prioritize differently, which restores flow without inflating estimates or burning out the team.

Exam trap

The trap here is responding to added scope by increasing capacity or estimates, rather than limiting the work entering the system and making its flow impact visible.

Full explanation →

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