Courseiva

CCNA Mindset Questions

72 questions · Mindset · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
Multi-Selectmedium

An Agile team is working in a complex environment where requirements emerge over time. The team wants to ensure they are applying an Agile mindset to decision-making. Which TWO of the following actions best demonstrate an Agile mindset? (Choose two.)

Select 2 answers
A.Delaying a decision until more information is available, while continuing to deliver small increments.
B.Making all architectural decisions upfront to avoid rework later.
C.Following a detailed plan strictly to ensure all requirements are met.
D.Assigning tasks based on individual expertise to maximize efficiency.
E.Encouraging the team to experiment with different solutions and learn from failures.
AnswersA, E

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.

Why this answer

The two actions that best demonstrate an Agile mindset are delaying decisions while delivering increments and encouraging experimentation and learning from failures. Both reflect Agile principles of embracing uncertainty, iterative delivery, and continuous improvement, enabling the team to adapt effectively in complex environments.

Exam trap

The trap here is equating efficiency with Agile mindset by choosing task assignment based on expertise, when Agile actually values team self-organization and collective decision-making.

Practice this question →
2
Multi-Selecteasy

Which TWO of the following are core Agile values?

Select 2 answers
A.Following a plan over responding to change
B.Working software over comprehensive documentation
C.Contract negotiation over customer collaboration
D.Rigid processes over team flexibility
E.Individuals and interactions over processes and tools
AnswersB, E

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.

Why this answer

Option B is correct because the Agile Manifesto explicitly states 'Working software over comprehensive documentation,' meaning functioning deliverables are valued more highly than exhaustive documentation. Option E is correct because the first value in the Agile Manifesto is 'Individuals and interactions over processes and tools,' emphasizing people and communication over rigid methodologies. Option A is incorrect because the Agile Manifesto values 'Responding to change over following a plan,' which is the reverse of what is stated.

Option C is incorrect because Agile values 'Customer collaboration over contract negotiation,' again the opposite of the option. Option D is incorrect because Agile favors team flexibility and adaptability, not rigid processes.

Exam trap

PMI-ACP often tests the misconception that Agile values mean abandoning documentation, plans, or contracts entirely, when the manifesto actually values the left items more while still acknowledging the right items.

Practice this question →
3
MCQhard

An organization is transitioning to Agile and has asked you to coach a product team. You notice that the team's manager assigns tasks, reviews all code before it is merged, and approves every user story before development begins. Which action best aligns with an Agile mindset?

A.Suggest the manager attend Agile training while the team continues with the current process until the manager is ready to change.
B.Recommend that the team adopt a strict approval workflow for user stories to ensure quality before development starts.
C.Ask the manager to continue assigning tasks but delegate code reviews to a senior developer to speed up merges.
D.Work with the manager to shift from directing tasks to enabling the team to self-organize and make technical decisions collectively.
AnswerD

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.

Why this answer

The correct action focuses on coaching the manager to transition from a directive role to a supportive one, enabling the team to self-organize. Agile mindset values individuals and interactions, self-organizing teams, and servant leadership. By shifting task assignment and decision-making to the team, the manager fosters ownership, collaboration, and adaptability, which are essential for Agile success.

Exam trap

The trap here is assuming that delegating specific tasks like code reviews solves the underlying command-and-control issue, when the real need is to shift the manager's overall approach to enable team autonomy.

Practice this question →
4
MCQmedium

You are a Scrum Master observing a team that relies heavily on a single senior developer to make all technical decisions. How should you apply servant leadership to improve team dynamics?

A.Ask the Product Owner to assign tasks directly to team members to bypass the senior developer.
B.Instruct the senior developer to continue making decisions to ensure project speed.
C.Facilitate a session on collaborative decision-making techniques to encourage input from all team members.
D.Remove the senior developer from the project to force others to lead.
AnswerC

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.

Why this answer

Servant leadership in Scrum means the Scrum Master removes impediments and coaches the team toward self-organization, not directing work or making personnel decisions. Facilitating a collaborative decision-making session directly addresses the root cause — the team's over-reliance on one voice — by building the skills and psychological safety needed for shared ownership. This aligns with the PMI-ACP Agile Principles of self-organizing teams and the Scrum Master's role as a servant-leader who grows the team's capability rather than solving the problem for them.

Exam trap

PMI-ACP often tests the misconception that a Scrum Master should solve team problems directly or escalate to authority figures, when the correct servant-leadership response is almost always to facilitate, coach, or remove impediments so the team can solve it themselves.

How to eliminate wrong answers

Option A is wrong because asking the Product Owner to assign tasks directly violates the principle of self-organizing teams and improperly mixes the PO's prioritization role with the team's internal work-management decisions. Option B is wrong because instructing the senior developer to continue making all decisions reinforces the very anti-pattern being addressed and contradicts servant leadership, which develops the team rather than preserving a single point of failure. Option D is wrong because removing a team member is a punitive, top-down action outside the Scrum Master's authority and destroys team trust; it also fails to build the collaborative decision-making skills the team actually needs.

Practice this question →
5
MCQeasy

During a sprint review, a key stakeholder expresses dissatisfaction with a feature that was built exactly to the written requirements. As the PMI-ACP practitioner, what is the most Agile-aligned interpretation of this situation?

A.The team should freeze the requirements and complete the remaining scope as planned.
B.The requirements were incomplete and the business analyst should be held accountable.
C.The feedback is valuable and the team should use it to adapt the product backlog.
D.The stakeholder should have been more involved earlier, so the fault lies with them.
AnswerC

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.

Why this answer

The sprint review is an inspect-and-adapt event where stakeholders examine the increment and provide feedback that shapes the product backlog. When a stakeholder is dissatisfied, the Agile-aligned response is to treat that feedback as valuable and use it to adapt future work. Blaming individuals or freezing requirements both reject the core Agile idea that requirements emerge and that customer collaboration drives value.

Exam trap

The trap here is assuming that because the feature matched the written requirements, the team did nothing wrong and the stakeholder must be mistaken, when Agile treats feedback as the primary measure of value.

Practice this question →
6
MCQmedium

A team is struggling to finish their stories. How can you help them improve their Agile mindset?

A.Tell them to work faster.
B.Assign more work to fill their time.
C.Extend the sprint.
D.Help them refine their stories to be smaller and clearer.
AnswerD

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.

Why this answer

The core issue is that stories are too large or ambiguous, which prevents the team from completing them within a sprint. By helping the team refine stories to be smaller and clearer, you address the root cause: large stories increase uncertainty, make estimation harder, and often lead to carryover. This aligns with Agile principles of incremental delivery and continuous improvement, enabling the team to finish work and gain a sense of accomplishment, which reinforces the Agile mindset.

Exam trap

PMI-ACP often tests the misconception that team performance issues are solved by adding pressure (work faster, more work) or changing the process constraints (extend sprint), rather than addressing the root cause through Agile practices like story refinement.

How to eliminate wrong answers

Option A is wrong because telling a team to 'work faster' ignores the underlying problem and violates Agile's emphasis on sustainable pace and self-organization. Option B is wrong because assigning more work to fill time increases pressure and reduces focus, contradicting the principle of limiting work in progress (WIP) and optimizing flow. Option C is wrong because extending the sprint undermines the timebox, reduces the team's ability to estimate and commit, and masks the real issue of story size and clarity.

Practice this question →
7
MCQeasy

A product owner wants to add a new requirement mid-sprint. According to Agile principles, what should the team do?

A.Accept the change and extend the sprint duration.
B.Refuse all changes immediately.
C.Ask the stakeholders to approve the change first.
D.Evaluate the change against the current sprint goal with the PO.
AnswerD

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.

Why this answer

In Agile, the sprint goal is the commitment the team makes for the sprint, and changes that jeopardize it should be evaluated collaboratively. The correct action is for the team to assess the new requirement against the current sprint goal with the Product Owner, determining whether it can be accommodated without compromising the sprint's objective. This aligns with the Agile principle of welcoming changing requirements, even late in development, while maintaining focus and protecting the sprint's integrity.

The PO and team decide together whether to adjust scope, swap items of equal size, or defer the change to the next sprint.

Exam trap

PMI-ACP often tests the misconception that any change request must be either immediately accepted (with sprint extension) or rejected, ignoring the collaborative evaluation against the sprint goal that Agile actually prescribes.

How to eliminate wrong answers

Option A is wrong because extending the sprint duration violates the timeboxing principle of Scrum and Agile; sprints are fixed-length and should not be extended to accommodate new work. Option B is wrong because refusing all changes contradicts the Agile value of responding to change over following a plan; changes should be evaluated, not automatically rejected. Option C is wrong because stakeholder approval is not required for mid-sprint changes; the Product Owner is empowered to make scope decisions and prioritize the backlog, so involving stakeholders in every change undermines the PO's authority and slows down the team.

Practice this question →
8
MCQhard

A team is failing to 'self-organize'. What is the most likely cause?

A.They are too smart.
B.They are lazy.
C.They have the wrong tools.
D.The leadership is still command-and-control.
AnswerD

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.

Why this answer

Self-organization requires an environment of trust and autonomy where the team owns its process and decisions. When leadership still operates in a command-and-control style — assigning tasks, dictating how work is done, and requiring approvals — the team has no room to self-organize. The most likely cause is therefore the leadership style, not the team's intelligence, motivation, or tooling.

Exam trap

PMI-ACP often tests the misconception that self-organization failures are team deficiencies (skill, motivation, tools) rather than symptoms of a controlling management environment.

How to eliminate wrong answers

Option A is wrong because intelligence has no bearing on a team's ability to self-organize; smart teams can still be blocked by external control. Option B is wrong because laziness is a judgmental label, not a root cause — Agile assumes teams are motivated and looks to systemic impediments instead. Option C is wrong because tools are enablers, not the determinant of self-organization; a team can self-organize with minimal tooling if given autonomy.

Practice this question →
9
MCQhard

During a sprint, the team realizes the current technical approach won't work. What is the most Agile action?

A.Pivot the approach and communicate the impact to the PO.
B.Continue the current path to avoid missing the sprint deadline.
C.Hide the issue and fix it next sprint.
D.Blame the architect for the bad design.
AnswerA

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.

Why this answer

Agile embraces change and empirical learning — when the technical approach is proven unworkable, the team should pivot, adapt the plan, and transparently communicate the impact to the Product Owner. This preserves the sprint goal's value and allows the PO to re-prioritize scope if needed. Hiding or persisting with a broken approach violates transparency and wastes effort.

Exam trap

PMI-ACP often tests the instinct to 'protect the sprint commitment' — candidates pick 'continue to avoid missing the deadline,' but Agile values transparency and adaptation over blind adherence to a plan.

How to eliminate wrong answers

Option B is wrong because continuing a known-broken path to 'save the deadline' delivers no value and accumulates technical debt — it violates the principle of technical excellence. Option C is wrong because hiding the issue destroys transparency, delays resolution, and compounds risk; Agile requires surfacing problems early. Option D is wrong because blaming the architect is not constructive and violates the Agile value of individuals and interactions over blame — the team owns the solution collectively.

Practice this question →
10
Multi-Selecteasy

Which TWO of the following are signs of a healthy Agile culture?

Select 2 answers
A.Disagreements are avoided at all costs
B.Decisions are made top-down by management
C.Performance is measured primarily by individual output
D.High level of transparency and honest communication
E.Team members feel comfortable sharing their mistakes
AnswersD, E

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.

Why this answer

Option D is correct because a healthy Agile culture depends on transparency and honest communication: information radiators, visible backlogs, and open discussion of progress and impediments let the team inspect and adapt, which is the foundation of empirical process control. Option E is correct because psychological safety — team members feeling comfortable admitting mistakes — enables early problem surfacing, blameless retrospectives, and continuous improvement rather than hiding defects or risks. The unmarked options describe unhealthy or anti-Agile patterns: avoiding disagreements (A) suppresses the constructive conflict needed for better decisions, top-down management decisions (B) contradict Agile self-organizing teams, and measuring primarily individual output (C) undermines team accountability and encourages local optimization over delivering value.

Exam trap

The trap here is equating 'healthy culture' with 'harmony,' so candidates pick 'disagreements are avoided' as a positive sign when it is actually a symptom of suppressed conflict and low safety.

Practice this question →
11
MCQhard

A team member consistently criticizes ideas during retrospectives, creating a defensive atmosphere. How should the facilitator address this to improve psychological safety?

A.Publicly reprimand the team member during the next meeting.
B.Discuss the impact of the behavior privately with the individual.
C.Ignore the behavior to avoid conflict.
D.Remove the team member from the project immediately.
AnswerB

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.

Why this answer

The facilitator should address the behavior privately with the individual, explaining how the constant criticism affects the team's psychological safety and retrospective effectiveness. A private conversation preserves the person's dignity, avoids defensiveness, and gives them a chance to adjust — which is the coaching-oriented, psychologically safe approach. Public confrontation or removal would escalate conflict and further damage safety.

Exam trap

PMI-ACP often tests whether candidates choose private coaching over public confrontation or avoidance — the trap is picking 'ignore the behavior' to avoid conflict, but facilitators must address dysfunction directly and privately to protect psychological safety.

How to eliminate wrong answers

Option A is wrong because publicly reprimanding the team member humiliates them, triggers defensiveness, and destroys the psychological safety the facilitator is trying to build — it models the very behavior causing the problem. Option C is wrong because ignoring the behavior lets it continue, signals to the team that toxic criticism is acceptable, and erodes trust and safety over time. Option D is wrong because removing the team member immediately is a disproportionate, punitive overreaction that skips coaching, damages team morale, and may not even address the root cause of the behavior.

Practice this question →
12
MCQmedium

A team is hesitant to share their 'Velocity'. Why might this be?

A.They are lazy.
B.They are hiding secrets.
C.They fear it will be used against them as a productivity metric.
D.They don't know what it is.
AnswerC

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.

Why this answer

Velocity is a planning and forecasting tool, not a productivity measure, and teams often resist sharing it because they've seen or fear it being weaponized in performance reviews or cross-team comparisons. That fear is rational: once velocity becomes a management metric, teams start gaming it by inflating estimates rather than improving delivery.

Exam trap

The trap is treating velocity as a productivity KPI — PMI-ACP wants candidates to recognize that velocity is a team-internal forecasting tool, and that fear of misuse is the legitimate reason teams hesitate to share it.

How to eliminate wrong answers

Option A is wrong because labeling the team 'lazy' is a judgmental stereotype that ignores the legitimate systemic reason teams withhold velocity — fear of misuse. Option B is wrong because 'hiding secrets' implies deception, when the actual dynamic is self-protection against a metric being misapplied, which is a well-documented Agile anti-pattern. Option D is wrong because most Agile teams know exactly what velocity is; the issue is not comprehension but the consequences of exposing it to the wrong audience.

Practice this question →
13
MCQhard

A team has high velocity but the quality of the product is declining. The team feels that speed is the only metric that matters to management. How should you address this as an Agile practitioner?

A.Reduce the team's story point estimates to make it appear that velocity remains high.
B.Coach the team and stakeholders on the Agile principle of sustainable development and the cost of technical debt.
C.Ignore the quality issues to keep velocity high, as requested by management.
D.Mandate that no new features can be added until all defects are resolved.
AnswerB

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.

Why this answer

When velocity is high but quality is declining, the root cause is usually pressure to prioritize speed over sustainable development, often driven by management's focus on velocity as the sole metric. The Agile practitioner's role is to coach both the team and stakeholders on the Agile principle of sustainable development and the long-term cost of technical debt. This addresses the systemic issue rather than masking symptoms, and it aligns with the Agile values of technical excellence and continuous improvement.

Exam trap

PMI-ACP often tests whether candidates will manipulate metrics or impose mandates under pressure — the trap is selecting a short-term 'fix' (reducing estimates, ignoring quality, freezing features) instead of the Agile-aligned coaching response that addresses sustainable development and technical debt.

How to eliminate wrong answers

Option A is wrong because reducing story point estimates to inflate apparent velocity is data manipulation that destroys the team's empirical forecasting ability and hides the real problem. Option C is wrong because ignoring quality issues to keep velocity high directly violates the Agile principle of technical excellence and will compound technical debt, eventually collapsing velocity. Option D is wrong because mandating a feature freeze until all defects are resolved is a command-and-control, prescriptive response that ignores the need for team self-organization and stakeholder collaboration — it treats a systemic coaching issue as a policy mandate.

Practice this question →
14
Multi-Selectmedium

Which THREE of the following are hallmarks of an Agile mindset?

Select 3 answers
A.Valuing collaboration over individual silos
B.Adapting to change rather than fearing it
C.Relying on strict top-down hierarchy for execution
D.Learning through experimentation and empirical data
E.Staying committed to an initial plan regardless of feedback
AnswersA, B, D

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.

Why this answer

Option A is correct because an Agile mindset prioritizes collaboration and cross-functional teamwork over individual silos, reflecting the Agile value of individuals and interactions over processes and tools. Option B is correct because Agile embraces changing requirements and uncertainty, responding to change rather than rigidly resisting it. Option D is correct because Agile relies on empiricism—transparency, inspection, and adaptation—and encourages learning through experimentation and data rather than assumptions.

Option C is incorrect because strict top-down hierarchy contradicts Agile's emphasis on self-organizing teams and distributed decision-making. Option E is incorrect because blindly following an initial plan despite feedback conflicts with Agile's iterative, feedback-driven approach.

Exam trap

PMI-ACP often tests the distinction between Agile values and traditional plan-driven approaches, trapping candidates who confuse 'Agile' with 'no planning' or who overlook the emphasis on empirical learning and collaboration.

Practice this question →
15
MCQmedium

An organization is transitioning to Agile and a program manager asks you, as the PMI-ACP practitioner, to define the team's success measures. They want to know what should be tracked to best reflect an Agile mindset. Which approach should you recommend?

A.Measure customer satisfaction and delivered business value through frequent releases.
B.Focus on individual utilization rates to ensure every team member is fully allocated.
C.Track adherence to the detailed project plan and report schedule variance weekly.
D.Track the number of hours worked per week as a proxy for team commitment.
AnswerA

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.

Why this answer

In an Agile mindset, success is defined by value delivered to the customer, not by conformance to a plan or by effort metrics. Measuring customer satisfaction and business value through frequent releases focuses the team on outcomes and continuous delivery, which reinforces the Agile principles the organization is trying to adopt. Plan adherence, utilization, and hours worked are internal, activity-based measures that can actively discourage the adaptability and collaboration Agile requires.

Exam trap

The trap here is assuming that because the organization wants metrics, traditional plan-conformance or effort metrics are acceptable, when Agile success measures must reflect delivered value and customer outcomes.

Practice this question →
16
Multi-Selectmedium

An Agile team is preparing for its first release and the product owner wants to ensure the team is truly embracing an Agile mindset rather than just following ceremonies. Which TWO behaviors best demonstrate an Agile mindset in this situation? (Choose two.)

Select 2 answers
A.The team strictly follows the initial release plan to avoid scope creep.
B.The team measures success primarily by how closely actual effort matches the original estimates.
C.The team delivers a working increment at the end of each iteration and seeks feedback.
D.The team documents every design decision in a comprehensive specification before coding.
E.The team welcomes changing requirements late in the release to improve the product.
AnswersC, E

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.

Why this answer

An Agile mindset is demonstrated by behaviors that prioritize customer value, adaptability, and frequent delivery of working product. Welcoming late changes and delivering a working increment each iteration with feedback both reflect core Agile principles. Strict plan adherence, comprehensive upfront specifications, and estimate accuracy as the primary success measure are all signs of a predictive mindset that merely performs Agile ceremonies without embracing the underlying values.

Exam trap

The trap here is equating Agile ceremony participation or disciplined plan-following with an Agile mindset, when the mindset is revealed by how the team responds to change and delivers value.

Practice this question →
17
Multi-Selectmedium

Which TWO of the following would a servant leader do?

Select 2 answers
A.Focus on removing impediments that stop the team from working
B.Help the team become more self-organizing and mature
C.Make all technical choices for the team
D.Avoid attending team meetings
E.Monitor individual time logs to check productivity
AnswersA, B

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.

Why this answer

Option A is correct because a servant leader's core responsibility is to clear obstacles and impediments that block the team's progress, ensuring the team can deliver value without unnecessary friction. Option B is correct because servant leadership in agile contexts emphasizes coaching and developing the team so it becomes increasingly self-organizing, cross-functional, and mature over time. Option C is incorrect because making all technical choices is a command-and-control behavior that undermines team autonomy and self-organization.

Option D is incorrect because avoiding team meetings removes the leader from the team's context and prevents the coaching, facilitation, and support a servant leader provides. Option E is incorrect because monitoring individual time logs is a micromanagement and surveillance practice that contradicts the trust-based, people-first nature of servant leadership.

Exam trap

The trap here is confusing servant leadership with passivity or with authoritarian decision-making, leading candidates to select options that describe disengagement or control.

Practice this question →
18
MCQmedium

A team is working on a project with a very strict, non-negotiable deadline. How do you handle this?

A.Cancel the project.
B.Negotiate the scope to deliver the most valuable features by the date.
C.Work overtime.
D.Change the definition of 'Done'.
AnswerB

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.

Why this answer

When faced with a strict, non-negotiable deadline, the Agile approach is to negotiate scope to deliver the most valuable features by the date. This respects the fixed constraint (time) while maximizing business value through prioritization and iterative delivery.

Exam trap

PMI-ACP often tests the misconception that overtime or lowering quality standards is acceptable to meet a deadline, when the Agile response is to negotiate scope and prioritize value.

How to eliminate wrong answers

Option A is wrong because canceling the project is a defeatist response that ignores the possibility of delivering value within the constraint. Option C is wrong because working overtime is unsustainable, reduces quality, and violates Agile principles of sustainable pace. Option D is wrong because changing the definition of 'Done' compromises quality and is an unethical shortcut that undermines the team's integrity and product reliability.

Practice this question →
19
Multi-Selecthard

Which THREE of the following help maintain a sustainable pace?

Select 3 answers
A.Mandating consistent weekend work
B.Implementing WIP limits to prevent overload
C.Ensuring the team does not consistently work overtime
D.Increasing sprint goals every time
E.Allowing for regular reflection and adjustment
AnswersB, C, E

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.

Why this answer

Option B is correct because implementing WIP (Work In Progress) limits constrains the amount of work in the system at any one time, preventing team members from being overloaded and enabling a steady, sustainable flow of delivery. Option C is correct because ensuring the team does not consistently work overtime avoids burnout and preserves a constant, repeatable level of effort, which is the essence of a sustainable pace. Option E is correct because allowing for regular reflection and adjustment (as in Scrum retrospectives) lets the team inspect its process and adapt its workload and practices to keep the pace maintainable over time.

Option A is not correct because mandating consistent weekend work directly undermines sustainability by driving overtime and burnout. Option D is not correct because increasing sprint goals every time creates ever-growing pressure and an unsustainable escalation of commitments.

Exam trap

PMI-ACP often tests the misconception that working harder or adding more work is a valid way to improve performance, when sustainable pace requires protecting capacity and limiting work in progress.

Practice this question →
20
MCQeasy

An Agile team is experiencing low morale due to excessive micromanagement. What is the servant leader's primary role here?

A.Tell the team they must adapt to the manager's style.
B.Report the team for lack of productivity.
C.Become the manager and direct all work.
D.Act as a buffer to prevent external interference.
AnswerD

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.

Why this answer

A servant leader's primary role when a team suffers from micromanagement is to shield the team from external interference so they can focus on delivering value. Acting as a buffer means intercepting disruptive demands, negotiating boundaries with management, and creating the protected space the team needs to self-organize and recover morale. This is a core servant-leadership behavior: remove impediments and protect the team.

Exam trap

PMI-ACP often tests the servant-leader mindset versus traditional management — the trap is picking 'tell the team to adapt' or 'become the manager' because they sound decisive, but servant leadership always means protecting the team and removing impediments.

How to eliminate wrong answers

Option A is wrong because telling the team to adapt to micromanagement endorses the dysfunctional behavior, abandons the servant-leader's duty to protect the team, and will worsen morale and performance. Option B is wrong because reporting the team for low productivity blames the victims of micromanagement, damages trust, and ignores the root cause — the manager's behavior. Option C is wrong because becoming the manager and directing all work replaces one micromanager with another, destroys self-organization, and is the opposite of servant leadership.

Practice this question →
21
MCQeasy

What is meant by 'customer collaboration over contract negotiation'?

A.Prioritize shared goals and understanding over rigid adherence to contracts.
B.Stop charging the customer for work.
C.Always give the customer whatever they want.
D.Ignore contracts entirely.
AnswerA

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.

Why this answer

'Customer collaboration over contract negotiation' is one of the four values of the Agile Manifesto. It means that while contracts still matter, the relationship, shared understanding, and working toward mutual goals with the customer take precedence over rigidly enforcing every clause. Option A captures this balance correctly.

Exam trap

The trap here is the absolutist reading — candidates who see 'over' and interpret it as 'instead of' will pick options that dismiss contracts entirely, but the Manifesto explicitly preserves the value of the right-hand items.

How to eliminate wrong answers

Option B is wrong because the Agile Manifesto value does not mean working for free — Agile projects still have commercial agreements and payment terms. Option C is wrong because 'always give the customer whatever they want' is not collaboration; it is unmanaged scope creep and contradicts the Agile principle of delivering value through prioritized, negotiated scope. Option D is wrong because the Manifesto explicitly says 'while there is value in the items on the right, we value the items on the left more' — contracts are not ignored, they are simply subordinated to collaboration when trade-offs arise.

Practice this question →
22
MCQeasy

A team is struggling with technical debt. What is the most Agile way to handle it?

A.Incorporate technical debt reduction into the product backlog.
B.Wait for a dedicated 'refactoring' project.
C.Blame the developers.
D.Ignore it.
AnswerA

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.

Why this answer

The most Agile way to handle technical debt is to make it visible and incorporate it into the product backlog, where it can be prioritized alongside other work based on business value and risk. This allows the team and Product Owner to make informed trade-offs and address debt incrementally. It ensures technical debt is not ignored or treated as a separate, low-priority project.

Exam trap

PMI-ACP often tests the misconception that technical debt should be handled in a separate project or ignored, when Agile promotes making it visible in the backlog and addressing it incrementally.

How to eliminate wrong answers

Option B is wrong because waiting for a dedicated refactoring project delays addressing debt and often never happens due to competing priorities; Agile favors incremental, continuous improvement. Option C is wrong because blaming developers is counterproductive and does not solve the problem; technical debt is often a systemic issue resulting from decisions made under constraints. Option D is wrong because ignoring technical debt leads to increased complexity, slower delivery, and higher risk over time, which is contrary to sustainable development.

Practice this question →
23
MCQeasy

During a sprint, the team realizes that following the original plan will result in a product that does not meet the user's current needs. Which Agile principle should guide the team's next move?

A.Consult the project contract and adhere strictly to the initial scope document.
B.Wait for the formal change request process to be completed before doing any new work.
C.Collaborate with the customer to pivot and adapt the plan based on the new information.
D.Stick to the original plan until the end of the sprint to remain consistent.
AnswerC

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.

Why this answer

The Agile principle of responding to change over following a plan directs the team to collaborate with the customer and adapt when new information shows the original plan won't meet current needs. Pivoting with the customer keeps the product valuable and treats the plan as a living artifact rather than a contract.

Exam trap

PMI-ACP often tests whether candidates will default to plan-following or change-responding — the trap is picking the 'stick to the plan' or 'follow the change request process' answer when the Agile principle clearly favors customer collaboration and adaptation.

How to eliminate wrong answers

Option A is wrong because adhering strictly to the initial scope document is the waterfall mindset that Agile explicitly rejects — the contract doesn't override the goal of delivering value. Option B is wrong because waiting for a formal change request process to complete before doing any new work introduces bureaucratic delay and contradicts the Agile preference for responding to change quickly. Option D is wrong because sticking to the original plan until the end of the sprint prioritizes consistency over value, which is exactly the behavior the Agile principles warn against.

Practice this question →
24
MCQhard

A stakeholder demands a 'fixed-price, fixed-scope' contract. How can you demonstrate an Agile mindset to influence this stakeholder?

A.Agree to the terms but plan to change them later.
B.Refuse to work on the project.
C.Submit a formal complaint to the executive board.
D.Show the stakeholder the cost of change if the scope is fixed.
AnswerD

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.

Why this answer

Demonstrating an Agile mindset to a fixed-price/fixed-scope stakeholder means using data and transparency to show the trade-offs. Option D — showing the cost of change when scope is fixed — makes the economic consequences of rigidity visible and opens a conversation about alternatives like fixed-price/variable-scope or incremental delivery. This is a collaborative, evidence-based approach rather than an adversarial one.

Exam trap

PMI-ACP often tests whether candidates choose collaborative, evidence-based influence over avoidance or escalation — options that sound decisive (refuse, complain) are tempting but violate Agile values of transparency and collaboration.

How to eliminate wrong answers

Option A is wrong because agreeing to terms with the intent to change them later is deceptive and violates the Agile value of honesty and collaboration. Option B is wrong because refusing to work on the project is not a demonstration of Agile mindset — it is avoidance and does not help the stakeholder understand the trade-offs. Option C is wrong because escalating a formal complaint to the executive board is confrontational and bypasses the collaborative relationship that Agile values; it also does not educate the stakeholder about why fixed scope is problematic.

Practice this question →
25
MCQeasy

What is the purpose of a retrospective?

A.To complain about management.
B.To review the code.
C.To inspect and adapt the team's process.
D.To assign tasks.
AnswerC

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.

Why this answer

The purpose of a retrospective is to inspect and adapt the team's process, as defined in the Scrum Guide. It is a recurring event where the team reflects on how they worked together, identifies improvements, and creates an action plan for the next sprint. This continuous improvement loop is a core agile practice that distinguishes retrospectives from status meetings or code reviews.

Exam trap

PMI-ACP often tests the misconception that a retrospective is for complaining or for technical reviews — the correct answer always centers on inspecting and adapting the team's process.

How to eliminate wrong answers

Option A is wrong because complaining about management is not the purpose of a retrospective — while issues may be raised, the focus is on actionable process improvements within the team's control, not venting. Option B is wrong because reviewing code is a technical practice (e.g., code reviews or peer reviews) and is not the purpose of a retrospective, which focuses on process and collaboration. Option D is wrong because assigning tasks is a planning activity (Sprint Planning) and not the goal of a retrospective, which is about reflection and improvement.

Practice this question →
26
MCQhard

A team leader is doing all the task assignments. How do you transition them to a servant leader?

A.Let the team continue to be dependent.
B.Tell them to stop doing it.
C.Remove the leader from the team.
D.Coach them on the benefits of team self-organization and pulling work.
AnswerD

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.

Why this answer

The correct answer is D because transitioning from a directive task-assigner to a servant leader requires a mindset shift, not a sudden removal of authority. Coaching the leader on the benefits of self-organization and pull-based work helps them understand why empowering the team leads to higher engagement, better decisions, and faster delivery. This aligns with PMI-ACP's emphasis on servant leadership, where the leader supports the team's growth rather than controlling assignments.

Simply telling them to stop or removing them would create a vacuum and likely harm the team's performance.

Exam trap

PMI-ACP often tests the misconception that servant leadership means abdicating all authority or removing the leader, when in fact it requires active coaching and a gradual shift toward team self-organization.

How to eliminate wrong answers

Option A is wrong because allowing the team to remain dependent on the leader for task assignments perpetuates a command-and-control culture, directly contradicting servant leadership and self-organization principles. Option B is wrong because abruptly telling the leader to stop assigning tasks without coaching or a transition plan can cause confusion, loss of direction, and resistance; it addresses the symptom, not the root cause. Option C is wrong because removing the leader from the team is a drastic, disruptive action that eliminates a potentially valuable coach and facilitator; servant leadership is about transforming the leader's behavior, not eliminating the role.

Practice this question →
27
Multi-Selecthard

Which TWO approaches help an organization move from a 'Command and Control' mindset to an Agile mindset?

Select 2 answers
A.Standardizing all workflows across the company to ensure maximum control.
B.Decentralizing decision-making to the people closest to the work.
C.Encouraging self-organization and team autonomy.
D.Establishing a strict hierarchy where all decisions flow from the top down.
E.Replacing all project managers with external auditors to monitor compliance.
AnswersB, C

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.

Why this answer

Option B is correct because decentralizing decision-making to the people closest to the work shifts authority away from a top-down command-and-control structure and empowers those with the most direct knowledge to make timely decisions, which is a core Agile principle. Option C is correct because encouraging self-organization and team autonomy lets teams manage their own work and adapt to change, directly countering the rigid control and micromanagement typical of a Command and Control mindset. Options A, D, and E are incorrect because standardizing all workflows for maximum control, enforcing a strict top-down hierarchy, and replacing project managers with external compliance auditors all reinforce centralized control and oversight rather than fostering the empowerment, trust, and flexibility that Agile requires.

Exam trap

PMI-ACP often tests the false equivalence that 'standardization' or 'governance' equals Agile maturity, luring candidates toward options that sound disciplined but actually reinforce command-and-control.

Practice this question →
28
Multi-Selecteasy

Which TWO of the following are benefits of an Agile mindset?

Select 2 answers
A.Improved team collaboration and satisfaction
B.Less need for communication
C.More predictable, fixed-scope projects
D.Elimination of all documentation
E.Faster delivery of value to the customer
AnswersA, E

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.

Why this answer

Option A is correct because an Agile mindset emphasizes self-organizing, cross-functional teams that collaborate closely through practices like daily standups and retrospectives, which measurably improves team morale and satisfaction. Option E is correct because Agile prioritizes delivering working, valuable increments to the customer in short iterations, enabling faster realization of business value compared with sequential waterfall delivery. The unmarked options do not belong: B is wrong because Agile increases, not reduces, communication through frequent ceremonies and feedback loops; C is wrong because Agile embraces emergent, evolving scope rather than fixed-scope predictability; and D is wrong because Agile values working software over comprehensive documentation but still requires sufficient documentation, not its elimination.

Exam trap

PMI-ACP often tests the misconception that Agile means 'no documentation' or 'no planning' — candidates must recognize that Agile values working software over comprehensive documentation, not the elimination of documentation.

Practice this question →
29
MCQhard

A team member is constantly 'gold-plating' (adding features not asked for). How do you address this?

A.Encourage them to do more gold-plating.
B.Explain the value of meeting the current goals and the 'Definition of Done'.
C.Fire them.
D.Ignore it.
AnswerB

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.

Why this answer

Gold-plating adds features not requested, which can increase complexity, risk, and cost without delivering value. The best approach is to explain the value of meeting current goals and adhering to the Definition of Done, which defines the scope of work for a user story. This aligns the team member with Agile's focus on delivering only what is needed.

Exam trap

PMI-ACP often tests the misconception that adding extra features is always beneficial — candidates must recognize that gold-plating is a form of waste and should be addressed through clear communication of the Definition of Done.

How to eliminate wrong answers

Option A is wrong because encouraging more gold-plating exacerbates the problem, leading to scope creep and wasted effort. Option C is wrong because firing is an extreme, punitive response that does not address the behavior or foster a learning culture. Option D is wrong because ignoring gold-plating allows it to continue, undermining the team's ability to meet commitments and deliver value.

Practice this question →
30
MCQmedium

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

A.The team needs to work longer hours.
B.The team needs to look at their commitment and estimation practices.
C.The team is incompetent.
D.The team is under-performing.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
31
MCQhard

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

A.Evaluate the change's value and discuss the impact with the PO.
B.Tell them it's too late.
C.Charge the stakeholder for the rework.
D.Do the change immediately without question.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
32
MCQhard

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

A.Use a facilitation technique like 'silent brainstorming' or 'anonymous cards'.
B.Call on people one by one.
C.Threaten to report the team's silence to the manager.
D.End the meeting early.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
33
MCQmedium

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

A.Tell them what to change.
B.Say no, because the current process works.
C.Wait for management approval.
D.Support their experiment and help them measure the outcome.
AnswerD

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
34
MCQeasy

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

A.Having clear instructions.
B.Being able to take risks without fear of punishment.
C.Working in a quiet environment.
D.Having high pay.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
35
Multi-Selectmedium

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

Select 2 answers
A.Writing documentation once and never reviewing it
B.Creating comprehensive documentation before starting any work
C.Mandating that all documents be signed by management
D.Writing only the documentation that is necessary
E.Ensuring documentation is kept up-to-date as the product evolves
AnswersD, E

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

Why this answer

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

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

Exam trap

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

Practice this question →
36
MCQmedium

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

A.Updating the product backlog based on user feedback.
B.Rejecting all feedback until the next project phase.
C.Changing the team members every sprint.
D.Strictly following the initial project roadmap.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
37
MCQeasy

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

A.The team always completes 100% of the work.
B.Team members feel safe to voice concerns.
C.No one ever disagrees.
D.The team follows the manager's instructions.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
38
MCQeasy

What is the goal of a servant leader?

A.To report to the board on team failure.
B.To command and control the team.
C.To remove obstacles and empower the team.
D.To make all technical decisions.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
39
MCQmedium

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

A.Fire the team and start over.
B.Assess current practices against Agile principles.
C.Force them to adopt a specific framework.
D.Do nothing, as long as they deliver.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
40
MCQhard

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

A.Discuss the change with the Product Owner to evaluate its impact on the Sprint Goal and potential trade-offs.
B.Ask the team to work overtime to accommodate the new requirement.
C.Immediately add the change to the current sprint backlog to satisfy the stakeholder.
D.Refuse the change entirely because the Sprint Plan is fixed.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
41
MCQmedium

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

A.Replacing people faster.
B.Lowering the performance expectations.
C.Investigating the team culture and working conditions.
D.Hiring more senior developers.
AnswerC

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
42
Multi-Selecthard

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

Select 2 answers
A.The team takes collective responsibility for outcomes
B.The team is granted the autonomy to choose how to do their work
C.Each team member works in complete isolation
D.The manager makes all the decisions
E.Strict adherence to the original plan
AnswersA, B

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

Why this answer

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

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

Exam trap

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

Practice this question →
43
MCQhard

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

A.Ask them to prototype both options to see which works best.
B.Force them to compromise on a sub-optimal design.
C.Choose the design you prefer.
D.Tell them to flip a coin.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
44
MCQmedium

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

A.Have the team strictly adhere to the acceptance criteria and explain to stakeholders that the criteria were met, so expectations should align.
B.Invite stakeholders to participate in refinement sessions to clarify and evolve acceptance criteria collaboratively.
C.Schedule a separate meeting after each sprint review to gather feedback and update the backlog accordingly.
D.Ask the product owner to create more detailed acceptance criteria and distribute them to stakeholders for sign-off before each sprint.
AnswerB

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

Why this answer

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

Exam trap

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

Practice this question →
45
MCQhard

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

A.Quietly mentor the individual on the value of team collective ownership.
B.Fire the individual.
C.Ignore it since the individual is productive.
D.Promote the high-performer to a lead role.
AnswerA

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
46
Multi-Selectmedium

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

Select 3 answers
A.Preference for command-and-control management
B.Commitment to empirical process control (inspect and adapt)
C.Valuing team self-organization over individual direction
D.Relentless focus on delivering value to the customer
E.Strict avoidance of any project documentation
AnswersB, C, D

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

Why this answer

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

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

Exam trap

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

Practice this question →
47
MCQhard

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

A.Facilitate a team working agreement session to clarify how the team will make decisions and pull work.
B.Escalate to the program manager to define a single prioritization owner and task allocation process.
C.Create a RACI chart that assigns decision rights and task ownership for all team activities.
D.Ask each department manager to assign tasks to their people so accountability is clear.
AnswerA

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

Why this answer

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

Exam trap

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

Practice this question →
48
Multi-Selecthard

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

Select 2 answers
A.Communicate the change impact to stakeholders transparently
B.Assess the impact on the current iteration
C.Always say yes to every change requested
D.Implement the change silently without telling the team
E.Reject all changes to protect the original plan
AnswersA, B

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

Why this answer

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

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

Exam trap

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

Practice this question →
49
MCQmedium

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

A.Ask them to provide their own plan.
B.Explain that Agile planning is iterative and focus on the upcoming release goals.
C.Tell them to wait for the final product.
D.Create a detailed plan to satisfy them.
AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Practice this question →
50
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.

Practice this question →
51
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.

Practice this question →
52
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.

Practice this question →
53
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.

Practice this question →
54
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.

Practice this question →
55
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.

Practice this question →
56
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.

Practice this question →
57
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.

Practice this question →
58
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.

Practice this question →
59
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.

Practice this question →
60
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.

Practice this question →
61
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.

Practice this question →
62
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.

Practice this question →
63
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.

Practice this question →
64
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.

Practice this question →
65
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.

Practice this question →
66
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.

Practice this question →
67
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.

Practice this question →
68
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.

Practice this question →
69
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.

Practice this question →
70
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.

Practice this question →
71
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.

Practice this question →
72
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.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Mindset questions.

Start 20-question session