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

Pair and mob programming force continuous verbalisation and shared code ownership, so knowledge transfers across the whole team rather than residing with individuals. This directly removes the siloed working that blocks collaboration, satisfying the stem's requirement for activities a leader can facilitate.

The Daily Stand-up is a short, timeboxed Scrum event where members share progress, plans and impediments, synchronising work and surfacing blockers early. This directly satisfies the stem's purpose, enabling rapid impediment removal rather than status reporting to management.

Technical debt arguments stall because positions harden without shared data. Facilitating a discussion that links debt to velocity and quality metrics gives the team objective evidence, then lets them agree a sustainable repayment approach — satisfying the stem's need for the agile lead to facilitate rather than decide.

Defining the sprint goal gives the iteration a single cohesive objective, aligning the team and guiding trade-off decisions during the sprint. It satisfies sprint planning's purpose of establishing a shared, negotiable target that focuses the team's work for the iteration.

This action reflects Agile mindset by embracing uncertainty and using iterative delivery to learn. Delaying irreversible decisions until more is known, while still delivering value, is a core Agile principle often called 'last responsible moment.' It allows the team to adapt based on feedback and reduce risk, rather than committing prematurely.

Working software over comprehensive documentation is one of the four values in the Agile Manifesto, prioritising demonstrable, functioning increments over exhaustive written specifications. This directly satisfies the stem's requirement for a core Agile value, distinguishing it from Agile principles or general project-management practises that lack Manifesto status.

The Product Owner owns backlog ordering and trade-offs, so routing the mid-sprint request there preserves the sprint commitment while letting value be weighed against existing work. The practitioner should not unilaterally insert scope, which would undermine the team's agreed sprint goal.

An oversized backlog becomes unnavigable: items lose visibility, prioritisation degrades, and lower-value entries linger indefinitely. This directly violates the agile principle of a lean, ordered backlog refined continuously, so it qualifies as a recognised backlog management pitfall.

Cycle time is a team-level flow metric, so the retrospective is where the team inspects its own process data and identifies systemic causes. Discussing the three-sprint trend there engages those closest to the work, satisfying the need to find root cause before prescribing changes.

Introducing varied retrospective formats disrupts habitual thinking, while outside observers supply perspectives the team cannot generate internally. This directly counters complacency by injecting novelty and external input, satisfying the stem's need to restart improvement-seeking behaviour during retrospectives.

This action aligns with the Agile mindset by fostering self-organization, which is a core principle of Agile. The manager's current behavior reflects command-and-control, and coaching them to enable team autonomy helps the team take ownership, make decisions, and collaborate effectively. This shift supports intrinsic motivation and faster feedback loops, which are essential for Agile success.

Cost of delay combines value and time sensitivity. The regulatory feature has a hard external deadline, so its cost of delay rises steeply and dominates the comparison, even if the delight feature has greater raw value. Sequencing the compliance work first protects the organization from penalties and preserves the option to deliver delight value afterward, which is the economically rational ordering.

Servant leadership develops the team rather than directing it. Facilitating a collaborative decision-making session transfers technical ownership from the single senior developer to the whole team, building shared accountability and psychological safety. This directly addresses the over-reliance constraint by growing collective capability instead of imposing a solution.

The delay is a scope-versus-schedule trade-off affecting cost, risk and value, so the decision belongs to those accountable for business outcomes. Presenting the trade-off lets stakeholders weigh the feature's worth against the two-week slip transparently.

Explaining the long-term cost of quick fixes and negotiating a sustainable pace addresses the root cause: the stakeholder's demands bypass quality processes. This satisfies the stem's constraint by protecting quality while maintaining stakeholder collaboration, rather than simply refusing or silently complying.

INVEST defines six quality criteria for user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. This directly answers the stem's request for the model's description, matching the acronym's exact terms. No other option enumerates these attributes, so it satisfies the question precisely.

A concise, easily understood vision communicates direction without ambiguity, letting the team and stakeholders grasp the product's purpose quickly. This satisfies the question's requirement for a defining characteristic, since brevity supports shared understanding and guides decisions throughout iterative delivery.

Lead Time measures the elapsed duration from a request being made to its delivery, capturing queueing and waiting waste across the whole value stream. This end-to-end visibility satisfies the stem's requirement for metrics that expose and help mitigate delivery waste.

Backlog grooming directly restores alignment by re-ranking items against current business value, satisfying the stem's constraint that delivered features no longer match organisational priorities. Engaging stakeholders in that session ensures the revised order reflects their priorities, so subsequent iterations deliver the highest-value work first.

The sprint review is designed to inspect the increment and adapt the backlog based on stakeholder feedback. Treating the dissatisfaction as valuable input and updating the product backlog reflects the Agile mindset of embracing change and delivering value. It turns a perceived failure into a learning opportunity and keeps the focus on the customer, which is exactly what the review is for.

Automated testing catches regressions on every commit, while continuous integration merges and verifies code frequently, exposing integration defects before release. This directly addresses the stem's post-release defect volume by shifting detection earlier, satisfying the need for a repeatable quality gate rather than relying on manual end-of-cycle testing.

A sprint goal must be clear and concise so every team member can state, without ambiguity, what the sprint intends to achieve and whether the selected backlog items serve it. That shared, memorable focus guides daily trade-off decisions and underpins meaningful inspection at the sprint review.

Oversized, ambiguous stories hide complexity and stall completion. Splitting them into smaller, clearer slices shortens feedback loops, exposes blockers earlier and lets the team deliver incrementally, which is the empirical, self-organising behaviour an Agile mindset requires.

Peer review is a quality gate applied to every increment, so it belongs in the Definition of Done as a consistently enforced criterion rather than a per-story choice. It satisfies the stem's demand for items applying uniformly across all work, distinguishing shared completion standards from acceptance criteria that vary by backlog item.

Time-boxing the decision forces the team to converge within a fixed window, preventing endless debate. The practitioner facilitates by clarifying options, surfacing dissent and driving consensus before the timer expires, so decision paralysis yields to forward progress without sacrificing team input.

Agile protects the sprint goal rather than freezing scope, so the team and product owner jointly assess whether the new requirement supports that goal before accepting it. This satisfies the stem by evaluating the change collaboratively instead of rejecting or silently absorbing it.

This action directly addresses the imbalance in participation by creating a structure that ensures everyone has an opportunity to contribute. It also models inclusive behavior, which helps rebuild psychological safety. While it may be combined with a private conversation, the structured approach is the most effective immediate action to restore collaborative problem-solving. It shifts the focus from blaming one individual to improving the team's process and culture.

Frequent demonstrations of working software give stakeholders tangible, incremental visibility of delivered functionality, letting them validate progress and course-correct early. This recurring feedback loop keeps expectations and priorities aligned throughout the project, satisfying the stem's requirement for ensuring stakeholder alignment.

The Sprint Burndown chart plots remaining work against time within the sprint, directly showing whether the team is on track to meet the sprint goal. It satisfies the stem's requirement for tracking progress towards that goal, unlike product-level or release-level artefacts, which measure broader scope beyond the current sprint.

Structured activities and retrospectives create repeated, low-risk interactions where members disclose concerns and build mutual reliability. This directly cultivates the openness and psychological safety a newly formed team needs before trust can emerge through shared delivery.

The product backlog is the single ordered list of all work not yet done, so a discovered bug is added there and prioritised by the Product Owner alongside other items. Sprint backlogs are fixed once the sprint starts, so only the product backlog can absorb it.

Command-and-control leadership directly blocks self-organisation by retaining decision-making authority, so the team cannot choose how to execute its own work. Self-organisation requires the team to own task allocation and process decisions; when leaders dictate these, the team merely executes instructions, which satisfies the stem's constraint of failed self-organisation.

Facilitating discussions embeds technical debt as a first-class backlog item, so remediation work competes for sprint capacity alongside features. This satisfies the stem's constraint of leader support by making debt visible and deliberately scheduled, rather than letting it accumulate invisibly outside planning.

Small, low-pressure contributions lower the psychological risk that silences hesitant members, letting them build confidence gradually. Acknowledging each input reinforces the behaviour, directly addressing the coaching need in the stem rather than forcing participation in larger forums.

One Product Owner with a single unified backlog gives all three teams a shared priority order, preventing divergent roadmaps. This satisfies the coordination constraint by aligning what each team builds toward one product vision rather than competing backlogs.

Facilitating a discussion targets the root cause: the team's estimation criteria and definition of 'done' are too loose, so work is counted as complete prematurely. Retrospective reflection lets the team recalibrate relative sizing against actual effort, directly addressing the recurring sprint overrun rather than masking it with padding.

Agile teams embrace responding to change over following a plan. Pivoting the technical approach once evidence shows it will not work, and immediately informing the Product Owner of schedule or scope impact, keeps the increment valuable and the backlog transparent.

Training plus protected time to experiment directly addresses the skill gap and resistance causing the struggle. People adopt unfamiliar tooling through guided practise and iteration, not mandates, so this builds competence and ownership faster than forcing immediate compliance.

Raising the behaviour in a retrospective lets the team discuss focus and participation norms collectively, avoiding singling out the individual and reducing defensiveness. The team then owns the working agreement, which is more likely to change behaviour than a private reprimand from the agile leader.

Transparency and honest communication let teams surface impediments, risks and bad news early, which is precisely the psychological-safety signal a healthy Agile culture depends on. Without it, status reporting becomes theatre and empirical inspection fails. This directly satisfies the stem's requirement for a cultural health indicator rather than a process artefact.

A private conversation lets the facilitator raise the behaviour's impact on psychological safety without publicly shaming the critic, which would harden defensiveness. Addressing it one-to-one preserves the team's safe retrospective space while giving the individual a chance to adjust, directly satisfying the goal of improving psychological safety.

Velocity measures completed work per iteration, not individual productivity. When treated as a performance target, teams inflate estimates or game scope to hit numbers, destroying its forecasting value. The team's fear reflects this misuse risk, so they withhold it to protect honest planning.

Articulating the rationale connects the change to business or customer outcomes, giving the team a purpose beyond compliance. This satisfies the coaching approach requirement by reducing resistance rooted in ambiguity, so team members can commit to the new way of working.

Agile teams address risk continuously because each iteration surfaces new information, changing the risk profile. Risk management is embedded in ceremonies such as daily stand-ups, retrospectives and iteration reviews, satisfying the stem's requirement for ongoing identification and response rather than a single upfront phase.

High velocity with declining quality signals accumulating technical debt caused by treating speed as the sole metric. Coaching the team and stakeholders on sustainable development rebalances delivery pace against maintainability, addressing the root cause rather than suppressing velocity or ignoring quality.

Valuing collaboration over individual silos reflects the Agile mindset's emphasis on cross-functional teamwork and collective ownership, directly satisfying the stem's requirement for a hallmark. Agile practise prioritises shared accountability and continuous communication over departmental isolation, enabling self-organising teams to deliver value iteratively rather than through handoffs between separate functions.

Agile success is judged by outcomes—working solutions that deliver value and satisfy the customer—not by internal plan conformance. Tracking customer satisfaction and value delivered through frequent releases aligns with the Agile mindset of early and continuous delivery. It keeps the focus on the customer and on tangible results, which is exactly what a transitioning organization needs to reinforce.

Reviewing retrospective notes targets the root cause of the 20% velocity drop by surfacing systemic blockers, such as unresolved impediments or process friction, rather than reacting to the symptom. This satisfies the stem's "first" constraint: inspect before adapting, consistent with the Agile principle of reflecting and adjusting at regular intervals.

Technical debt represents genuine work requiring capacity, so listing it in the backlog alongside features lets the product owner prioritise it transparently against customer value. This satisfies the stem's refinement constraint by making debt visible and tradeable rather than hidden, preventing unplanned rework from silently eroding velocity in later sprints.

The Product Vision articulates the long-term purpose and goal of the product, giving the team and stakeholders a shared destination that guides backlog prioritisation and release decisions. It is not a detailed requirements list or sprint plan; it provides enduring direction across the product's life.

Delivering a working increment frequently and seeking feedback embodies the principle of early and continuous delivery of valuable software. It demonstrates that the team values tangible results and customer collaboration over comprehensive documentation or internal progress reports. This behavior shows the mindset is focused on learning and value, not just on completing activities.

Servant leaders prioritise the team's ability to deliver by clearing blockers, so removing impediments that stop work directly satisfies the stem's requirement. This unblocking behaviour is the defining operational act of servant leadership, shielding the team and enabling flow rather than directing tasks.

With the date fixed and non-negotiable, schedule and cost are constrained, leaving scope as the only flexible variable. Agile teams protect the deadline by prioritising the highest-value features and deferring or dropping lower-priority work, delivering maximum business value within the immovable timeframe.

Value stream mapping exposes every step between request and delivery, revealing queues, handoffs and rework that inflate lead time. Eliminating those non-value-added activities directly shortens the end-to-end flow the stem describes, rather than optimising individual functions in isolation.

WIP limits cap concurrent work in progress, preventing the team from starting more items than it can finish and exposing bottlenecks early. This directly sustains pace by eliminating the overload and context switching that erode throughput over time.

A collaborative review lets the team clarify, tighten and agree the Definition of Done so it is consistently applied. This directly addresses the stem's inconsistent application and resulting technical debt by removing ambiguity through shared ownership rather than imposing a mandate.

A servant leader shields the team from external pressures and interference, restoring autonomy and morale. Acting as a buffer directly counters the micromanagement causing low morale, satisfying the stem's requirement for the servant leader's primary role in this situation.

Prioritising shared goals and understanding directly satisfies the agile value of customer collaboration, which favours ongoing dialogue with the customer over rigid contractual terms. This enables iterative feedback and adaptive scope, whereas strict contract negotiation fixes requirements upfront and undermines the responsiveness that agile delivery demands.

Technical debt is work, so it belongs in the product backlog alongside features and is prioritised by the Product Owner with the team. This keeps it visible, lets the team trade it against new scope each sprint, and avoids hidden side work that undermines sustainable pace.

Responding to change over following a plan means the team should collaborate with the customer to pivot and adapt, rather than delivering against an outdated plan. This satisfies the scenario's constraint that the original plan no longer meets current user needs, keeping the product valuable.

Fixed scope removes the team's ability to absorb change, so any new requirement forces renegotiation or rework. Quantifying that cost in money and delay gives the stakeholder concrete evidence that flexibility on scope protects budget and schedule, satisfying the demand to demonstrate an Agile mindset.

An MVP ships the smallest increment that lets real users test the underlying hypothesis, converting assumptions into validated learning. This produces meaningful outcomes because feedback from actual usage, not internal output metrics, determines whether the product delivers value and guides the next iteration.

A retrospective is a recurring inspect-and-adapt event where the team examines how it worked, identifies impediments and agrees improvements to its process and collaboration. It targets the team's way of working, not the product backlog or individual performance.

The Sprint Review is an inspect-and-adapt event centered on the working product increment. Demonstrating the increment and letting stakeholders interact with it produces concrete feedback that the Product Owner uses to update the product backlog. This collaborative, transparent approach embodies agile product management and keeps stakeholders engaged in shaping value rather than approving paperwork.

Collaborative decision-making gives stakeholders genuine influence over outcomes, building ownership and surfacing constraints early. This satisfies the engagement criterion by making stakeholders participants in shaping the product rather than recipients of decisions made elsewhere, which sustains commitment across the delivery lifecycle.

WIP limits should be set around the workflow's constrained steps, because limiting work elsewhere merely shifts the queue to the bottleneck. Identifying bottlenecks first lets the practitioner cap WIP at the slowest stage, exposing the real constraint and driving improvement there rather than at unconstrained stages.

Independence lets a story be developed, tested and accepted on its own, satisfying the INVEST criterion that prevents scheduling and prioritisation being blocked by another story's unfinished work. This decoupling reduces coordination overhead and enables the team to deliver value incrementally within an iteration.

Coaching shifts the leader from pushing assignments to enabling pull-based self-organisation, directly addressing the stem's constraint: the leader monopolising task allocation. Explaining why teams that pull work commit more deeply builds intrinsic motivation, so authority gradually transfers to the team rather than being seized or abandoned abruptly.

This response recognizes the team's demonstrated capability and readiness for greater autonomy while ensuring they understand the boundaries within which they operate. By clarifying boundaries and providing support, you enable the team to take on more responsibility safely. This is a balanced approach that fosters self-organization and aligns with servant leadership principles. It also maintains the necessary connection to organizational goals and stakeholder needs.

Command and control concentrates authority in managers; pushing decisions to those closest to the work shortens feedback loops and removes approval bottlenecks. This directly shifts authority downward, satisfying the move toward an Agile mindset rather than merely renaming roles.

An Agile mindset fosters shared ownership and open communication, directly improving team collaboration and satisfaction. This satisfies the stem's requirement for a benefit by addressing the human and social dimensions of delivery, rather than process artefacts or tooling. Cross-functional, self-organising teams report higher morale because they control their own work.

Shared digital Kanban boards give distributed teams a single, real-time visual source of truth, replacing physical task walls that co-location would otherwise provide. This directly satisfies the stem's distributed constraint by making work-in-progress, blockers and ownership visible asynchronously across time zones, sustaining the transparency agile communication depends on.

Reinforcing the Definition of Done anchors the team member to the agreed acceptance criteria, making unrequested features visibly out of scope. Gold-plating violates the "no extra work" principle, so framing it against the current sprint goal redirects effort toward delivering exactly what was committed, satisfying the constraint that scope must match stakeholder requirements.

A dedicated enabler team or infrastructure service-level agreement removes the cross-team dependency that repeatedly blocks delivery, addressing the delays at organisational rather than team level. This satisfies the stem's requirement for an organisational-level fix rather than local workarounds.

Continuous improvement targets the process itself, not just the product, so retrospectives feed small iterative changes that compound into better delivery efficiency. This directly satisfies the stem's goal of enhancing processes and delivery efficiency over time, rather than merely fixing defects or adding features.