PMI Agile Certified Practitioner (PMI-ACP), 2024-revamped exam outline (PMI-ACP) PMI-ACP Questions 226–244 | Page 4/4

226

MCQeasy

Why do we value 'individuals and interactions over processes and tools'?

A.Processes are useless.

B.Individuals should ignore processes.

C.We don't need tools.

D.People are more important than the tools they use.

AnswerD

Agile prioritises people because software is built by collaborating humans, not by tooling alone. Processes and tools support delivery, but they cannot replace communication, shared understanding and rapid feedback. Valuing individuals and interactions keeps teams adaptive when requirements change, which tools alone cannot achieve.

Why this answer

The Agile Manifesto values individuals and interactions over processes and tools because working software and customer collaboration depend on people communicating effectively, and no process or tool can substitute for that. It does not mean processes and tools are worthless; it means when there is a conflict, prioritize people and direct communication. This principle underpins self-organizing teams and face-to-face conversation as the most efficient way to convey information.

Exam trap

PMI-ACP often tests the literal misreading of the manifesto's values; the trap is interpreting 'over' as 'instead of' and selecting an extreme option that dismisses processes or tools entirely.

How to eliminate wrong answers

Option A is wrong because the manifesto does not say processes are useless; it says processes and tools are valuable but less valuable than individuals and interactions when trade-offs arise. Option B is wrong because individuals should not ignore processes; they should use processes that support them and adapt when processes get in the way. Option C is wrong because tools are not unnecessary; they are useful enablers, but they should not replace human collaboration and judgment.

Full explanation →

227

MCQeasy

What is the best way to handle a team member who is not adhering to the agile values?

A.Provide consistent, private feedback and coaching to help them understand and adopt the values.

B.Shame them in the daily stand-up.

C.Ignore the behavior, as everyone has their own way of working.

D.Remove them from the team immediately.

AnswerA

Private, consistent coaching addresses the behaviour directly without humiliating the individual, helping them understand why the agile values matter and adopt them. This preserves team trust and psychological safety, which public criticism or escalation would undermine, making it the most effective corrective approach.

Why this answer

The correct answer is A because providing consistent, private feedback and coaching is the most constructive way to help a team member understand and adopt agile values. This approach respects the individual, fosters psychological safety, and aligns with the servant-leader role of an agile practitioner. It addresses the behavior directly while supporting the team member's growth.

Exam trap

PMI-ACP often tests conflict resolution and team development; candidates may incorrectly choose punitive or avoidant actions, missing that coaching and private feedback are the agile-preferred approaches.

How to eliminate wrong answers

Option B is wrong because shaming in a public forum is destructive, erodes trust, and violates agile's emphasis on respect and safety. Option C is wrong because ignoring the behavior allows it to persist and undermines team cohesion and agile adoption. Option D is wrong because immediate removal is an extreme, punitive measure that should be a last resort after coaching and feedback have failed, and it may not address the root cause.

Full explanation →

228

MCQmedium

A practitioner wants to improve team engagement during the retrospective. What technique should they use?

A.Strict time-keeping by a manager.

B.Mandatory silent reading.

C.Annual performance reviews.

D.'Start, Stop, Continue' activity.

AnswerD

'Start, Stop, Continue' gives every member a structured, low-risk prompt to voice observations across three dimensions, surfacing improvement actions without blame. This directly raises participation and psychological safety, satisfying the goal of improving team engagement during the retrospective.

Why this answer

'Start, Stop, Continue' is a structured retrospective activity that actively engages team members by having them brainstorm and discuss what they should start doing, stop doing, and continue doing. It promotes participation and ownership, directly improving engagement during the retrospective.

Exam trap

PMI-ACP often tests the misconception that management-driven control techniques (like strict time-keeping or performance reviews) improve team engagement, when Agile facilitation focuses on collaborative, team-owned activities.

How to eliminate wrong answers

Option A is wrong because strict time-keeping by a manager can stifle open discussion and does not improve engagement — it may even reduce psychological safety. Option B is wrong because mandatory silent reading is passive and does not encourage active participation or collaboration. Option C is wrong because annual performance reviews are unrelated to retrospective engagement and are typically a top-down, non-Agile practice.

Full explanation →

229

MCQmedium

A team is struggling with frequent context switching. As a servant leader, what is the best first step to foster an Agile mindset regarding focus?

A.Implement mandatory overtime to finish tasks.

B.Mandate daily status reports to the PMO.

C.Assign specific tasks to individuals without team input.

D.Introduce WIP limits at the team level.

AnswerD

WIP limits directly cap concurrent work, forcing the team to finish before starting and thereby reducing context switching. This addresses the stem's constraint — frequent task interleaving — by making focus a structural property of the workflow rather than relying on individual discipline, which aligns with servant-leadership enabling the team's Agile mindset.

Why this answer

Introducing WIP (Work In Progress) limits at the team level is a direct Kanban/Agile practice that reduces context switching by capping the number of concurrent items. As a servant leader, the best first step is to foster this mindset through a lightweight, team-owned mechanism rather than imposing controls.

Exam trap

PMI-ACP often tests servant leadership versus directive management, so the trap is choosing a control-oriented action (overtime, status reports, task assignment) instead of a team-empowering practice like WIP limits.

How to eliminate wrong answers

Option A is wrong because mandatory overtime is a command-and-control tactic that increases burnout and does not address the root cause of context switching. Option B is wrong because mandating daily status reports to the PMO adds administrative overhead and reinforces top-down control, contrary to servant leadership. Option C is wrong because assigning tasks to individuals without team input undermines self-organization and does not inherently reduce context switching.

Full explanation →

230

MCQhard

The team is feeling burned out. What is your role as a leader?

A.Work with the team to identify the causes of burnout and adjust their workload and processes accordingly.

B.Ask them to work harder to finish the project sooner.

C.Tell the team to take more breaks.

D.Tell the team to be more resilient.

AnswerA

Burnout stems from systemic causes such as unsustainable workload or flawed processes, so a leader must diagnose those root causes with the team rather than apply surface fixes. Adjusting workload and process addresses the actual driver, restoring sustainable pace.

Why this answer

The leader's role in addressing burnout is to work with the team to identify root causes and adjust workload and processes accordingly, because burnout is a systemic issue, not an individual failing. This approach aligns with agile principles of sustainable pace and servant leadership, where the leader facilitates solutions rather than prescribing them. By involving the team in diagnosis and remediation, the leader empowers them and addresses the underlying drivers of burnout.

Exam trap

PMI-ACP often tests the misconception that resilience or breaks are sufficient solutions to burnout — the correct answer always involves systemic diagnosis and adjustment of workload and processes with the team.

How to eliminate wrong answers

Option B is wrong because asking the team to work harder directly contradicts the principle of sustainable pace and will exacerbate burnout, leading to decreased quality and increased turnover. Option C is wrong because telling the team to take more breaks is a superficial fix that does not address the root causes of burnout, such as unrealistic deadlines, unclear priorities, or excessive workload. Option D is wrong because telling the team to be more resilient places the burden on individuals and ignores the leader's responsibility to create a healthy work environment and remove systemic impediments.

Full explanation →

231

MCQhard

A senior manager tells an Agile team that they must adopt a new estimation technique and a specific tool immediately because 'that is how Agile is done here.' The team is uncomfortable but compliant. As the PMI-ACP practitioner, what is the most appropriate action to support an Agile mindset?

A.Ensure the team follows the mandate precisely so the organization has consistent data.

B.Coach the manager on self-organization and help the team evaluate the technique and tool against their context.

C.Escalate the conflict to HR because the manager is violating Agile principles.

D.Quietly tell the team to ignore the mandate and continue working as they prefer.

AnswerB

The Agile mindset holds that self-organizing teams choose how to do their work, and the practitioner's role includes coaching leaders toward that understanding. Helping the team evaluate the mandate against their context respects both the manager's intent and the team's autonomy. It also creates a feedback loop where the team can adopt, adapt, or reject based on evidence, which is the essence of continuous improvement.

Why this answer

An Agile mindset requires that teams self-organize and choose their own practices, while leaders are coached to support rather than dictate. The practitioner should coach the manager on self-organization and help the team evaluate the mandated technique and tool against their actual context. Enforcing the mandate, escalating punitively, or encouraging covert non-compliance all fail to address the underlying mindset and damage the trust needed for a sustainable Agile transformation.

Exam trap

The trap here is choosing between blind compliance and quiet rebellion, when the Agile-aligned path is transparent coaching of the leader combined with team-led evaluation.

Full explanation →

232

Multi-Selectmedium

An agile leader is coaching a team that has strong technical skills but consistently avoids raising impediments during daily stand-ups. The leader suspects that fear of blame is suppressing transparency. Which TWO actions best demonstrate servant leadership in this situation? (Choose two.)

Select 2 answers

A.Privately ask each team member to report impediments to you so you can address them without public discussion.

B.Publicly recognize team members who raise impediments and celebrate the learning that follows.

C.Change the daily stand-up format to a written asynchronous update to reduce the pressure of speaking in front of peers.

D.Require team members to log all impediments in a tracking tool with mandatory daily updates.

E.Model vulnerability by sharing your own mistakes and what you learned from them during team meetings.

AnswersB, E

Positive recognition for raising impediments directly counteracts the fear of blame. By celebrating those who surface problems, the leader signals that transparency is valued and rewarded. This encourages others to follow suit and helps shift the team culture toward open communication. It is a servant leadership action because it removes a barrier to transparency and supports the team's growth.

Why this answer

The team's avoidance of raising impediments stems from fear of blame. The most effective servant leadership actions are to model vulnerability by sharing your own mistakes and to publicly recognize those who do raise impediments. These actions build psychological safety and signal that transparency is valued.

Private reporting, mandatory logging, and switching to asynchronous updates do not address the underlying fear and may further suppress openness.

Exam trap

The trap here is choosing a process change, such as mandatory logging or asynchronous stand-ups, as a way to make reporting feel safer, when the real need is to build a culture of psychological safety through modeling and recognition.

Full explanation →

233

MCQeasy

What is the primary role of the 'Definition of Done' (DoD)?

A.To list the team members on the project.

B.To describe the user's requirements for the product.

C.To define the budget limit for the project.

D.To ensure a common understanding of quality and completeness for all work items.

AnswerD

The Definition of Done establishes a shared quality bar, so every increment meeting it is genuinely complete. This directly satisfies the stem's requirement for common understanding of quality and completeness across all work items, preventing differing interpretations between developers and stakeholders.

Why this answer

The Definition of Done is a shared, explicit checklist that determines when a product increment is complete and of acceptable quality. It creates a common understanding across the team, PO, and stakeholders of what 'done' means for every backlog item, preventing ambiguity about quality and completeness. Without a DoD, 'done' becomes subjective and technical debt accumulates.

Exam trap

The trap here is confusing the Definition of Done (quality/completeness standard) with acceptance criteria (specific functional requirements for a single story) — candidates often pick the requirements-based answer.

How to eliminate wrong answers

Option A is wrong because listing team members is a team roster or resource plan, not a quality/completeness agreement. Option B is wrong because user requirements are captured in user stories, acceptance criteria, or the product backlog — the DoD is about quality standards, not functional requirements. Option C is wrong because budget limits belong to financial planning or the project charter, not the DoD, which governs work item completion criteria.

Full explanation →

234

MCQmedium

Your team has a high level of dependency on an external vendor. How should you facilitate this relationship?

A.Demand that the vendor adopt your team's exact agile process.

B.Stop using the vendor's services.

C.Ask the team to work around the vendor's delays.

D.Facilitate regular communication channels and define clear interfaces for the dependencies.

AnswerD

Regular communication channels plus explicitly defined interfaces reduce the coordination ambiguity inherent in external vendor dependency. Clear interfaces specify what crosses the boundary and when, satisfying the constraint that the vendor sits outside the team's direct control and cannot be managed through internal self-organisation alone.

Why this answer

Managing external dependencies requires deliberate communication and interface definition rather than process imposition or avoidance. Regular communication channels (sync meetings, shared boards, status updates) keep both parties aligned on timelines and expectations, while clearly defined interfaces (APIs, contracts, deliverables) reduce ambiguity and integration risk. This is the agile way to handle dependencies you cannot directly control.

Exam trap

PMI-ACP often tests the misconception that the solution to a difficult vendor relationship is to impose your process or cut ties, when the agile answer is to facilitate communication and define clear interfaces.

How to eliminate wrong answers

Option A is wrong because demanding the vendor adopt your exact agile process ignores that vendors have their own constraints and contracts; agile emphasizes adapting to the other party rather than forcing conformity. Option B is wrong because stopping the vendor's services is a drastic, often contractually and operationally infeasible response that ignores the value the vendor provides. Option C is wrong because working around the vendor's delays hides the dependency rather than managing it, leading to rework, integration failures, and unaddressed risk.

Full explanation →

235

MCQeasy

A team is struggling to understand the Product Owner's vision. What should you do?

A.Create your own vision for the team.

B.Ask the developers to interview the customers themselves.

C.Facilitate a visioning workshop where the PO presents the product roadmap and goals to the team.

D.Tell the team to just focus on completing their tasks.

AnswerC

A visioning workshop directly addresses the team's unclear understanding by having the Product Owner articulate the roadmap and goals, creating shared context and enabling questions. This satisfies the stem's constraint that the team cannot grasp the PO's vision, which written artefacts alone failed to convey.

Why this answer

When the team doesn't understand the PO's vision, the root cause is usually a communication gap, not a lack of capability, so the right move is to create a structured forum where the PO can articulate the roadmap and goals directly. A visioning workshop aligns everyone on purpose and priorities while keeping the PO as the authoritative source of product direction.

Exam trap

PMI-ACP often tests whether candidates will substitute their own judgment for the PO's — the trap is picking 'create your own vision' or 'interview customers directly' when the correct Agile answer is to facilitate PO-led alignment.

How to eliminate wrong answers

Option A is wrong because creating your own vision usurps the PO's accountability and guarantees divergence between what the team builds and what the product actually needs. Option B is wrong because sending developers to interview customers themselves bypasses the PO's prioritization role and can produce conflicting, unranked requirements that the team isn't positioned to reconcile. Option D is wrong because telling the team to just focus on tasks is a task-oriented dodge that leaves the underlying vision gap unaddressed, so the team will keep building without understanding the 'why.'

Full explanation →

236

MCQeasy

A team is confused about who should make decisions. How should the servant leader address this?

A.Encourage the team to make decisions themselves.

B.Let the team struggle indefinitely without guidance.

C.Make all decisions for the team.

D.Ask the client to make every decision.

AnswerA

Servant leaders deliberately shift decision authority to the team, since self-organising teams own their work and resolve ambiguity fastest when empowered. Encouraging the team to decide removes the confusion about ownership and builds the shared accountability that agile practise requires.

Why this answer

Encouraging the team to make decisions themselves is correct because a servant leader's role is to empower self-organizing teams, fostering ownership and accountability. When the team is confused about decision-making authority, the servant leader should clarify boundaries, provide coaching, and then step back to let the team decide within those boundaries. This builds capability and aligns with Agile principles.

Exam trap

PMI-ACP often tests the difference between servant leadership and laissez-faire leadership; candidates may pick 'let them struggle' thinking it builds resilience, but the correct answer includes active encouragement and support.

How to eliminate wrong answers

Option B is wrong because letting the team struggle indefinitely without guidance is abdication, not servant leadership—the leader must provide support and remove impediments. Option C is wrong because making all decisions for the team creates dependency and undermines self-organization, turning the leader into a bottleneck. Option D is wrong because asking the client to make every decision removes autonomy from the team and the product owner, violating Agile's customer collaboration and team empowerment principles.

Full explanation →

237

MCQeasy

A team member frequently arrives late to daily stand-up and seems disengaged. As the agile leader, what is the most appropriate first step?

A.Bring up the lateness during the next stand-up and ask the team member to explain in front of everyone.

B.Ignore the behavior for now and focus on the team's overall performance metrics.

C.Speak with the team member privately to understand any obstacles and offer support.

D.Send a reminder email to the entire team about the importance of punctuality at stand-up.

AnswerC

Addressing the behavior privately shows respect and allows the leader to uncover underlying issues such as personal problems, workload, or lack of clarity. This approach aligns with servant leadership by focusing on removing impediments and supporting the individual. It also avoids embarrassing the team member publicly, which could worsen disengagement and damage trust within the team.

Why this answer

The most appropriate first step is to have a private conversation to understand the team member's situation. This aligns with servant leadership, which prioritizes removing impediments and supporting individuals. It also respects the team member's dignity and increases the likelihood of addressing the root cause, whether it is a personal issue, workload problem, or lack of engagement with the work.

Exam trap

The trap here is assuming that a public correction or a general reminder will resolve the issue, when in fact it often exacerbates disengagement and damages trust.

Full explanation →

238

MCQhard

An organization is transitioning from project-based funding to product-based funding. How does this impact the Product Owner's role?

A.The Product Owner is now responsible for the annual budget.

B.The Product Owner no longer manages the backlog.

C.The Product Owner focuses on long-term product value rather than project milestones.

D.The Product Owner now reports to the finance department.

AnswerC

Product-based funding shifts investment toward sustained outcomes instead of fixed project scope and deadlines. The Product Owner therefore prioritises maximising long-term product value and continuous discovery, rather than tracking delivery against project milestones and temporary team assignments.

Why this answer

Moving from project-based to product-based funding shifts the Product Owner's focus from delivering against fixed project milestones and budgets to maximizing long-term product value and outcomes. Funding becomes continuous and tied to product strategy, so the PO prioritizes the backlog around value streams, customer outcomes, and lifecycle economics rather than one-time project completion.

Exam trap

PMI-ACP often tests the misconception that a funding model change alters the PO's core accountabilities, tempting candidates to pick options that reassign backlog ownership or budget responsibility instead of recognizing the shift toward long-term value focus.

How to eliminate wrong answers

Option A is wrong because budget ownership typically remains with finance, portfolio, or product leadership; the PO influences investment through value-based prioritization, not by owning the annual budget. Option B is wrong because backlog management is the core, non-negotiable accountability of the Product Owner in Scrum and is unaffected by the funding model. Option D is wrong because reporting lines are organizational and not dictated by the funding model; the PO remains accountable to the product's stakeholders and customers, not to finance.

Full explanation →

239

MCQhard

An organization is scaling agile across five teams working on a single product. To optimize the end-to-end delivery flow, the teams identify dependencies between them. Which approach best coordinates this cross-team delivery?

A.Assign a dedicated project manager to track every individual task across all teams.

B.Combine all five teams into one large daily stand-up meeting.

C.Mandate that all teams use the same velocity reporting tool.

D.Request that teams ignore dependencies until the final integration sprint.

E.Implement a Scrum of Scrums meeting to discuss cross-team dependencies and integration blockers.

AnswerE

A Scrum of Scrums directly satisfies the cross-team coordination constraint by having each team's representative surface dependencies, integration blockers and inter-team risks in a recurring forum. This scales agile communication across the five teams without adding a command-and-control layer, preserving team autonomy while optimising end-to-end delivery flow.

Why this answer

A Scrum of Scrums is the standard scaling mechanism for coordinating multiple Scrum teams working on a single product. It brings representatives from each team together to discuss cross-team dependencies, integration blockers, and alignment, optimizing end-to-end delivery flow.

Exam trap

PMI-ACP often tests the misconception that scaling coordination requires centralized control (project managers, unified tools, giant meetings) rather than lightweight, team-driven mechanisms like Scrum of Scrums.

How to eliminate wrong answers

Option A is wrong because assigning a dedicated project manager to track every task reintroduces command-and-control micromanagement and does not scale; it also undermines team self-organization. Option B is wrong because combining five teams into one large daily stand-up creates a lengthy, unfocused meeting that loses the purpose of the 15-minute timebox and reduces individual team accountability. Option C is wrong because mandating a common velocity reporting tool addresses metrics, not coordination of dependencies, and velocity is not comparable across teams anyway.

Option D is wrong because ignoring dependencies until the final integration sprint guarantees late discovery of blockers, rework, and integration failures — the opposite of optimizing flow.

Full explanation →

240

MCQeasy

A team member is consistently distracting others during pair programming. What is the most appropriate action?

A.Remove the pair programming practice.

B.Tell the team member to be quiet.

C.Coach the team to discuss collaboration norms, including focus and respect, during a retrospective.

D.Move the team member to a different project.

AnswerC

Addressing the behaviour through team-owned collaboration norms in a retrospective avoids singling out the individual while making focus and respect explicit. The team collectively agrees on pair programming etiquette, satisfying the stem's need for a sustainable, non-punitive correction.

Why this answer

In Agile, team dynamics and collaboration norms are best addressed by the team itself during a retrospective, where members can openly discuss behaviors like focus and respect. Coaching the team to surface and resolve the distraction through shared norms aligns with self-organization and continuous improvement principles.

Exam trap

PMI-ACP often tests whether candidates choose a collaborative, team-driven solution (retrospective/coaching) over a directive or punitive one (telling someone to be quiet, removing them), so the trap is selecting the seemingly 'quick fix' that violates self-organization.

How to eliminate wrong answers

Option A is wrong because removing pair programming penalizes the whole team and discards a valuable practice rather than addressing the root behavioral issue. Option B is wrong because simply telling the member to be quiet is a directive, top-down fix that ignores the team's ownership of its working agreements and may damage psychological safety. Option D is wrong because moving the person off the project is an extreme, punitive action that avoids the real problem and undermines team stability and trust.

Full explanation →

241

MCQeasy

Which of the following is a key component of a good user story?

A.A fixed deadline.

B.A 20-page document.

C.INVEST criteria.

D.Detailed technical specifications.

AnswerC

INVEST criteria—Independent, Negotiable, Valuable, Estimable, Small, Testable—provide the concrete quality checklist a user story must satisfy. This directly answers the stem's demand for a key component of a good user story, since INVEST defines the attributes separating well-formed stories from vague requirements.

Why this answer

INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) are key components of a good user story. They ensure that user stories are well-defined, deliver value, and are suitable for iterative development.

Exam trap

PMI-ACP often tests the misconception that user stories require detailed specifications or deadlines, but the key is the INVEST criteria for quality.

How to eliminate wrong answers

Option A is wrong because a fixed deadline is not a component of a user story; deadlines are constraints that may be applied but are not part of the story's quality criteria. Option B is wrong because a 20-page document is excessive and contradicts the agile principle of lightweight documentation. Option D is wrong because detailed technical specifications are not part of user stories; they are typically captured separately and should not dictate the story's structure.

Full explanation →

242

MCQmedium

A Product Owner notices that a user story describing an online checkout flow is too large to complete in a single sprint and keeps getting partially done. What is the most appropriate agile action to improve product flow?

A.Allow the team to carry the partially completed checkout story into the next sprint and count it toward that sprint's goal.

B.Ask the developers to work overtime to complete the full checkout story within the current sprint without changing its scope.

C.Split the story into smaller, independently valuable slices that each satisfy the Definition of Done within a sprint.

D.Extend the sprint length from two weeks to four weeks so the team has more time to finish the large checkout story.

AnswerC

Splitting a large story into smaller vertical slices that each meet the Definition of Done improves flow, enables frequent integration, and produces potentially releasable value each sprint. This practice, often called story slicing, keeps the product backlog actionable and lets the team finish work rather than carrying partial stories, which directly addresses the recurring incomplete checkout story.

Why this answer

Oversized stories that cannot meet the Definition of Done within a sprint disrupt flow and hide progress. Slicing them into smaller vertical increments, each independently valuable and completable within the timebox, restores predictable delivery and frequent feedback. This keeps the product backlog healthy and aligns with agile principles of small batches, sustainable pace, and potentially releasable increments.

Exam trap

The trap here is treating a story-sizing problem as a scheduling or effort problem by extending the sprint or adding overtime.

Full explanation →

243

MCQeasy

An agile team is having trouble getting feedback from a remote stakeholder. What should you do?

A.Stop the project until the stakeholder is available.

B.Facilitate a session to find a collaborative tool or meeting time that works for everyone.

C.Send the stakeholder a daily summary of the work.

D.Assume the stakeholder is not interested and proceed without them.

AnswerB

Facilitating a session directly addresses the remote stakeholder's access constraint by co-creating a communication channel and schedule the stakeholder can actually commit to. Rather than imposing a tool or time, the team negotiates shared working agreements, restoring the feedback loop that agile delivery depends on.

Why this answer

When a remote stakeholder is not providing feedback, the best action is to facilitate a session to find a collaborative tool or meeting time that works for everyone. This addresses the root cause—accessibility and communication preferences—and aligns with Agile's emphasis on customer collaboration and face-to-face interaction (or its virtual equivalent).

Exam trap

The trap is choosing a one-way communication method (daily summary) or giving up on the stakeholder, whereas Agile demands active collaboration and adaptation to overcome impediments.

How to eliminate wrong answers

Option A is wrong because stopping the project is drastic and unproductive; it does not solve the feedback problem and may cause delays. Option C is wrong because sending a daily summary is one-way communication, not the collaborative feedback loop Agile requires. Option D is wrong because assuming disinterest and proceeding without them ignores the stakeholder's needs and risks building the wrong product.

Full explanation →

244

Multi-Selecthard

Which THREE factors are critical when aligning agile work with organizational priorities?

Select 3 answers

A.Value-based prioritization.

B.Strategic business objectives.

C.Personal developer interests.

D.Stakeholder feedback loops.

E.The number of emails sent.

AnswersA, B, D

Value-based prioritisation ranks backlog items by delivered business value, ensuring limited agile capacity flows to the highest-return work first. This satisfies the alignment constraint by tying day-to-day iteration selection directly to organisational priorities rather than effort, seniority or technical preference.

Why this answer

Value-based prioritization (A) is critical because agile alignment means ranking backlog items by the business value they deliver, ensuring effort goes to work that maximizes customer and organizational outcomes. Strategic business objectives (B) provide the north star that agile teams must trace their work back to, so every increment contributes to the enterprise's goals rather than local optimizations. Stakeholder feedback loops (D) are essential because they continuously validate that the work still matches shifting priorities and customer needs, enabling rapid course correction.

Personal developer interests (C) are not a valid alignment factor since individual preferences can diverge from organizational value and would distort prioritization. The number of emails sent (E) is a meaningless activity metric that says nothing about value delivery or strategic alignment.

Exam trap

The trap is selecting plausible-sounding but non-strategic factors (personal interests, activity metrics) instead of the three that actually connect delivery to business value and customer validation.

Full explanation →

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