PMI-ACP PMI Agile Certified Practitioner (PMI-ACP) Questions and Answers

In agile, information radiators—such as visual boards placed in common areas—are used to make project data accessible, transparent, and real-time. According to the PMI Agile Practice Guide (Section 7.1 Communication), visibility improves coordination across interdependent teams.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) recommends that agile teams use visible, shared artifacts such as task boards, burn charts, or Kanban walls to improve cross-team communication and reduce friction.

Option B is correct: a physical or virtual board offers transparency and encourages informal communication.

Option A is useful but not as effective for rapid visibility.

Option C is one-way and doesn’t support real-time updates.

Option D is reactive and could cause delays or misalignment.

The correct answer is D – Stop updating the documentation and initiate an analysis to identify its value and act on the findings.

Agile promotes the creation of “just enough” documentation. If a document isn’t being used and adds no value, the team should reflect on whether to discontinue or improve it. Retrospectives are the appropriate venue to identify such inefficiencies and implement continuous improvement.

From the Agile Manifesto (referenced in PMI Agile Practice Guide):

“Working software over comprehensive documentation.”

From the PMI Agile Practice Guide:

“Agile teams minimize non-value-added work. If documentation is not being used or reviewed, teams should examine whether it is necessary, and if not, discontinue or replace it.”

(PMI Agile Practice Guide, Section 7.1 – Continuous Improvement)

Mike Griffiths adds:

“Documentation should serve a purpose. If stakeholders do not find value in it, the team should discontinue or refactor it to meet actual needs.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement)

Why the other options fall short:

A prolongs the wasteful practice unnecessarily.

B lacks the analysis needed before eliminating documentation.

C enforces process over value, which contradicts Agile principles.

Answer: D

══════════════════════════════════════════════════

In Agile, it ' s important to maintain focus on the current sprint ' s goals and scope. Since the sprint deadline is approaching, adding additional features may compromise the team ' s ability to deliver the planned work on time. The best approach is to explain to the client that the new features can be considered for the next sprint, ensuring that the team can finish the current work and deliver value on time. This also allows the team to properly plan for the new features in the next iteration without overloading the current sprint.

This approach reinforces the core values of agile, particularly the idea that a self-managed team should be collaborative and support one another. The agile lead should focus on creating a safe environment where team members feel comfortable sharing challenges and asking for help. This will not only help the junior team member but also improve the overall team dynamics and performance by fostering a culture of openness and mutual support.

Kanban is a visual management tool that helps teams improve workflow efficiency. One of its key principles is the use of a pull system, where work is pulled into the process when capacity allows, rather than being pushed into the system. This contrasts with a push system, where work is assigned or forced into the workflow regardless of capacity. This approach helps avoid bottlenecks and ensures work is handled efficiently.

In agile, when uncertainty exists around a technical or functional aspect of work, the team can use a spike—a time-boxed research or prototyping activity—to explore the unknown. According to the PMI Agile Practice Guide (Section 5.2 User Stories and Spikes), spikes are ideal when the team lacks information or confidence about a proposed solution and needs to experiment before committing.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that spikes are used to investigate technical approaches, prove concepts, or explore new technologies, and they provide the team with the insight and confidence needed to proceed with less risk.

Option A is correct because a spike would allow the team to explore the new framework in a controlled way.

Other options such as Ishikawa diagrams (B), pre-mortems (C), and trend analysis (D) are useful in other contexts, but not suitable for increasing confidence in new technical implementation approaches.

Given the global distribution of the stakeholders and their high interest in the project (as indicated in the stakeholder power/interest grid), a dynamic feedback platform is the most effective way to ensure consistent engagement. By leveraging collaboration tools that allow asynchronous feedback, the team can accommodate stakeholders in different time zones, reducing the delay in obtaining feedback and helping to speed up the decision-making process. This approach ensures that all stakeholders can contribute when it’s convenient for them, without the need for synchronized meetings, thus improving overall engagement and decision-making efficiency.

The correct answer is A – Kaizen. Kaizen is a Japanese term meaning " continuous improvement. " In Agile, Kaizen refers to the practice of regularly reflecting on processes and results, then making incremental improvements. By tracking impediments and resolving them transparently, the team engages in Kaizen behavior.

From the PMI Agile Practice Guide:

“Agile teams embrace a mindset of continuous improvement (Kaizen), regularly inspecting their work and processes and adapting them for better outcomes.”

(PMI Agile Practice Guide, Section 6.6 – Continuous Improvement)

Mike Griffiths writes:

“Agile is rooted in lean thinking, including Kaizen. Teams reflect on what went well and what needs to change, often using tools like Kanban boards to visualize and track improvements.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

B refers to goal-setting, not process improvement.

C are metrics, not an outcome of experimentation.

D (Muda) refers to waste, which Kaizen seeks to reduce.

Answer: A

────────────────────────────────────

The correct answer is A – Plan activities that will require the team to work collaboratively on a regular basis.

Agile teams thrive on collaboration, shared ownership, and collective problem solving. While individual performance may meet goals short-term, long-term value and quality come from integrated teamwork. An agile practitioner should help foster collaboration through team-building activities or practices like pair programming, collective backlog grooming, and swarming.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing and collaborative. Encouraging collaborative practices builds trust, increases quality, and improves alignment.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths states:

“Collaboration does not happen automatically—it must be supported. Facilitating shared work and group problem-solving leads to stronger team dynamics and better outcomes.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why the other options are less effective:

B introduces rigid evaluation that contradicts agile values.

C bypasses coaching and assumes the current team can’t improve.

D ignores the growing problem of misalignment and disengagement.

Answer: A

══════════════════════════════════════════════════

The in-person demonstration meeting is crucial because it allows the team to directly engage with the product owner, ask clarifying questions, and immediately address any feedback or concerns. This fosters better communication, understanding, and collaboration between the team and the product owner. Being able to have a real-time conversation helps the team ensure they are building the right product, and it allows the product owner to provide nuanced feedback that might not be as clear through asynchronous communication (like sending a link).

The face-to-face interaction provides an opportunity for both parties to align more effectively on the product vision, avoid misunderstandings, and prevent misalignment on priorities, ultimately ensuring that the product being developed meets expectations.

The correct answer is A – Facilitate a team discussion to identify knowledge gaps and determine the best way to address them.

The agile coach ' s role is to foster team ownership and encourage collaborative problem solving. When knowledge gaps are uncovered, the first step is to create transparency and engage the team in identifying how to resolve the gap—through pairing, mentoring, spikes, or backlog adjustments.

From the PMI Agile Practice Guide:

“Agile leaders coach teams to self-identify impediments and explore solutions collaboratively. Coaching helps teams build awareness and take ownership of their development and process improvements.”

(PMI Agile Practice Guide, Section 6.2 – Coaching the Agile Team)

Mike Griffiths adds:

“Rather than providing direct solutions, agile coaches should help teams uncover their own improvements through retrospection, facilitated discussion, and group problem solving.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement / Coaching)

Why the other options fall short:

B and C externalize the problem instead of building team capability.

D may be part of the solution, but the team should explore it collectively—not as a unilateral decision.

Answer: A

══════════════════════════════════════════════════

The correct answer is A — Lead the team and help them to constantly improve the processes in the project.

The Scrum Master is responsible for ensuring that retrospective action items are tracked and followed up on. While the team owns the improvement actions, the Scrum Master provides support, accountability, and facilitation to ensure that continuous improvement happens.

PMI Agile Practice Guide:

“The Scrum Master facilitates continuous improvement by helping the team reflect, identify actions, and ensure those actions are implemented.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths:

“Retrospectives are only effective if outcomes are tracked. The Scrum Master ensures improvement ideas are not forgotten and become part of the team’s evolution.”

(PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

B uses a confrontational tone—contrary to servant leadership.

C implies micro-management and contradicts self-organization.

D avoids responsibility for facilitating improvements.

Answer: A

—

In an adaptive environment, the project manager’s role is focused on facilitating collaboration and communication among stakeholders, teams, and sponsors to ensure that decisions are made quickly and effectively as circumstances change. This aligns with the agile principle of collaboration over contract negotiation and emphasizes adaptability and the ability to respond to changing needs. While project managers may still contribute to planning and other activities, fostering a collaborative and flexible decision-making process is key in an adaptive environment.

In Agile, ensuring that the product works without bugs or missing features can be achieved through continuous testing and validation of the product. Test-driven development (TDD) is an approach where tests are written before the code is developed. This helps ensure that each feature is fully tested as it is built, focusing on customer requirements from the start and preventing issues from accumulating. By using TDD, the product owner ensures the product is being tested incrementally, which reduces the risk of defects and aligns with customer expectations for a high-quality product upon release.

The correct answer is A – Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.

Sprint reviews are designed to showcase the completed product increment to stakeholders and receive feedback. The primary goal is to validate that the work delivered provides value to the customer—not to present technical details. Demonstrating working software is one of the core tenets of Agile.

From the PMI Agile Practice Guide:

“Sprint reviews are working sessions designed to elicit feedback and foster collaboration. Teams demonstrate completed work and adjust the backlog based on stakeholder input.”

(PMI Agile Practice Guide, Section 5.3 – Value Delivery)

Mike Griffiths confirms:

“The output of every iteration should be potentially shippable product. The sprint review is for stakeholders to see that output and provide feedback to inform future development.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 2 – Value-Driven Delivery)

Other options explained:

B may be helpful, but it doesn’t solve the immediate issue of misaligned sprint reviews.

C misunderstands the purpose of the sprint review—it’s not about architecture.

D changes the audience instead of correcting the approach.

Answer: A

══════════

The correct answer is C — The stakeholders will learn whether or not the implementation has worked by getting immediate feedback so they can correct their assumptions for the next sprint.

Agile welcomes stakeholder involvement throughout the project lifecycle. Demos (also called sprint reviews) are critical opportunities for stakeholders to inspect the product increment and provide feedback, which helps teams pivot or adapt early and often. Immediate feedback reduces the risk of building features that do not meet business needs.

PMI Agile Practice Guide:

“Iteration reviews/demos provide stakeholders with the opportunity to see working product increments and offer feedback while there is still time to make changes.”

(PMI Agile Practice Guide, Section 5.7 – Reviews and Demos)

Mike Griffiths supports this by stating:

“Engaging stakeholders during sprint reviews allows assumptions to be challenged early. This feedback loop ensures value alignment and reduces the likelihood of rework.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Other options:

A incorrectly distances stakeholders from essential agile feedback cycles.

B shifts focus away from value to effort-based metrics.

D is more about long-term ROI, not immediate iterative feedback.

Answer: C

—

The correct answer is A – Send the member to training. Agile encourages cross-functional teams and continuous improvement. When a team member identifies a skill gap that affects delivery, addressing it promptly through training or mentoring increases team capability and autonomy.

From the PMI Agile Practice Guide:

“Agile teams strive for cross-functionality. When skill gaps hinder progress, organizations support learning to reduce dependencies and improve throughput.”

(PMI Agile Practice Guide, Section 4.3 – Continuous Learning and Team Development)

Mike Griffiths adds:

“Empowering team members through skill development enhances flexibility and velocity. Encouraging proactive learning improves team performance.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

B defers ownership of the solution.

C unnecessarily delays action.

D delays learning due to unnecessary constraints.

Answer: A

────────────────────────────────────

Agile principles emphasize just-in-time (JIT) planning and design, meaning work should not begin until it ' s pulled into the current sprint or iteration. According to the PMI Agile Practice Guide (Section 5.4 Iteration Planning) and Mike Griffiths (Chapter 6: Adaptive Planning), teams should focus on committed iteration work and avoid speculative work that is not yet planned or prioritized.

Designing item B early introduces unvalidated assumptions and risks rework if priorities or requirements change. Agile encourages deferring decisions until the last responsible moment to preserve flexibility.

Option A is correct: the team should wait until item B is formally planned before investing effort.

Option B violates agile principles by introducing premature work.

Option C and D suggest formal escalation that is unnecessary and not in the spirit of agile’s decentralized decision-making.

A user story that is too large to complete in one sprint is considered an epic. Agile teams should split it into smaller, valuable, testable stories. The PMI Agile Practice Guide (Section 5.2: User Stories and Decomposition) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend breaking down large stories and renegotiating sprint scope collaboratively with the product owner.

Option C is correct: this aligns with collaborative planning and story decomposition.

Option A is rigid and dismisses collaboration.

Option B promotes unsustainable practices.

Option D violates the principle of fixed-length iterations.

The correct answer is D – Create a collaborative team environment so that the team can explore a solution together. Agile emphasizes self-organization, teamwork, and collective ownership of problem-solving. The Scrum Master facilitates, not dictates, and enables the team to resolve impediments through collaboration.

From the PMI Agile Practice Guide:

“The Scrum Master helps the team identify, address, and remove impediments. This is often done by fostering an environment of open communication and team problem-solving.”

(PMI Agile Practice Guide, Section 6.5 – Problem Detection and Resolution)

Mike Griffiths elaborates:

“Rather than escalate or assign responsibility, the Scrum Master enables the team to work together to solve problems. This builds trust, increases team capability, and supports agile values.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A and B promote a command-and-control approach, which violates agile values.

C defers the solution to a future sprint, rather than solving it now.

Answer: D

────────────────────────────────────

The correct answer is D – Turn the requests into user stories and prioritize them. In agile, all feature requests must be expressed in the form of user stories and added to the product backlog. Once added, they are prioritized collaboratively with the product owner and stakeholders, usually based on value, risk, and effort.

From PMI Agile Practice Guide:

“Product backlog refinement includes breaking down large items into user stories, reprioritizing items, and ensuring they are properly understood by the team. This activity is critical in ensuring the right items are worked on at the right time.”

(PMI Agile Practice Guide, Section 5.2 – Product Backlog Refinement)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile teams transform customer needs into user stories during backlog grooming. These are then prioritized by the product owner to ensure maximum value is delivered early.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Option A ignores customer needs. Option B (ordering by complexity) does not consider value. Option C skips the important step of converting feature requests into properly structured backlog items.

Answer: D

=========

The correct answer is C – Asked to be relieved of project tasks to maintain team velocity.

Agile promotes transparency and accountability within teams. When a team member becomes unavailable due to competing priorities, it is their responsibility to inform the team so that work can be reallocated appropriately. This maintains the integrity of sprint commitments and avoids unplanned impacts on velocity.

From the PMI Agile Practice Guide:

“Team members are expected to proactively communicate capacity issues. Agile teams thrive when individuals are transparent about availability and workload, allowing adjustments to commitments.”

(PMI Agile Practice Guide, Section 4.1 – Agile Mindset and Team Behavior)

Mike Griffiths states:

“If someone’s availability changes, they must make that clear to the team. Holding on to tasks without capacity leads to velocity distortion and delivery issues.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why other options are incorrect:

A attempts to do both initiatives, which may result in burnout or failed delivery.

B focuses effort away from the agile team’s responsibilities.

D is unrealistic in cross-functional organizations where members may support multiple initiatives.

Answer: C

══════════════════════════════════════════════════

In Agile, change is considered a natural part of the process, as requirements evolve based on feedback and new insights. The Scrum Master should help the team understand that changes are an opportunity to improve the product and deliver more value to the stakeholders. While it ' s important to manage changes effectively, it ' s also crucial to communicate that continuous improvement and adaptation are integral parts of Agile practices. The Scrum Master should foster a positive environment where change is seen as a way to better meet the customer ' s needs rather than a hindrance to performance.

The correct answer is D – Make use of a Kanban board so that the team will have a clear view of the work in progress (WIP) for the release.

Agile teams use information radiators like Kanban boards to visualize work, improve flow, identify bottlenecks, and maintain team focus. Visibility of work enhances self-organization and accountability while reducing ambiguity and delays.

From the PMI Agile Practice Guide:

“Kanban boards provide visibility into the work in progress. They support collaboration, improve team focus, and are effective in both Scrum and Kanban approaches.”

(PMI Agile Practice Guide, Section 5.1 – Visual Controls)

Mike Griffiths writes:

“Visual tools such as task boards and Kanban boards allow the team to manage their flow and workload. This enables collaboration and transparency without micromanagement.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why the other options fall short:

A introduces unnecessary meetings, potentially disrupting flow.

B may lead to micromanagement and undermine team ownership.

C implies a command-and-control style, which is contrary to Agile principles.

Answer: D

The correct answer is A — A formalized agile approach offers controlled flexibility in dealing with unknown variables in a manner that adds business value.

Agile is designed to operate effectively under conditions of high uncertainty. It allows for controlled experimentation, feedback loops, and adaptive changes, all while maintaining a focus on delivering business value. This makes it ideal for environments reliant on data analytics and frequent changes.

PMI Agile Practice Guide:

“Agile approaches provide the flexibility to respond to changing conditions and unknowns while ensuring that value delivery remains aligned with stakeholder needs.”

(PMI Agile Practice Guide, Section 2.2 – Agile Principles)

Mike Griffiths:

“Agile’s incremental delivery model enables teams to validate assumptions and adapt based on feedback and data—making it a natural fit for data-driven organizations.”

(PMI-ACP Exam Prep, Chapter 1 – Agile Principles and Mindset)

Incorrect options:

B is factually incorrect and overly simplistic.

C misrepresents agile as a formal change-control process.

D is an opinion, not a principle.

The correct answer is A – Perform value stream analysis to eliminate the processes with wastage. Value stream mapping is a lean and agile technique used to identify and eliminate non-value-adding activities, optimize flow, and increase delivery efficiency—especially crucial when facing tight deadlines.

From PMI Agile Practice Guide:

“Value stream mapping is used to analyze the flow of materials and information required to bring a product or service to a consumer. It helps teams eliminate waste and improve speed and quality.”

(PMI Agile Practice Guide, Section 6.4 – Continuous Improvement and Feedback Loops)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Value stream analysis is a lean technique that helps agile teams identify delays, bottlenecks, and handoffs that waste time. When velocity lags behind expectations, understanding the end-to-end process is essential to improvement.”

(Mike Griffiths, Chapter 7 – Continuous Improvement)

Option B (removing high-risk stories) may introduce more long-term risk and undermine value.

Option C suggests manipulating metrics instead of addressing root causes.

Option D may help identify risks early, but it doesn’t address why velocity is low.

Answer: A

The correct answer is D — Create a space on the board to prioritize the threats, along with an update on the actions that are in progress and what still needs to be done.

Agile promotes visual management and transparency. By using a dedicated section on the team board (information radiator), risks can be prioritized, tracked, and made visible to the entire team, enabling ongoing awareness and proactive response.

PMI Agile Practice Guide:

“Information radiators can be used to display risk burndown charts, prioritization, and mitigation plans, allowing teams to manage and address risk openly.”

(PMI Agile Practice Guide, Section 7.3 – Risk Management)

Mike Griffiths:

“Making risks visible and tracking them alongside features fosters collective ownership and ensures proactive handling.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A is reactive and lacks persistent visibility.

B may create fatigue and be seen as micromanagement.

C involves the sponsor unnecessarily and doesn’t address day-to-day risk management.

Answer: D

—

The correct answer is B — Balance risk reduction and value-adding activities in the next iteration.

Agile recommends actively managing risks as part of iteration planning. While delivering customer value remains a top priority, severe risks should be mitigated as early as possible. The team should consider allocating capacity in the next sprint to reduce risk while still maintaining delivery focus.

PMI Agile Practice Guide states:

“Agile teams incorporate risk mitigation work into iteration planning. Teams should prioritize high-impact risks early and balance risk management with delivering customer value.”

(PMI Agile Practice Guide, Section 7.3 – Agile Risk Management)

Mike Griffiths supports this:

“Agile does not separate risk management into a different process—it is embedded within backlog prioritization. Addressing risk early can prevent downstream impacts, and teams must weigh risk vs. value regularly.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A disrupts current iteration goals and contradicts agile time-boxing.

C ignores the severity of the risk.

D escalates unnecessarily—agile promotes team-level decision-making first.

Answer: B

—

The correct answer is A – Add code cleanup activities to the product backlog and request prioritization by the product owner. In Agile, technical debt should be made visible and managed like any other backlog item. The product owner is responsible for backlog prioritization and must balance feature delivery with quality-related tasks.

From the PMI Agile Practice Guide:

“Technical debt should be made transparent and included in the product backlog. Teams should advocate for addressing it, and the product owner prioritizes its resolution based on the impact to future work.”

(PMI Agile Practice Guide, Section 5.5 – Technical Debt)

Mike Griffiths’ guidance reinforces this:

“Technical debt erodes long-term productivity and must be tracked and addressed. Agile teams collaborate with product owners to prioritize and schedule code cleanup or refactoring activities.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

B and C bypass the product owner’s prioritization role.

D delays action unnecessarily and misrepresents Agile’s emphasis on transparency and early resolution.

Answer: A

Velocity is a team-specific metric and cannot be reliably estimated until the team has worked together for several sprints. According to the PMI Agile Practice Guide (Section 5.4 Sprint Planning and Velocity Tracking), velocity should be measured empirically, not predicted based on assumptions or external input.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Adaptive Planning) emphasizes that new teams need to run a few sprints to establish a reliable velocity through real performance data, not estimation.

Option D is correct: actual performance determines true velocity.

Option A and B rely on speculation.

Option C incorrectly uses sponsor input for team planning, which goes against agile principles.

The product owner should work closely with the team to ensure that the most critical features are prioritized and clearly understood. Inviting the customer to the sprint planning meeting helps ensure that the team has a direct understanding of what is most important to the customer and their business needs. This fosters collaboration and ensures the team works on the most valuable features first.

Additionally, refining the product backlog and identifying the Minimum Viable Product (MVP) ensures the team knows the minimum set of features required for the product to provide value to the customer. By focusing on the MVP, the team can quickly deliver a product that addresses the core needs, enabling faster feedback and iterations.

The correct answer is B – It prevents a wasteful buildup of requirements inventory that may never be processed. Rolling wave planning is a core agile planning practice where detailed planning is deferred until closer to execution. It aligns with lean principles by avoiding over-specification and prioritizing only near-term, high-value work.

From the PMI Agile Practice Guide:

“Rolling wave planning minimizes wasted effort by only detailing work that is near execution. Planning further ahead can result in rework or unused artifacts if requirements change or become irrelevant.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning and Rolling Wave Planning)

Mike Griffiths writes:

“Agile avoids big upfront planning. Rolling wave planning reduces waste, improves responsiveness, and focuses on delivering the highest-value features first while leaving less valuable work unplanned until necessary.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A is misleading; agile allows varying levels of detail, not fixed.

C is a traditional (waterfall) planning mindset.

D suggests fixed scope per release, which contradicts agility.

Answer: B

────────────────────────────────────

Delivering value in agile depends on frequent prioritization and real-time feedback. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Prioritization), product owners and agile teams must continuously reprioritize the backlog based on changing stakeholder needs, market shifts, and feedback. Failure to do so can result in building the wrong product—even if it ' s " done. "

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) stresses that value delivery is iterative and depends on current priorities, not static backlogs. It is vital that teams confirm that they ' re working on the highest-value items before committing to a sprint.

Option A is correct: proper backlog refinement and reprioritization ensures alignment with evolving stakeholder needs.

Option B is an anti-pattern; agile welcomes change even late in development.

Option C and D are irrelevant or do not address the core issue of prioritization.

Once scope and acceptance criteria are known, the next step is to estimate the size and effort of backlog items, which enables planning. The PMI Agile Practice Guide (Section 5.2: Backlog Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend using estimation techniques (e.g., story points, T-shirt sizing) to determine the relative effort of each backlog item before performing release or sprint planning.

Option D is correct: backlog estimation enables velocity-based forecasting.

Option A and B come after estimation is complete.

Option C is too narrow—iteration planning comes later.

The Scrum Master should act as a facilitator and protect the team from unnecessary distractions that do not add value. By attending the meetings in place of the team members, the Scrum Master can assess the meetings ' value and determine if they are essential to the team ' s progress. If the meetings are unnecessary or inefficient, the Scrum Master can work with stakeholders to improve or remove them, ensuring that the team’s time is used productively and that they can focus on delivering value.

In this situation, the most practical solution is to reduce the scope of the release to meet the deadline. Since one team member will be absent, causing a reduction in velocity, the team may not be able to complete all planned work in the time remaining. By reducing the scope, the team can focus on delivering the most critical features for the industry fair and ensure that the release is still valuable and on time. This aligns with Agile principles of prioritizing the most valuable work and delivering iteratively based on available capacity.

The correct answer is A – Be transparent with all the stakeholders and make them aware of the issues encountered and the current project ' s status.

Agile encourages transparency and regular stakeholder engagement to ensure alignment and avoid surprises. Even if a stakeholder prefers minimal involvement, it is the team’s responsibility to raise issues that could impact delivery, especially if they introduce risk or require input.

From the PMI Agile Practice Guide:

“Agile promotes transparency and ongoing stakeholder engagement. Teams should proactively communicate risks and emerging issues to build trust and enable timely decision-making.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths notes:

“Transparency is one of the pillars of Agile. Teams must keep stakeholders informed—even those who prefer limited involvement—to ensure that value is continuously delivered.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options explained:

B is a secondary action; transparency should come first.

C risks late discovery and undermines agile values.

D removes responsibility from the team, which contradicts self-management.

Answer: A

═════════════

Stakeholder participation, especially during sprint reviews, is critical to agile success. The PMI Agile Practice Guide (Section 7.2: Stakeholder Engagement) emphasizes the importance of actively engaging stakeholders throughout the project lifecycle, particularly during key ceremonies like sprint reviews, where feedback shapes the product.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) states that stakeholders need to understand the value of their input and how it influences product direction. The agile practitioner or Scrum Master should educate and influence stakeholders by demonstrating the tangible impact of their participation.

Option D is correct: aligning stakeholders with the benefits of engagement fosters participation.

Option A, B, and C are passive substitutes and don’t address the root issue of stakeholder disengagement.

In an Agile environment, fostering a culture of collaboration and effective communication is key to success, especially when working with a diverse team. By creating a shared vision, the project manager aligns the team towards common goals, which helps reduce misunderstandings. Using techniques to increase empathy and positive interaction ensures that team members understand and respect each other ' s different perspectives. This approach promotes a collaborative environment where diverse ideas can be valued and conflicts can be addressed constructively.

In agile, early and frequent feedback from stakeholders and clients is critical to ensure that what is being built delivers the intended value. The PMI Agile Practice Guide (Section 5.5 and Section 7.2.2) promotes regular product review sessions (e.g., sprint reviews) with stakeholders to validate progress and obtain immediate feedback.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 6: Value-Driven Delivery) explains that product validation is continuous and not left to the end of the project. Regular review sessions allow clients to confirm that the product meets expectations, reducing the risk of building the wrong solution.

Therefore, Option D is correct: holding product review sessions with the client aligns with agile values of transparency, collaboration, and value delivery.

The correct answer is C – Agile leader (e.g., Scrum Master). One of the key responsibilities of an agile leader is to protect the development team from external interruptions so that the team can maintain focus and maximize productivity.

From PMI Agile Practice Guide:

“The agile leader shields the team from outside disruptions to allow them to remain focused on their commitments. They work to establish working agreements, communication protocols, and help manage stakeholder access to the team.”

(PMI Agile Practice Guide, Section 6.1 – Responsibilities of the Agile Leader)

From PMBOK® Guide – 7th Edition (tailoring for agile environments):

“Leaders in agile environments facilitate communication, clear obstacles, and protect teams from disruptions and distractions that can compromise the team’s ability to deliver value.”

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Scrum Masters and agile leaders act as gatekeepers to the team, ensuring that stakeholder interactions are managed and that the team can focus on iteration goals.”

(Mike Griffiths, Chapter 4 – Team Performance)

Option A (Product owner) is responsible for backlog clarity, not for shielding the team from distractions.

Option B (Project manager) is not a standard agile role; agile uses roles such as Scrum Master or Agile Coach.

Option D (Developers) may address distractions, but it is the agile leader ' s role to proactively prevent them.

Answer: C

=========

The scrum master should first remind the team of the purpose and goals of each scrum event (such as the daily standup, sprint planning, sprint review, and retrospective) to ensure that they remain focused on their intended outcomes. The scrum master can then implement a policy that ensures discussions that deviate from the scope of the event are stopped. This approach keeps the team on track, prevents time-wasting conversations, and helps maintain the efficiency of the events.

This method empowers the team to stay focused on what is essential for each event and encourages self-management while still providing room for relevant discussions. In doing so, the team can achieve the desired outcomes of each scrum event without unnecessary delays.

The correct answer is A because an Agile leader, such as a Scrum Master, is a servant-leader and facilitator. The Scrum Master supports the development team by helping remove impediments and facilitating healthy team dynamics. When there is misalignment or interpersonal conflict, the Scrum Master should help the team explore the root causes and encourage self-directed resolution.

From PMI Agile Practice Guide:

“Agile coaches facilitate conflict resolution by helping individuals understand each other’s perspectives and guiding them to collaborative solutions. The goal is to promote team ownership of outcomes and reinforce healthy communication.”

(PMI Agile Practice Guide, Section 6.3 – Facilitating Agile Practices)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“The role of the Scrum Master is not to direct or micromanage the team, but to facilitate communication and remove barriers that prevent team members from collaborating effectively. In conflict scenarios, the Scrum Master should help the team uncover the root issue, then allow them to resolve it constructively.”

(Mike Griffiths, Chapter 4 – Team Performance)

Option B is slightly less effective than A because it escalates to the whole team before trying a focused resolution.

Option C abdicates responsibility and may allow conflict to worsen.

Option D contradicts agile’s emphasis on self-organizing teams.

Answer: A

=========

The correct answer is C – Facilitate a retrospective to identify areas of improvement.

In Agile, mistakes are viewed as learning opportunities. The Scrum Master should create a safe environment where the team can reflect, discuss issues openly, and identify ways to prevent similar mistakes in the future.

From the PMI Agile Practice Guide:

“Retrospectives provide a regular forum for teams to inspect and adapt. Teams discuss what went well, what didn’t, and how to improve. This supports continuous learning and performance enhancement.”

(PMI Agile Practice Guide, Section 3.5 – Iteration Retrospectives)

Mike Griffiths states:

“Mistakes are inevitable; agile teams embrace them to improve. Retrospectives are essential for structured reflection and action planning.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 – Continuous Improvement)

Why other options are less appropriate:

A may reinforce outdated or flawed processes.

B may help in quality control but does not address the mistake constructively.

D promotes fear and competition, which undermines team trust and collaboration.

Answer: C

Iteration reviews (or sprint reviews) are designed to demonstrate completed, potentially shippable product increments. According to the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance), the purpose of the iteration review is to showcase work that meets the Definition of Done (DoD) and to receive stakeholder feedback. Demonstrating incomplete or in-progress stories can mislead stakeholders about progress and reduce trust in the team.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) emphasizes the importance of showing only completed work to maintain transparency and clarity in stakeholder communication.

Option A is correct: only completed stories should be demoed to ensure expectations are managed effectively.

Option B and C are not part of the typical iteration review agenda unless explicitly required.

Option D is incorrect, as it blurs the line between done and in-progress work.

A product roadmap is a strategic plan that outlines the vision for the product, the business objectives that need to be achieved, and the timeframes for delivering key milestones or features. It provides a high-level overview of the product ' s development, aligning the team and stakeholders on the product ' s direction and the expected delivery timeline.

Product vision defines what the product aims to achieve and the value it will deliver to customers or the business.

Business objectives outline what the product aims to accomplish in terms of business impact, like increasing revenue or improving customer satisfaction.

Timeframes indicate when key milestones or releases are planned to occur, ensuring that progress can be tracked and expectations set.

This high-level structure is essential for guiding product development and keeping stakeholders aligned, without delving into the specific details of design or project management, which are more suited for other planning documents.

The correct answer is A — Stakeholders should have regularly been engaged to obtain feedback and reduce the functionality risk.

In Agile, stakeholder engagement and iterative feedback loops ensure that the solution being built is aligned with business value. Simply meeting documented requirements is insufficient. Agile practices such as demos and user feedback sessions minimize the risk of building features that fail to deliver value.

PMI Agile Practice Guide:

“Agile emphasizes ongoing stakeholder engagement. Demonstrating working software at the end of each iteration and gathering feedback ensures that the product is delivering business value.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths states:

“Value-driven delivery is achieved not just by delivering what was asked for, but by ensuring it actually meets customer needs. Regular feedback from stakeholders is critical to avoid building low-value features.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B refers to the lean principle of “decide as late as possible,” but feedback, not delay, would have addressed the issue.

C is unrelated to this context.

D lacks the collaborative engagement approach emphasized in Agile.

Answer: A

—

The correct answer is D — Suggest an iterative approach including timely engagement of all key stakeholders and hold regular review meetings.

Engaging stakeholders continuously and using iteration reviews to validate deliverables ensures that misunderstandings are addressed early. This is especially critical in situations where expectations were not met in previous projects. Agile thrives in environments that require responsiveness to feedback.

PMI Agile Practice Guide:

“Early and continuous stakeholder engagement and regular reviews help ensure alignment and satisfaction, especially when past experiences were negative.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths:

“Agile promotes iterative delivery and early validation, minimizing the risk of misaligned expectations and unmet requirements.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A and C are useful, but don’t directly prevent recurrence of the problem.

B is vague and lacks concrete action.

Answer: D

The correct answer is D – Meet with project stakeholders to review the backlog and determine if the scope should be adjusted. Agile emphasizes continuous stakeholder collaboration and delivering maximum value. If the remaining backlog may not contribute significant value, it’s prudent for the Product Owner to reassess scope and validate changes with stakeholders.

From the PMI Agile Practice Guide:

“Engage stakeholders continuously to review priorities and business value. If the product delivers sufficient value earlier than anticipated, the scope may be reduced or the project closed.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery)

Mike Griffiths adds:

“Early delivery of value allows teams to stop work that no longer serves business objectives. This requires transparent communication with stakeholders to validate scope adjustments.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A assumes authority without consulting stakeholders.

B doesn’t address the possible need for scope reduction.

C skips stakeholder validation before deployment decisions.

Answer: D

────────────────────────────────────

Understand the current progress:

The project is halfway through development.

The team has reached a stable velocity after 8 iterations.

Each sprint duration is two weeks.

Determine the remaining number of iterations:

Since the project is halfway completed, an equal amount of work remains.

If 8 iterations have been completed, 8 more iterations are required to complete the project.

Calculate the remaining time:

Each iteration (sprint) lasts 2 weeks.

8 iterations × 2 weeks per iteration = 16 weeks.

16 weeks = 4 months.

With a limited budget of $17,000 remaining, the product owner should prioritize features that provide the most value to the customer. This means considering the business needs, customer feedback, and potential value of each feature rather than focusing solely on completing all planned features. Features like the Reporting Module, which have not started and have a high estimated cost, might need to be reconsidered or deferred based on priority. By assessing which features deliver the most value to stakeholders and aligning with the overall objectives, the product owner can make the most efficient use of the remaining budget.

Estimation challenges are common among new agile teams. According to the PMI Agile Practice Guide (Section 5.2 Requirements and Estimating Techniques), improving estimation accuracy involves team collaboration, continuous feedback, and inspecting and adapting techniques such as Planning Poker, affinity estimation, or triangulation. These discussions should happen in dedicated planning or retrospective meetings, but estimation issues can be flagged and lightly discussed in daily scrums to initiate deeper review.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) advises that estimation is a team activity, not an individual one, and that teams learn and improve accuracy over time through feedback loops and shared insights.

Option B is correct because discussing estimating challenges—even briefly during daily scrums—raises team awareness and drives improvement.

Option A and C deal with symptoms rather than the root cause.

Option D suggests using metrics for performance evaluation, which contradicts agile values (Agile Manifesto: " Individuals and interactions over processes and tools " ).

The correct answer is D because organizational transformation to agile requires more than process changes—it requires a shift in mindset. Training teams on agile values and principles builds a shared foundation and helps foster commitment to agile ways of working.

From PMI Agile Practice Guide:

“Agile transformation requires attention to both practices and mindset. Leaders must help teams embrace agile values, empower decision-making, and promote an agile culture through education and active support.”

(PMI Agile Practice Guide, Section 2.1 – Organizational Change and Transformation)

From PMBOK® Guide – 7th Edition:

“Successful transformation begins with people understanding the why and how of agile. Change cannot happen effectively without adequate training and communication.”

(PMBOK Guide 7th Ed., Principle 1 – Be a Diligent, Respectful, and Caring Steward)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile success is rooted in the team’s understanding of core principles. Agile leaders must invest in developing a strong foundational mindset, as well as practices. Education is a critical enabler of sustainable agile adoption.”

(Mike Griffiths, Chapter 1 – Agile Principles and Mindset)

Option A is a partial strategy but doesn’t ensure cultural transformation.

Option B is necessary but not sufficient—buy-in alone won’t change behavior.

Option C is tactical and useful but doesn’t address team-wide mindset change.

Answer: D

In Scrum, the goal is to have open discussions during estimation, where all team members, including junior developers, can express their thoughts and assumptions. The Scrum Master should encourage the junior developers to keep their estimations because these can highlight different perspectives, constraints, or assumptions that others may not have considered. This helps create a more comprehensive understanding of the work and fosters a collaborative environment. It also builds confidence in junior team members, allowing them to contribute more effectively and learn from their peers in the process.

The correct answer is A – Conduct regular one-on-one meetings to review development features and trace them back to the product roadmap. Close collaboration between the agile leader (e.g., Scrum Master or Project Lead) and the Product Owner ensures alignment between the product strategy and development execution.

From the PMI Agile Practice Guide:

“Frequent and open collaboration between the Product Owner and agile project leader helps maintain alignment between delivery and business objectives. These discussions link work to roadmap-level planning.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths states:

“Agile leadership includes partnering with the Product Owner to ensure that work being done contributes to overall product goals. Roadmap alignment is critical.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

B is more appropriate for the Product Owner, not the project leader.

C implies waterfall-style communication.

D oversteps the Product Owner’s authority in setting feature priorities.

Answer: A

────────────────────────────────────

To kick off the project, especially when the idea is not yet clear, the agile lead should focus on understanding the needs and challenges of the end users—HR in this case. By applying the empathy map technique, the team can gather insights into the users ' experiences, needs, and pain points. This helps in building a more focused and user-centered approach to solving the problem, which is the foundation for developing a product backlog. Engaging stakeholders early and understanding the problem space will clarify the project direction and lay the groundwork for creating meaningful user stories.

The correct answer is C – Invite the new release manager to the sprint demo and ask for help. Agile encourages stakeholder collaboration and visibility. Sprint reviews (also known as demos) are key opportunities for stakeholders, including release managers, to engage directly with the team and provide feedback. Since the issue is related to environmental instability and the new release manager is a key stakeholder, involving them in the sprint review enables mutual understanding and sets the stage for collaboration.

From PMI Agile Practice Guide:

“Agile teams use the sprint review to present completed work to stakeholders and receive direct feedback. It is also an opportunity to engage stakeholders who can influence the delivery environment.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Agile encourages frequent stakeholder collaboration. Sprint reviews should include key stakeholders who are responsible for operational and release matters to ensure alignment.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Options A and D are passive approaches and may not lead to effective communication. Option B (attending daily standups) may be helpful but is not the best opportunity for strategic involvement compared to a sprint demo.

Answer: C

=========

According to the PMI Agile Practice Guide (Section 7.2.1), the Scrum Master’s role includes removing impediments and shielding the team from outside interference. A team member being pulled into work on a different project is a classic example of an impediment. Recording the issue in a risk register is appropriate, but more importantly, the Scrum Master must communicate and resolve the issue.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 3: Team Performance) emphasizes that agile teams require full dedication and protection from context switching, as multitasking reduces productivity and increases error rates. Merely documenting the issue is not enough—the Scrum Master must take steps to escalate and resolve the interference, potentially by negotiating with the former supervisor or re-clarifying role boundaries.

Therefore, Option C is correct as it involves actively addressing the threat rather than passively monitoring or adjusting around it.

Kanban is continuous and can lead to burnout or low morale due to lack of visible milestones. The PMI Agile Practice Guide (Section 5.7: Flow-based Agile) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance) suggest that recognizing and celebrating milestones or delivery points is essential to maintain motivation, especially in long-running Kanban teams.

Option A is correct: celebrating completed work gives the team a sense of closure and achievement, improving engagement.

Option B might help temporarily but doesn’t address the root motivational issue.

Option C adds pressure and is counterproductive.

Option D may improve flow but doesn ' t directly address the lack of visible progress recognition.

The correct answer is A – Facilitate team agreement on the definition of done (DoD) during the chartering process.

The “Definition of Done” is a shared understanding among the team of what it means for work to be considered complete. Disputes over whether a deliverable is done usually arise due to the lack of a clearly defined and agreed-upon DoD.

From the PMI Agile Practice Guide:

“Teams should define and agree on the Definition of Done (DoD) early. This shared understanding reduces ambiguity and misalignment over when a task is complete.”

(PMI Agile Practice Guide, Section 5.2 – Definition of Done and Acceptance Criteria)

Mike Griffiths emphasizes:

“The Definition of Done provides clarity, especially in multi-functional teams. It avoids misunderstandings and disputes about work completeness.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why other options fall short:

B refers to a team formation stage but doesn’t address the root cause of conflict.

C and D help improve backlog clarity but don’t resolve issues around completion criteria.

Answer: A

══════════════════════════════════════════════════

Agile emphasizes sustainable pace and continuous improvement, not overworking or overcommitting. The appropriate response is to identify why the team overcommitted, learn from it, and adjust future sprint planning. This aligns with the PMI Agile Practice Guide (Section 5.4: Sprint Planning and Velocity) and Section 5.6: Retrospectives, which recommend using retrospectives to address such issues.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explains that over-committing leads to poor predictability, and inspecting root causes helps refine estimation and velocity in future sprints.

Option C is correct: it supports learning and improves future planning.

Option A promotes unsustainable practices.

Option B misunderstands velocity—it’s a measurement, not something to be increased by will.

Option D undermines team stability and agile planning based on consistent team capacity.

The primary reason for delivering a minimally viable product (MVP) is to reduce risk as quickly as possible. By releasing a version of the product with just the essential features, the team can quickly test assumptions, gather feedback from users, and make necessary adjustments before investing more time and resources. This approach allows the team to identify and address potential risks early in the process, ensuring that the product is on the right track and meets user needs before full-scale development continues.

To understand the needs of different user types, agile teams use personas and extreme characters to represent a range of users, including edge cases. According to the PMI Agile Practice Guide (Section 5.2: Requirements and Personas) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), personas help teams build empathy and ensure that stories reflect actual user roles—not just generic assumptions.

Option D is correct: personas and extreme characters ensure inclusive and realistic story coverage.

Option A and B focus on communication and sequencing but not user diversity.

Option C (process flows) is more technical and doesn’t solve the misalignment with user perspectives.

The correct answer is B – Have team members work in pairs to learn from each other and develop new skills. Pairing encourages collaboration, knowledge sharing, and skill development, which helps reduce dependency on specific individuals and enhances engagement through variety.

From the PMI Agile Practice Guide:

“Pair programming and other collaborative work methods help reduce repetition, promote learning, and improve motivation. These techniques allow for shared ownership and skill diversity.”

(PMI Agile Practice Guide, Section 4.3 – Continuous Learning and Team Development)

Mike Griffiths adds:

“Cross-training and pairing reduce boredom, eliminate knowledge silos, and increase team flexibility. They are effective responses to reduced motivation from repetitive work.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

A may temporarily help morale but doesn’t address the root cause.

C is more suitable for analyzing inefficiencies, not directly resolving monotony.

D adds cost and doesn’t solve the underlying engagement problem.

Answer: B

────────────────────────────────────

The correct answer is D – Ask the team to decide if the task should be reassigned. In agile, the Scrum Master serves as a servant leader and facilitator, not a manager. Task decisions are made by the team through collaboration and self-organization.

From the PMI Agile Practice Guide:

“Agile teams self-organize and make decisions collaboratively. The Scrum Master facilitates discussion and decision-making but does not dictate task assignments.”

(PMI Agile Practice Guide, Section 4.3 – Team Empowerment and Self-Organization)

Mike Griffiths adds:

“The Scrum Master’s role is to empower the team to find their own solutions and make informed decisions that support sprint goals. When adjustments are needed, the team should decide how to proceed.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A undermines self-management and may create fear or pressure.

B implies outside control instead of team autonomy.

C ignores opportunity for improvement and team input.

Answer: D

The storming phase (from Tuckman’s model: Forming–Storming–Norming–Performing) is marked by conflict and role negotiation. The agile coach or Scrum Master plays a critical role in guiding teams through this phase with structured facilitation and conflict-resolution techniques.

According to the PMI Agile Practice Guide (Section 4.3.2: Team Development Stages) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), the agile coach must provide support, guidance, and tools to help the team evolve toward self-organization and maturity.

Option B is correct: effective facilitation helps the team progress toward high performance.

Option A promotes dysfunction.

Option C risks escalating unresolved conflict.

Option D is overly individual-focused and not team-centric.

In Scrum, the product owner is the primary point of contact between stakeholders and the development team. According to the PMI Agile Practice Guide (Section 3.3: Roles and Responsibilities), the Scrum Master ensures that communications flow properly and protects the team from distractions.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes the importance of having a single point of contact for stakeholder feedback to avoid miscommunication and overload.

Option A is correct: redirecting communication through the product owner keeps the team focused and the backlog structured.

Option B is unprofessional and discourages stakeholder engagement.

Option C bypasses review and prioritization—backlog management should be intentional.

Option D could blur roles and bypass proper channels.

If a story is not completed, it is not counted toward the current sprint velocity. When carrying the story forward to the next sprint, teams should re-evaluate the story size, especially if part of the work is already done. According to the PMI Agile Practice Guide (Section 5.4: Velocity and Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile teams are encouraged to re-estimate such items based on remaining work.

Option D is correct: incomplete stories should be re-estimated based on new size or effort.

Option A violates velocity principles—only fully completed stories count.

Option B undermines the fixed-length timebox principle of sprints.

Option C is not directly relevant unless the story’s complexity necessitates research, which is not stated here.

The correct answer is C — Ask the team member to update daily progress on the information radiators.

In Agile, transparency and self-organization are key. Information radiators (e.g., task boards, digital dashboards) allow all team members and stakeholders to see the current state of work at any time. If a team member cannot attend stand-ups, they should still update their tasks on the board so that others are informed.

PMI Agile Practice Guide:

“Information radiators ensure transparent communication of progress, risks, and blockers to all team members and stakeholders. These should be updated in real-time or daily by those responsible.”

(PMI Agile Practice Guide, Section 5.6 – Information Radiators)

Mike Griffiths:

“Task boards and progress charts allow anyone to see project status without waiting for meetings. Team members must take responsibility for keeping them current.”

(PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A punishes the team for one member’s lack of participation and doesn’t solve the communication issue.

B reintroduces a command-and-control model, reducing team ownership.

D is dishonest and violates agile principles of transparency.

Answer: C

—

The scrum master should emphasize the core principles of agile, which are centered around collaboration, delivering value incrementally, and fostering a shared mindset among the team. In an agile environment, success is not only about following processes but about the team working together towards a common goal, adapting to change, and continuously delivering value to customers. These principles are the foundation of agile methodologies and essential for teams that are new to agile to understand.

The correct answer is D – Assume the team member ' s tasks to meet iteration goals and notify the Product Owner. Agile teams are self-organizing and accountable. High-performing teams take ownership of shared goals and redistribute work as needed to maintain commitment.

From the PMI Agile Practice Guide:

“High-performing agile teams collaborate to deliver sprint goals, adapting to changes such as unavailability of team members. They adjust workload and communicate impacts transparently.”

(PMI Agile Practice Guide, Section 4.3 – Team Performance and Self-Organization)

Mike Griffiths explains:

“When team composition changes, the team must redistribute work to ensure delivery. Ownership, trust, and flexibility are core traits of high-performing agile teams.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A signals dysfunction and abdicates team responsibility.

B implies external management of team staffing.

C violates the principle of self-organization.

The correct answer is D – Break non-functional requirements into those that can be delivered in the given sprint. Agile teams apply the principle of incremental and iterative delivery not only to functional requirements but also to non-functional ones. Large or complex work—including non-functional requirements—should be decomposed into smaller, manageable items.

From the PMI Agile Practice Guide:

“Work items, including non-functional requirements, should be split to fit within a sprint’s capacity. Teams use story-splitting techniques and prioritize parts that provide the most value or enable further development.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning and Story Sizing)

Mike Griffiths reinforces:

“If a user story or requirement is too large for a sprint, it should be broken down. Even performance and security requirements can often be delivered incrementally.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A ignores important non-functional quality attributes.

B is not in line with agile ' s sustainable pace and team stability.

C deflects ownership without attempting a solution.

Answer: D

────────────────────────────────────

The correct answer is D — Help establish the next sprint ' s goal.

The sprint goal provides a shared objective and guides the selection and execution of user stories. It is established collaboratively between the product owner and the development team at the start of sprint planning and precedes task decomposition or estimation.

PMI Agile Practice Guide:

“The team collaborates with the product owner during sprint planning to define a sprint goal. The sprint goal gives the team clarity and focus on what it intends to achieve during the sprint.”

(PMI Agile Practice Guide, Section 5.5 – Iteration Planning)

Mike Griffiths reinforces:

“Effective planning starts with understanding the desired outcome of the sprint. The sprint goal aligns the team and informs prioritization and task breakdown.”

(PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A prematurely assigns tasks, which goes against Agile’s collaborative ethos.

B and C happen later in the sprint planning process after defining the sprint goal.

Answer: D

—

The correct answer is C – Identify and monitor issues through a risk burndown chart.

Risk burndown charts track how risk exposure is increasing or decreasing over time. This agile artifact is used to communicate risk trends and drive conversations around risk mitigation. It’s especially useful when risks threaten iteration goals or release timelines.

From the PMI Agile Practice Guide:

“Risk burndown charts are visual tools that track remaining project risk. They help identify whether risks are increasing or decreasing and enable proactive management.”

(PMI Agile Practice Guide, Section 3.5 – Risk Management in Agile)

Mike Griffiths explains:

“Tracking risks visually, such as in a risk burndown chart, helps stakeholders understand exposure levels and fosters risk-mitigation behavior across the team.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 – Risk Management)

Why the other options fall short:

A delays action and does not help real-time monitoring.

B tracks tasks, not risk.

D (issue log) may help but lacks the proactive visual trend tracking provided by a burndown chart.

Answer: C

The correct answer is D – Brainstorm with the team to identify a solution.

Agile promotes collective ownership and team-based decision-making. When a critical issue such as architectural scalability arises, the team should be involved in brainstorming alternatives, weighing trade-offs, and deciding how best to move forward collaboratively.

From the PMI Agile Practice Guide:

“Agile encourages collaborative problem-solving and cross-functional ownership. Teams should collectively analyze challenges and determine the most appropriate course of action.”

(PMI Agile Practice Guide, Section 4.3 – Collaborative Decision-Making)

Mike Griffiths also affirms:

“When teams face significant technical or architectural risks, they should come together to explore options and make decisions based on consensus, feasibility, and value.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 – Problem Detection and Resolution)

Why the other options are inappropriate:

A is authoritarian and ignores team input.

B risks performance degradation without team consensus.

C may be part of the process, but only after the team has evaluated options.

Answer: D

═══════════

══════════════════════════════════════════════════

When considering an increase in scope, it ' s important to first align with the organization ' s higher-level objectives. Seeking executive approval on the approach ensures that the change is in line with organizational priorities and gets the necessary buy-in from key stakeholders. Additionally, determining the purpose and value proposition helps clarify the benefits of the new scope, ensuring the team focuses on delivering value that is clear and beneficial to the organization. These actions are critical before making any further decisions or changes.

The correct answer is D – Set up a meeting with the stakeholder to modify the working agreement and ensure future engagement.

Agile values regular collaboration with stakeholders. When a stakeholder becomes disengaged, the first step is to address it through open communication and mutual agreement. Revisiting or modifying the working agreement helps reset expectations and reestablish commitment in a collaborative and respectful way.

From the PMI Agile Practice Guide:

“Agile teams work closely with stakeholders and set expectations through working agreements that are revisited and refined as necessary. These agreements include communication preferences and participation expectations.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths reinforces this:

“Creating and maintaining stakeholder engagement requires ongoing alignment of goals and expectations. When participation drops, revisit agreements and reset expectations collaboratively.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Why the other options fall short:

A may help short-term but doesn’t address the root issue of misalignment or expectation gaps.

B comes across as directive rather than collaborative.

C escalates prematurely without attempting resolution directly with the stakeholder.

Answer: D

══════════════════════════════════════════════════

The correct answer is A – Conduct frequent demos and obtain feedback from users throughout the development of the next release. Agile is feedback-driven. Regular demonstrations (e.g., sprint reviews) help gather customer input to continuously enhance the product and optimize value.

From the PMI Agile Practice Guide:

“Frequent demonstrations and validation with stakeholders ensure that teams deliver value continuously and adapt the product based on real-time feedback.”

(PMI Agile Practice Guide, Section 5.2 – Feedback and Product Review)

Mike Griffiths notes:

“Customer feedback loops are vital to agile. Demos provide a mechanism for validating delivered functionality, identifying improvement opportunities, and maximizing product value.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B contradicts continuous delivery and customer collaboration.

C may help with scale, but doesn’t directly address value improvement.

D is more about process quality than business value.

Answer: A

────────────────────────────────────

The correct answer is A – Inform the stakeholder that all updates are provided in the sprint review sessions and encourage them to attend.

The Sprint Review is designed to provide transparency to stakeholders, demonstrate completed work, and gather feedback. Stakeholders should be encouraged to attend these events to stay updated and engaged.

From the PMI Agile Practice Guide:

“Sprint reviews are intended to engage stakeholders in reviewing completed work and discussing priorities. This event ensures transparency and encourages stakeholder collaboration.”

(PMI Agile Practice Guide, Section 5.5 – Stakeholder Engagement)

Mike Griffiths adds:

“Agile teams encourage stakeholder participation in regularly scheduled review meetings to maintain alignment and foster transparency.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Other options:

B adds non-Agile overhead and undermines Agile transparency mechanisms.

C and D are dismissive and uncollaborative, potentially damaging relationships.

Answer: A

══════════════════════════════════════════════════

The correct answer is C – The team realized that some stories were underestimated relative to other stories and reestimated as needed.

According to the data in the chart:

Backlog started at 500 points.

Points steadily decreased by 25 points per iteration for the first 3 iterations, reflecting normal velocity.

At the end of iteration 4, the backlog increased from 425 to 450 points (a 25-point jump), which indicates an increase in estimated remaining work.

In Agile, backlog point totals can increase when work is reestimated—typically because items were originally underestimated or new complexity is discovered. Reestimation reflects the evolving understanding of requirements and is a core principle of adaptive planning.

From the PMI Agile Practice Guide:

“Estimates may change as the team learns more. Agile teams inspect and adapt their understanding of the work during iteration planning and refinement. Story reestimation is normal and may result in backlog point increases.”

(PMI Agile Practice Guide, Section 5.3 – Adaptive Planning and Estimation)

Mike Griffiths writes:

“Backlogs are dynamic. Teams may reestimate stories during grooming or retrospectives if they find that original estimates were off. This helps maintain planning accuracy and backlog integrity.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Estimation and Backlog Refinement)

Incorrect options:

A refers to external factors not reflected in the backlog points.

B would be better handled by new backlog items, not inflating prior estimates.

D suggests increased scope/output, which would add stories but not necessarily reestimate existing ones.

Answer: C

────────────────────────────────────

The correct answer is D – Implement a spike to enhance creativity by experimenting with new techniques and process ideas in order to discover more efficient and effective ways of working.

A spike is a time-boxed research or prototyping activity used to explore uncertainty, investigate a technology, or gain deeper knowledge of an implementation. Spikes are especially useful when a team lacks familiarity with certain technologies, as they reduce risk and support better estimation.

From the PMI Agile Practice Guide:

“Spikes are a type of exploration that agile teams use when they are uncertain about a technology or technique. They are time-boxed research efforts aimed at reducing risk and improving future delivery.”

(PMI Agile Practice Guide, Section 5.3 – Spikes)

Mike Griffiths further explains:

“Spikes allow the team to gain knowledge needed to understand a technical or design problem. They are particularly useful when the team lacks domain or technical experience and are often used to improve estimation accuracy.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why other options fall short:

A and B manipulate iteration length without addressing the core problem (lack of technical knowledge).

C increases overhead without solving the learning gap or preventing the root cause (rework).

Answer: D

══════════════════

answers and comprehensive explanations drawn from authoritative sources including the PMI Agile Practice Guide, PMBOK® Guide, Mike Griffiths’ PMI-ACP Exam Prep Book, and Andy Crowe’s PMI-ACP Exam materials.

══════════════════════════════════════════════════

The correct answer is B – Manage communication between all team members and the customer to promote effective and transparent collaboration. Agile values open, direct, and frequent communication, particularly between team members and stakeholders. Transparency, collaboration, and shared understanding reduce misunderstandings and promote customer satisfaction.

From the PMI Agile Practice Guide:

“Agile values individuals and interactions over processes and tools. Frequent, open, and direct communication with stakeholders is essential. Agile teams are encouraged to engage stakeholders frequently to ensure alignment and transparency.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths emphasizes:

“Agile fosters transparency and trust through direct communication. Information should flow freely between all team members and stakeholders to facilitate quick feedback and mutual understanding.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 – Stakeholder Engagement)

Incorrect options:

A and C limit communication and transparency.

D is useful for conflict resolution, but not for broad issue management or stakeholder communication.

Answer: B

────────────────────────────────────

The correct answer is B – Create a team norms document to set participation guidelines. Establishing team norms improves psychological safety, trust, and collaborative behavior. It provides a structured way to handle differences of opinion and ensure equal contribution.

From the PMI Agile Practice Guide:

“Team norms or working agreements are guidelines created by the team to set expectations for behavior, participation, and communication. These norms are agreed upon early and revisited as needed to support healthy collaboration.”

(PMI Agile Practice Guide, Section 4.3 – Team Charter and Working Agreements)

Mike Griffiths elaborates:

“High-performing agile teams create shared agreements that clarify roles, expectations, and behavior. When team conflict or disconnects arise, practitioners should guide the team to revisit or develop such norms.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A lacks structure and may not address the root issue.

C delays resolution and misuses the stand-up’s purpose.

D waits too long to act; issues should be addressed immediately, not deferred.

Answer: B

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

The correct answer is B – Review possible options and make an informed decision to cut losses based on delivered business value. In agile, decisions are continuously evaluated based on value delivery, inspect-and-adapt principles, and business justification.

From the PMI Agile Practice Guide:

“Agile projects emphasize delivering the highest value features early and frequently. When new information emerges—such as the high risk of failure of a critical feature—the product owner must evaluate the cost-benefit, assess remaining value, and make a business-based decision.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery)

“The agile mindset embraces failure as a learning opportunity but also encourages continuous evaluation of whether a project should continue. It is better to stop a project early based on value delivery assessments than to continue wasteful efforts.”

(PMI Agile Practice Guide, Section 2.3 – Fail Fast to Learn Quickly)

Mike Griffiths’ PMI-ACP Exam Prep Book notes:

“Agile teams reassess business value frequently. If remaining features do not justify additional investment due to technical, market, or cost concerns, the product owner may decide to stop the project and preserve resources. This decision should always be informed by the value already delivered versus expected benefits.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Why the other options are incorrect:

A is a possible outcome, but prematurely terminating without analyzing value delivery is hasty.

C (bringing in experts) may increase costs and still not solve the fundamental issue of failing value.

D ignores the significance of the critical feature and assumes it can be deferred without impact—this may not be viable.

Answer: B

The team lead should work to resolve the conflict by negotiating with the project director. Since the lead developer cannot complete their work due to the request for a detailed testing plan, the team lead should seek to limit the scope of the documentation request. By negotiating for fewer details or a reduced scope of testing documentation, the team can continue their work on the iteration while still meeting the project director ' s needs. This approach balances the need to progress with development and address the request without causing significant delays.

The correct answer is D – Ask the team to estimate the amount of rework needed so that adjustments can be made to both the project and release plan.

Agile planning is adaptive and iterative. New information, including required rework, must be integrated into updated estimates and plans. Agile teams frequently replan based on the realities of work-in-progress.

From the PMI Agile Practice Guide:

══════════════════════════════════════════════════

Managing technical debt is crucial for the long-term health of the project. The most effective approach is to include technical debt tasks in every sprint, ensuring that the debt is addressed incrementally without disrupting the flow of new feature development. By treating technical debt as a priority alongside new features, the team can reduce the impact of technical debt over time, maintain product quality, and align with stakeholder expectations. Continuous review of the impact ensures that the team is making informed decisions and balancing both short-term delivery and long-term maintainability. This approach also allows the team to meet performance expectations and customer satisfaction more consistently.

The correct answer is C – Create an environment of continued learning by providing opportunities for team members to develop their skills as generalized specialists.

Agile encourages the concept of “T-shaped” team members—individuals who have deep expertise in one area and broad skills across multiple areas. Promoting cross-skilling and continued learning reduces risk, increases collaboration, and helps build a resilient, self-sustaining team.

From the PMI Agile Practice Guide:

“Teams should strive to become cross-functional and develop generalized specialists who can collaborate effectively across domains.”

(PMI Agile Practice Guide, Section 5.2 – Building High-Performing Teams)

Mike Griffiths notes:

“Agile promotes team learning. Encouraging members to grow as generalized specialists reduces reliance on single individuals and improves flexibility.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Other options:

A helps but is not sufficient on its own.

B is a solid practice but doesn ' t directly promote skills growth.

D goes against Agile values of team development and empowerment.

Answer: C

══════════════════════════════════════════════════

The correct answer is A — Capture risks and make them visible, and use a burndown chart to focus on reducing risks early in the project.

Technical uncertainty is a key area of risk in Agile projects. These risks should be clearly communicated, visualized, and prioritized early in the project to allow timely mitigation. Agile teams are empowered to make decisions and highlight blockers rather than delay work or seek hierarchical intervention.

PMI Agile Practice Guide states:

“Agile teams actively manage risk through transparency and continuous feedback. Risks should be made visible on information radiators and addressed early in the project to prevent impact on value delivery.”

(PMI Agile Practice Guide, Section 7.3 – Risk Management)

Mike Griffiths adds:

“Teams facing uncertainty must surface risks openly and early. Using charts such as risk burndown and dashboards helps keep focus on managing these risks iteratively.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

B contradicts the time-boxing principle of sprints.

C raises awareness but lacks proactive risk mitigation.

D introduces a command-and-control dynamic, which is not agile.

Answer: A

—

The correct answer is C – Use class of service. In Kanban, the Class of Service (CoS) model is a key technique for prioritization and flow management. It helps teams decide which work items should be expedited, delayed, or treated as standard. Using CoS enables teams to handle tasks based on urgency, business value, and risk.

From PMI Agile Practice Guide:

“Classes of service define the rules by which work is selected, prioritized, and delivered. They help make prioritization policies explicit and transparent to stakeholders and team members.”

(PMI Agile Practice Guide, Section 5.4 – Kanban and Flow-Based Approaches)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Class of service models—such as ‘Expedite’, ‘Fixed Delivery Date’, ‘Standard’, or ‘Intangible’—allow teams to prioritize tasks by business value, risk, and urgency. This is particularly useful in Kanban systems where items flow continuously.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery / Kanban Practices)

Option A (involving the product owner) is more applicable to Scrum teams; Kanban teams often have shared ownership of flow.

Option B (reviewing WIP limits) affects flow but doesn’t guide task prioritization.

Option D (measuring lead time) helps with process analysis but not immediate prioritization.

Answer: C

────────────────────────────────────────────

Pull communication is most effective for a distributed team working across multiple locations, especially when task-oriented communications and discussion boards are involved. With pull communication, team members can access information when needed, such as through shared documents, wikis, or discussion boards. This ensures that communication is effective and available asynchronously, allowing the team to collaborate and stay informed without needing to be online at the same time. This method is particularly useful when managing a geographically dispersed team.

The correct answer is D – Work with the team to ensure that acceptance criteria is being properly defined and understood.

Incomplete work that fails to meet stakeholder expectations often results from unclear or misunderstood acceptance criteria. Clarifying the definition of “done” and ensuring alignment between the Product Owner and development team can drastically reduce rework and defects.

From the PMI Agile Practice Guide:

“Clear and testable acceptance criteria help ensure shared understanding. Quality issues frequently stem from misaligned expectations or vague requirements.”

(PMI Agile Practice Guide, Section 5.2 – Definition of Done and Acceptance Criteria)

Mike Griffiths writes:

“Teams must understand what success looks like for each story. Poorly defined or misunderstood acceptance criteria are a major cause of defects and missed expectations.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 – Problem Detection and Resolution)

Other options explained:

A (spike) is used for research or uncertainty—not fixing misunderstood requirements.

B (burndown chart) helps track progress, not resolve defects.

C may help indirectly but doesn ' t address the core problem of unclear requirements.

Answer: D

══════════════════════════════════════════════════

When the team determines that the highest-priority item will take longer than expected in the current sprint, it is essential to engage the product owner. The product owner is responsible for maintaining the product backlog and defining the priority of work items. By scheduling a meeting with the product owner, the team can collaboratively reassess the priorities and make adjustments based on the evolving understanding of the work required.

The product owner can help determine if the current high-priority item should be moved to the next sprint or if other adjustments to the backlog are needed. This ensures that the team is always focused on delivering the most valuable work within the given sprint time frame. Engaging with the product owner fosters collaboration and ensures alignment between the team and stakeholders, maintaining flexibility and focus on delivering customer value.

When the team is facing difficulties in estimating the scope of work due to unclear or ambiguous requirements, the product owner should collaborate closely with the client to ensure that the requirements are clear and well-defined. By refining the product backlog with more detailed and clarified requirements, the product owner can help the team generate more accurate estimates and better understand the scope of work. This is a fundamental step in ensuring the team can properly plan and execute the project on time.

The correct answer is B – Prioritizing stories.

The MoSCoW method is a prioritization technique used in Agile to categorize requirements and backlog items based on their business value. It helps stakeholders and teams agree on what is essential to deliver versus what is desirable or optional.

MoSCoW stands for:

M – Must have

S – Should have

C – Could have

W – Won’t have (this time)

From the PMI Agile Practice Guide:

“The MoSCoW prioritization method helps stakeholders classify backlog items based on their criticality and desired delivery timing. This enables better alignment with business objectives.”

(PMI Agile Practice Guide, Section 5.2 – Prioritization)

Mike Griffiths explains:

“MoSCoW is a simple but effective method for clarifying which features are essential and which can be deferred. It enhances transparency during prioritization discussions.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Value-Driven Delivery)

Why the other options are incorrect:

A – Estimating story size involves techniques like planning poker or T-shirt sizing.

C – Product validation is done via demos, acceptance criteria, and stakeholder feedback.

D – Progress tracking uses tools like burndown charts or cumulative flow diagrams.

Answer: B

══════════════════════════════════════════════════

The correct answer is C – Determine who is best qualified to address the challenges. Agile teams are self-organizing and empowered to make technical decisions. When challenges arise, the team collaboratively identifies who is best suited to resolve issues, rather than relying on external direction or top-down task assignment.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing. When challenges or new work arises, the team decides how to proceed, including task allocation based on skills and availability.”

(PMI Agile Practice Guide, Section 4.3 – Self-Organization)

Mike Griffiths also notes:

“Team members decide how work is divided and who tackles what. When technical complexity is involved, those with relevant expertise are encouraged to step in, with support from the rest of the team.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A violates the principle of team autonomy.

B delays delivery rather than solving the problem.

D incorrectly places the Product Owner in a team management role.

Answer: C

The correct answer is D – Planning poker.

Planning poker is a consensus-based estimation technique commonly used in Agile projects. During this technique, team members discuss user stories, clarify details, and independently assign story points. The facilitator (often the Scrum Master) ensures balanced participation. This process encourages team collaboration and reduces estimation bias.

From the PMI Agile Practice Guide:

“Planning poker is a common estimation technique where team members discuss the story, then individually provide estimates using a card deck, reaching consensus over multiple rounds.”

(PMI Agile Practice Guide, Section 5.3 – Estimation Techniques)

Mike Griffiths adds:

“Planning poker is based on Wideband Delphi and allows teams to converge on estimates through discussion and consensus. It is particularly useful for relative estimation of story points.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why other options are incorrect:

A (Lessons learned) applies to retrospective activities, not estimation.

B (Wideband Delphi) is the foundation of planning poker but is more formal and anonymous.

C (Formal point counting) is not a standard Agile estimation technique.

Answer: D

══════════════════════════════════════════════════

In Agile, collaboration is important, but it should not disrupt the team’s ability to focus on sprint goals. The Scrum Master can address this situation by designating a single team member to represent the team in external meetings, which reduces the impact on the rest of the team’s working time. Additionally, establishing a capacity buffer helps ensure that the team has enough time for their tasks while accounting for the time needed for meetings. This solution maintains both collaboration and productivity without overwhelming the development team.

The agile facilitator should focus on keeping the daily coordination meeting (daily stand-up) focused and efficient. If the meeting is becoming unproductive or lengthy, the facilitator needs to actively manage the flow and intervene when team members deviate from the meeting ' s objective, which is to quickly discuss progress, identify blockers, and align on the work for the day. By doing this, the facilitator can help the team maintain the purpose and time-box of the meeting, which is generally 15 minutes.

The correct answer is B — Two-way communication.

Agile thrives on collaboration and transparency. In sprint planning, the product owner presents the business needs (via user stories), and the team responds with estimates and commitments. This mutual communication fosters alignment, shared understanding, and trust, which is characteristic of two-way communication.

PMI Agile Practice Guide:

“Agile projects rely on high levels of communication and collaboration, especially between the product owner and development team.”

(PMI Agile Practice Guide, Section 4.2 – Communications and Collaboration)

Mike Griffiths:

“Two-way communication allows feedback and clarification. Sprint planning is a prime example where the PO and team interact to shape and commit to sprint goals.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A refers to managing emotions, not communication style.

C is unrelated to agile practice.

D (reciprocal communication) is a less common term and not directly aligned with the scenario.

Answer: B

—

Agile promotes self-organizing teams, where leadership can emerge naturally. The PMI Agile Practice Guide (Section 4.3.2: Team Empowerment and Leadership) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance) both emphasize supporting team members who take on informal leadership roles, as this strengthens team capability and fosters growth.

Option A is correct: nurturing emerging leaders aligns with agile values of empowerment and self-organization.

Option B may suppress initiative.

Option C escalates unnecessarily.

Option D applies hierarchical control inconsistent with agile team dynamics.

According to the PMI Agile Practice Guide (Section 7.1 Communication) and PMBOK® Guide (6th Edition, Section 13.3 Manage Stakeholder Engagement), transparency with stakeholders is fundamental in agile environments. Delays or deviations from expected outcomes must be promptly communicated to affected stakeholders to adjust expectations and plans.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) emphasizes that one of the key values in agile is responding to change over following a plan, and that includes openly discussing risks and delays with impacted parties.

Thus, Option D is correct: the agile coach should proactively engage marketing stakeholders to inform them about the delay and support revised planning.

To assess process efficiency, agile teams use value stream mapping to identify waste, delays, and non-value-adding steps. According to the PMI Agile Practice Guide (Section 5.5 Process Analysis and Value Stream Mapping), value stream analysis helps determine how efficiently a process converts inputs into valuable outputs, making it ideal for supporting customer inquiries on operational performance.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Continuous Improvement) reinforces the value of using value stream mapping for both software development processes and operational workflows to increase transparency and drive improvements.

Option B is correct: reviewing the value stream provides a structured way to evaluate efficiency.

Option A and D are important for team improvement and performance but don’t focus on process activity efficiency.

Option C relates to value prioritization, not operational efficiency.

Since PO Integration (Item #3) currently lacks user stories and estimated story points, the project team needs to break it down into smaller user stories or tasks before moving forward. This will allow the team to:

Assess dependencies and integration requirements more effectively.

Prioritize and deliver in smaller, testable increments.

Improve estimation accuracy using techniques like planning poker.

Ensure alignment with agile principles of incremental and iterative delivery.

The correct answer is C – Work with product owners and turn product backlog items into potentially shippable product increments.

Agile is grounded in the principle of delivering value early and often. Agile teams deliver value by continuously converting high-priority product backlog items into working software or product increments. These increments are potentially shippable, meaning they meet the Definition of Done and could be released at any point if the business chooses. Collaboration with the product owner ensures that the most valuable features are prioritized and refined before development begins.

From PMI Agile Practice Guide:

“Agile teams focus on delivering small, valuable, and potentially shippable increments of working product on a regular basis. This allows for frequent feedback and ensures that teams are always working on the most valuable features.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Working software is the primary measure of progress in agile projects. Agile teams collaborate with product owners to break down backlog items into increments that can be developed, tested, and delivered within a single iteration.”

(Mike Griffiths, Chapter 3 – Value-Driven Delivery)

Option A contradicts agile principles, which emphasize cross-functional teams capable of analysis, development, and testing.

Option B is a supporting activity but does not directly increase value delivery.

Option D reflects traditional project management thinking and does not align with the iterative, adaptive nature of agile.

Answer: C

The Walking Skeleton approach involves developing a minimal, end-to-end working system with just enough functionality to demonstrate how the product works in its simplest form. This is often used in Agile to ensure the core structure of the product is in place, and it allows stakeholders to see how basic features are implemented and how the product will evolve. By highlighting this approach, the project manager can help the sponsor understand the essential features and the incremental development process, making it clear what will be developed and when, without overwhelming them with detailed planning at this stage.

The correct answer is D – Encourage the team member to use experimentation/spikes for continuous improvement and help the team understand why it is important. Agile encourages learning and experimentation through techniques like spikes (time-boxed research or exploration activities).

From the PMI Agile Practice Guide:

“Agile encourages teams to experiment and learn continuously. Time-boxed spikes can be used to investigate alternative designs, reduce uncertainty, and support informed decisions.”

(PMI Agile Practice Guide, Section 5.3 – Spikes and Uncertainty Reduction)

Mike Griffiths supports this:

“Spikes are short, time-limited investigations into a design or technical approach. They are a vital part of agile development for reducing risk, exploring alternatives, and enabling innovation.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

A and C discourage innovation and agility.

B defers action rather than enabling real-time learning.

Answer: D

────────────────────────────────────

The correct answer is A — Make sure the product owner is fully embedded into the project team so that they are readily available to make quick decisions.

One of the major benefits of agile is that decision-making is streamlined by having empowered roles, such as the product owner, closely embedded with the team. This reduces delays and improves the responsiveness and accuracy of decisions, especially for prioritization and clarification.

PMI Agile Practice Guide:

“Empowering the product owner and embedding them with the team ensures faster decision-making, increased feedback loops, and reduces delays.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths:

“Agile teams thrive when key decision-makers, especially the product owner, are available to provide clarification and approval on the spot.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

B is too broad and may slow decision-making further.

C adds overhead and delays.

D misplaces decision authority; the Scrum Master is not responsible for product decisions.

Answer: A

—

The correct answer is B – The duration of feedback cycles has increased.

In Agile, quick feedback is crucial to success. An increase in feedback cycle time indicates breakdowns in communication, delayed decision-making, or weak collaboration—all of which are signs that a distributed team may not be functioning effectively.

From the PMI Agile Practice Guide:

“Distributed teams require more intentional efforts to maintain communication and reduce feedback loops. Lag in feedback reduces responsiveness and impedes value delivery.”

(PMI Agile Practice Guide, Section 2.3 – Agile Team Communication)

Mike Griffiths highlights:

“One of the key risks in distributed teams is the degradation of feedback speed. Long feedback cycles result in slower adaptation and lost opportunities.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Other options:

A (more emails) is neutral—could be communication, not dysfunction.

C (increased velocity) is a positive sign.

D (rescheduling meetings) is an adjustment, not necessarily dysfunction.

Answer: B

══════

══════════════════════════════════════════════════

To identify the features that offer the maximum value, the product owner should focus on understanding the needs and priorities of the product ' s end users. By identifying the users and their key activities, the product owner can ensure that the features included in the roadmap directly address the most important user needs and deliver the highest value. This user-centric approach ensures that the product delivers tangible benefits to its intended audience and aligns with their requirements.

The correct answer is D – Provide a delivery range based on the team ' s estimated velocity.

In Agile, planning is iterative and inherently uncertain. Rather than committing to a fixed schedule, it is best practice to provide a forecasted delivery window based on the team’s actual measured velocity. This reflects the inspect-and-adapt mindset of Agile.

From the PMI Agile Practice Guide:

“Agile teams forecast delivery using velocity ranges derived from completed work. Ranges reflect uncertainty and promote realistic expectations with stakeholders.”

(PMI Agile Practice Guide, Section 5.4 – Adaptive Planning)

Mike Griffiths affirms:

“Planning with ranges rather than fixed commitments respects the uncertainty of estimates and the empirical nature of Agile delivery. Forecasts should be based on velocity trends and updated iteratively.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Adaptive Planning)

Why the other options are less suitable:

A suggests triangulating data but wrongly implies a precise commitment.

B is more of a work preparation activity, not a planning technique.

C (analogous estimation) is better suited for initial planning, not for an in-progress agile project with real velocity data.

Answer: D

══════════════════════════════════════════════════

The correct answer is A – Use an information radiator to help increase the transparency of work for key stakeholders.

Information radiators (such as Kanban boards, burndown charts, and story maps) make work status visible to the entire team and stakeholders in real-time, improving communication without additional meetings or reporting overhead.

From the PMI Agile Practice Guide:

“Agile teams use information radiators to promote transparency, show progress, and increase stakeholder engagement without adding administrative burden.”

(PMI Agile Practice Guide, Section 3.5 – Information Radiators)

Mike Griffiths confirms:

“Effective agile environments display work status where everyone can see it. Visual indicators allow stakeholders and team members to remain informed without direct queries.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 – Agile Monitoring and Control)

Other options explained:

B creates unnecessary manual effort.

C may disrupt team rhythm; daily stand-ups are sufficient in Scrum.

D encourages siloed behavior and contradicts collaboration.

Answer: A

══════════════════════════════════════════════════

The correct answer is B — Hold regular retrospectives and have team members commit to specific actions.

Regular retrospectives enable the team to continuously reflect and adapt their processes and product based on new challenges or insights. Commitment to specific action items ensures accountability and fosters a culture of learning and responsiveness.

PMI Agile Practice Guide:

“Teams should hold regular retrospectives to identify areas for improvement and define concrete actions. These actions are tracked and reviewed in subsequent iterations.”

(PMI Agile Practice Guide, Section 5.8 – Retrospectives)

Mike Griffiths:

“Continuous improvement is a core agile value. Retrospectives allow teams to evaluate their performance and commit to actionable improvements.”

(PMI-ACP Exam Prep, Chapter 7 – Continuous Improvement)

Incorrect options:

A is a waterfall mindset.

C lacks structured reflection and accountability.

D is a poor coding practice and anti-pattern.

Answer: B

—

The correct answer is D — Engaged key stakeholders periodically to collect requirements.

Agile is based on frequent stakeholder collaboration. Continuous engagement ensures evolving needs are captured and prevents misalignment. Waiting for planning meetings or demos is too late to catch missing input.

PMI Agile Practice Guide:

“Agile teams ensure stakeholder engagement is ongoing throughout the project. This helps validate requirements and prevent surprises during reviews.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths:

“Stakeholders should be consulted early and often. Relying on static requirements leads to gaps. Agile teams maintain constant feedback loops.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A is too early and one-time.

B may help but is reactive.

C is a predictive approach inconsistent with agile.

Answer: D

The correct answer is B – Discuss the value of the change for the project with the customer.

Agile encourages ongoing collaboration with the customer, even if changes occur late in development. The contractor should not immediately reject or escalate the request. Instead, the first step is to assess the value of the requested change, collaborate on its importance, and then determine the best path forward—whether through backlog reprioritization or contractual adjustment.

From the PMI Agile Practice Guide:

“Agile welcomes changes in requirements, even late in development. Collaborate with the customer to explore the value of the change and its impact on schedule, cost, and scope.”

(PMI Agile Practice Guide, Section 3.4 – Delivering Value Frequently)

Mike Griffiths emphasizes:

“Before resorting to contract changes or governance processes, teams should talk with the customer to understand the reason behind the change and its value.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Value-Driven Delivery)

Why the other options are suboptimal:

A assumes the change must go through legal channels without exploring its business value.

C may be necessary later but not as a first step.

D passively ignores the change and risks stakeholder dissatisfaction.

Answer: B

══════════════════════════════════════════════════

To ensure that the service will benefit the customer and meet their requirements, the product owner should build a prototype. Prototypes allow the team to create an early, low-fidelity version of the product that can be used to gather direct feedback from the targeted customer segment. This helps to validate whether the service aligns with the customer ' s needs and expectations before investing heavily in full development.

In agile, especially under conditions of uncertainty or anticipated changes, teams should focus on collaborative product development, including ongoing backlog refinement and continuous product reviews. This approach is endorsed by the PMI Agile Practice Guide (Section 5.1 Product Backlog and Refinement) and Section 7.2 (Engaging Stakeholders), which emphasize frequent interaction with the product owner and iterative feedback loops to adapt quickly.

Mike Griffiths in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) supports the practice of refining the backlog regularly and conducting frequent reviews to stay aligned with stakeholder expectations.

Option B is correct: continuous collaboration with the product owner supports flexible, value-driven delivery.

Option A is only a partial measure.

Option C promotes a waterfall mindset.

Option D ignores the nature of changing requirements.

The correct answer is B — Communicate the issue to the team in the next stand-up meeting.

Agile emphasizes early detection and resolution of impediments through daily communication. The Daily Stand-up is the appropriate forum to raise issues, so the entire team is aware and can decide collaboratively how to proceed.

From the PMI Agile Practice Guide:

“Daily stand-ups allow team members to communicate problems and identify impediments early. The team collaboratively determines how to respond to issues raised.”

(PMI Agile Practice Guide, Section 5.4 — Stand-up Meetings)

Mike Griffiths adds:

“Issues must be shared early and openly. The stand-up is designed to expose blockers and ensure collective team awareness and decision-making.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Option A skips collaboration and bypasses the team’s self-organizing nature. Options C and D delay the communication until the retrospective, which would result in lost time and potentially compound the issue.

Answer: B

—

The Scrum Master should remind the team that in Agile, the entire team is responsible for delivering the sprint goal, and it is important to take into account the different skill levels of team members when setting goals. This approach promotes a collaborative and supportive environment where experienced members can mentor less experienced ones, helping to improve the team ' s overall performance. It also encourages more realistic and achievable sprint goals, fostering empathy and understanding within the team. By acknowledging competency differences, the team can better allocate work and support each other to meet their goals.

The best answer is D because the project lead should foster psychological safety. In agile teams, people need to feel safe to share opinions, challenge ideas, raise concerns, and provide feedback without fear of blame, embarrassment, or punishment. This is especially important in international or cross-cultural teams where communication styles may differ.

Option A may help with meeting structure, but emphasizing rules does not necessarily make people feel safe. Option B is passive and may allow silence to continue. Option C may help in some cases, but separate meetings do not solve the root issue in team discussions. Option D directly addresses the problem by improving the team environment.

PMI-ACP explicitly includes fostering psychological safety, encouraging dialogue, soliciting constructive feedback, and promoting a collaborative team environment.

=========

This situation introduces technical uncertainty. In agile, such scenarios are best addressed by spikes or incremental implementation and early feedback. The PMI Agile Practice Guide (Section 5.2 Spikes and Experimentation) suggests that uncertain work should be prototyped, tested early, and shown during sprint reviews for feedback and learning.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution) recommends testing high-risk integrations early and iteratively, rather than over-planning.

Option D is correct: developing, testing, and demonstrating early minimizes risk and aligns with agile principles.

Option A leans toward waterfall-style planning and over-documentation.

Option B incorrectly assumes non-functional requirements are less valuable—they’re critical in many systems.

Option C may delay necessary architectural work and increase risk.

The correct answer is B – Ensure there is a balanced mix of people who are experts and members with broad experience based on the work to be performed and determine training needs.

Scrum encourages cross-functional, self-organizing teams with complementary skills. Building a balanced team that reflects both depth and breadth of experience ensures optimal delivery while enabling team learning.

From PMI Agile Practice Guide:

“Agile teams are cross-functional. The team may need T-shaped skills—members with deep expertise in one area and a willingness to broaden knowledge in other areas. Creating balanced teams with knowledge diversity leads to better collaboration and learning.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths adds:

“Team selection should prioritize diversity of skill sets and the ability to collaborate, not just performance history. The goal is a team that can deliver value collectively, not as individuals.”

(Mike Griffiths, Chapter 4 – Team Performance)

Why the other options are not suitable:

A may reduce team diversity and discourage healthy conflict resolution.

C may not be feasible in distributed environments and is not a strict requirement.

D focuses on individual velocity contributions, which contradicts Agile’s team-based delivery focus.

Answer: B

The first step for a new Scrum Master is to gain context and alignment. According to the PMI Agile Practice Guide (Section 2.3: Agile Mindset), agile leaders must understand the product vision and goals to provide proper support to the team and align delivery efforts with organizational objectives.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 2: Agile Principles and Mindset) emphasizes that new leaders should start by understanding stakeholder expectations, enterprise context, and business drivers before making operational decisions like backlog setup or sprint planning.

Option B is correct: understanding the project vision provides critical context.

Option A is premature without first understanding the broader organizational objectives.

Option C (sprint 0) can be useful but should follow alignment on vision and context.

Option D skips necessary discovery and planning.

The correct answer is C — All stakeholders are responsible for identifying risks during standups, retrospectives, and other team meetings.

Agile promotes collective ownership. Risk identification and mitigation are shared responsibilities involving the entire team, including the product owner, developers, and other stakeholders. Agile meetings (e.g., stand-ups, retrospectives) are excellent forums for surfacing risks early.

PMI Agile Practice Guide:

“In agile projects, everyone is responsible for identifying and managing risk. Teams inspect frequently, enabling early detection and resolution of issues.”

(PMI Agile Practice Guide, Section 7.3 – Risk Management)

Mike Griffiths:

“Risk management is embedded in agile events. Teams don’t defer risk analysis to a specialist—they collaborate continuously to identify, discuss, and respond to risks.”

(PMI-ACP Exam Prep, Chapter 6 – Problem Detection and Resolution)

Incorrect options:

A ignores active risk management needs.

B assumes individual rather than shared responsibility.

D misrepresents the PO’s role—risks may appear in the backlog, but management is team-based.

Answer: C

—

The project lead should focus on creating a safe environment where all team members feel comfortable expressing their opinions without fear of judgment or repercussions. This can be achieved by encouraging open communication, showing appreciation for diverse perspectives, and actively ensuring that everyone ' s voice is heard. A safe environment fosters trust and collaboration, which is essential for the team ' s success. While other options may help in certain contexts, building a culture of safety and trust is the most effective long-term strategy to encourage team members to speak up.

The correct answer is C – Meet with the team to discuss the issue and identify specific actions to reduce or eliminate the issue. Agile coaches facilitate team self-management, guide reflection, and encourage the team to solve performance issues collaboratively. Open discussion fosters ownership and accountability.

From the PMI Agile Practice Guide:

“Agile coaches guide teams through self-reflection and help them identify root causes of issues. Coaches support team-driven resolutions to behavioral and performance problems.”

(PMI Agile Practice Guide, Section 4.3 – Agile Coaching and Team Performance)

Mike Griffiths adds:

“Effective agile leadership involves enabling the team to identify and resolve their own challenges. Top-down directives may harm morale and self-organization.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance and Coaching)

Incorrect options:

A and B bring in external control, undermining team autonomy.

D is punitive and contradicts agile principles of empowerment and trust.

Answer: C

The best answer is A because an agile practitioner should first facilitate collaboration, uncover the root causes of disagreement, and help the teams align around a shared outcome. The issue is not simply the absence of targets or KPIs; it is a cross-functional conflict involving cost, compliance, product choices, and sustainability commitments. PMI-ACP topics emphasize collaboration, stakeholder engagement, shared vision, systems thinking, and conflict facilitation.

Option B is too directive and may increase resistance because it forces compliance without resolving the underlying concerns. Option C centralizes the decision with executives, which reduces team collaboration and does not reflect agile servant leadership. Option D may be useful later, but KPIs alone will not resolve the tension or rebuild alignment. The agile practitioner should promote a collaborative approach to solving conflict and ensure common understanding of purpose and vision.

=========

When a feature is too large to fit into a sprint, agile recommends decomposing it into smaller user stories or increments. According to the PMI Agile Practice Guide (Section 5.2: User Stories and MVPs) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), teams should break down epics or large stories into Minimum Viable Product (MVP) segments and deliver value incrementally.

Option A is correct: this enables the team to deliver value sooner and iteratively build on it.

Option B delays addressing customer concerns.

Option C sacrifices overall product balance.

Option D violates time-boxing principles in Scrum and agile.

If the team members are already communicating regularly with each other and the customer, the daily coordination meetings may not be necessary. The project manager should adapt to the team ' s needs by reducing the frequency of these meetings, allowing the team to focus more on delivering work. This approach supports Agile principles of minimizing waste and encouraging efficient communication, ensuring that meetings are only held when they add clear value. The team can use alternative methods (e.g., a digital board or asynchronous communication) to stay aligned.

The Minimum Viable Product (MVP) is the smallest set of features needed to satisfy early adopters and deliver value quickly while enabling further development based on feedback. From the conversation:

Android phone integration: The customer specifically asks if they can connect their phone to the calendar app, so integrating with Android is a key MVP feature.

Scheduler to add events: The customer requests the ability to schedule and manage upcoming releases, including quarterly metrics deadlines and other key dates. This is fundamental functionality for the calendar app.

Product increment release dates: The customer wants the calendar to show release dates, so having the ability to display product increment release dates is essential.

The correct answer is C — During the retrospective, discuss the issue and create an action plan to avoid it in the future.

When teams misestimate or experience incomplete work, it’s important to reflect during the retrospective and create action items. This is a fundamental aspect of agile: continuous inspection, adaptation, and team-driven improvement.

PMI Agile Practice Guide:

“Retrospectives help identify opportunities for improvement. The team reviews its estimation accuracy and adjusts processes or practices based on patterns observed.”

(PMI Agile Practice Guide, Section 5.8 — Retrospectives)

Mike Griffiths elaborates:

“Estimating complexity is an area for ongoing learning. Teams use retrospectives to improve their sizing, identify knowledge gaps, and refine their planning techniques.”

(PMI-ACP Exam Prep, Chapter 5 — Adaptive Planning)

Other options:

A unnecessarily involves a project manager (non-agile).

B assumes one-size-fits-all rules, which limits team agility.

D ignores the structured opportunity the retrospective provides for team learning.

Answer: C

—

When the team is uncertain about a technical solution, a spike—a timeboxed research task—is used to explore possible approaches. The PMI Agile Practice Guide (Section 5.2: Spikes) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) recommend spikes as a formal way to explore unknowns and reduce risk in the backlog.

Option B is correct: spikes provide structure for resolving uncertainty.

Option A ignores the technical risk.

Option C disrupts team structure and ownership.

Option D defers the problem without seeking resolution.

The correct answer is A – Use the DISC framework with each team member.

The DISC model (Dominance, Influence, Steadiness, and Conscientiousness) is a well-established behavioral assessment tool used to understand communication preferences, motivators, and individual work styles. Agile leaders may use tools like DISC to foster emotional intelligence, improve collaboration, and re-engage disengaged team members.

From the PMI Agile Practice Guide:

“Effective agile leaders understand individual team members ' communication styles and motivations. Tools such as DISC or MBTI can help assess personality preferences and enable better coaching.”

(PMI Agile Practice Guide, Section 6.2 – Coaching Agile Teams)

Mike Griffiths notes:

“Behavioral models such as DISC support the development of emotionally intelligent teams. They help leaders tailor their coaching and communication approaches to individual needs.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why other options are incorrect:

B (MoSCoW) is a prioritization technique, not a tool for personal engagement.

C (Hiring a SAFe coach) is overkill and not the most direct or relevant response.

D (BDUF – Big Design Up Front) is a traditional approach unrelated to team dynamics or motivation.

Answer: A

The correct answer is C — Training in areas of weakness.

Velocity can be improved when the team removes skill-based bottlenecks. If some members struggle due to lack of knowledge or technical gaps, their productivity—and the team ' s velocity—will be impacted. Targeted training helps the team overcome these weaknesses and deliver more efficiently.

PMI Agile Practice Guide:

“Improving technical and team skills through training and mentoring increases team performance and agility. Learning is a continuous improvement activity that directly impacts delivery capacity.”

(PMI Agile Practice Guide, Section 6.4 – Developing People and Teams)

Mike Griffiths adds:

“Velocity is driven by team capabilities. When teams address their weakest areas—through training, pairing, or knowledge sharing—they improve quality and throughput.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Other options:

A supports communication but doesn’t directly impact skill-based bottlenecks.

B helps with planning but not necessarily performance.

D describes the work cadence, not a practice that enhances velocity.

Answer: C

—

The correct answer is D – Facilitate a just-in-time exploration of the functionality by the customer and the team.

Agile promotes emergent planning and just-in-time elaboration. When a customer cannot clearly define how a feature should function, collaborative exploration at the point of need (just-in-time) ensures shared understanding, timely feedback, and minimized waste.

From the PMI Agile Practice Guide:

“User stories are deliberately kept light to encourage conversation. These conversations often occur just before the story is scheduled for development—known as just-in-time elaboration.”

(PMI Agile Practice Guide, Section 5.2 – Backlog Preparation and Refinement)

Andy Crowe also explains:

“Agile teams defer detail until the last responsible moment. This supports flexibility and better understanding through collaboration. Facilitating exploration sessions when needed helps clarify expectations and reduce uncertainty.”

(Andy Crowe, PMI-ACP Exam Prep, Chapter 5 – Value Delivery)

Why other options are less suitable:

A may be helpful for technical uncertainty, but the issue here is lack of functional clarity from the customer.

B (iteration 0) is more of a preparatory stage; it is not typically used mid-project.

C suggests decomposition but without resolving the lack of understanding; it assumes the problem is granularity, not clarity.

Hence, the correct agile action is to engage collaboratively at the point of need: D

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

When the organization transitions from longer to shorter iterations, it’s crucial to provide the team with the right support and ensure they have the resources to adapt. Requesting support from the enterprise coach and HR can help the team manage this change effectively, providing them with necessary training or assistance. Additionally, assessing the impact of the change and brainstorming solutions with the team helps address concerns about testing and ceremonies, while allowing the team to provide input on how they can adapt to the new iteration length without compromising quality or efficiency.

The Scrum Master should facilitate a conversation between the team and the senior manager to understand the purpose and expectations behind the request for real-time updates to the burndown chart. By aligning on the reporting requirements and discussing potential impacts on team productivity, the Scrum Master can ensure that the metrics are meaningful and do not interfere with the team ' s ability to deliver value. It ' s important to find a balance between transparency and efficiency, ensuring that the team’s workflow isn’t disrupted by unnecessary administrative tasks.