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

Servant leadership is about supporting the team, empowering them, and ensuring they have what they need to succeed. The team leader should focus on removing impediments that block the team ' s progress. By doing so, the leader enables the team to work more efficiently and effectively, without being obstructed by recurring issues. This aligns with the servant leadership mindset of putting the team ' s needs first and helping them reach their goals.

In Kanban, lead time is a key performance indicator (KPI) that should be regularly monitored. Lead time measures the amount of time it takes for a work item to move from the start of the process to its completion. By monitoring lead time, the team lead can assess how efficiently work is flowing through the system and identify areas where bottlenecks or delays may be occurring. Reducing lead time is one of the primary goals in Kanban to improve overall process efficiency and delivery speed.

The correct answer is A – Lead time, throughput, and due date performance. These are key flow-based metrics used in Kanban systems to monitor performance, efficiency, and predictability of delivery.

From the PMI Agile Practice Guide:

“Kanban systems rely heavily on flow metrics to measure performance and identify bottlenecks. Key Kanban metrics include lead time, throughput, and cycle time. These metrics provide insights into how quickly work is flowing through the system.”

(PMI Agile Practice Guide, Section 5.5 – Kanban System Metrics)

Mike Griffiths further explains:

“Kanban teams track cumulative flow, lead time, and throughput to ensure steady and predictable delivery. Due date performance is used to evaluate commitments and reliability.”

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

Incorrect options:

B refers to tools and principles, not performance metrics.

C includes practices not specific to Kanban metrics.

D includes some Scrum metrics, such as burndown, but not Kanban-centric ones.

Answer: A

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

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 C – Encourage all feedback then work with the customer to prioritize work for future sprints. Agile welcomes continuous feedback and values customer collaboration. All feedback should be collected and considered, but the product backlog is reprioritized to align with capacity and business goals.

From the PMI Agile Practice Guide:

“Agile promotes constant feedback to refine product direction. Feedback is incorporated into the backlog, prioritized based on value, and delivered incrementally according to capacity.”

(PMI Agile Practice Guide, Section 3.4 – Value-Driven Delivery and Continuous Customer Collaboration)

Mike Griffiths adds:

“Stakeholder feedback is essential in agile. Not all feedback can be implemented immediately, but it should be welcomed, evaluated, and prioritized transparently in collaboration with the product owner and stakeholders.”

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

Incorrect options:

A implies a heavy process not aligned with agile.

B prematurely limits feedback before collaborative prioritization.

D ignores the product owner’s prioritization role.

Answer: C

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

The correct answer is B – Invite the team to evaluate the suggestion and measure the effectiveness of the implementation.

In Agile, continuous improvement is a shared responsibility, and retrospectives are meant to be collaborative sessions where all team members—regardless of experience—can contribute. Ideas that could enhance performance should be discussed by the team as a whole and, when deemed valuable, tested and evaluated in upcoming sprints.

From the PMI Agile Practice Guide:

“The team owns the process and should inspect and adapt at regular intervals. During retrospectives, the team identifies potential improvements and experiments with them in subsequent iterations.”

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

Mike Griffiths states:

“Retrospectives empower teams to improve. All suggestions, regardless of origin, should be treated with respect. Teams test ideas and inspect outcomes to improve incrementally.”

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

Why other options fall short:

A delays action and discourages innovation.

C makes the product owner responsible for a team process decision, which is outside their role.

D promotes hierarchy, which undermines team collaboration and Agile values.

Answer: B

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

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 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

══════

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

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 A — Practicing the servant leadership style of working with an agile team.

Servant leadership is foundational to Agile. The agile project leader serves the team by removing impediments, supporting their needs, and promoting transparency. Using information radiators and being involved in team progress reflects servant leadership in action.

PMI Agile Practice Guide:

“Agile leaders act as servant leaders. They support the team, remove obstacles, and foster a transparent, collaborative environment.”

(PMI Agile Practice Guide, Section 6.2 – Coaching and Servant Leadership)

Mike Griffiths:

“Servant leadership is about enabling the team to succeed. Agile leaders serve by ensuring the team has what it needs, while maintaining visibility through information radiators.”

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

Incorrect options:

B and C are valid Agile behaviors but not the most specific or complete match.

D references feedback loops but not leadership style.

Answer: A

—

The correct answer is C – Passive-aggressive. When a team delivers work but avoids open discussion or interaction, especially in meetings, it may indicate passive-aggressive behavior. This behavior might reflect unresolved tension, lack of engagement, or unwillingness to collaborate transparently.

From the PMI Agile Practice Guide:

“High-performing agile teams thrive on open communication and collaboration. Passive-aggressive behavior, where communication is avoided despite task completion, can hinder trust and team health.”

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

Mike Griffiths warns:

“Silence or avoidance in agile teams may signal underlying issues. While work might be completed, lack of transparency and communication should be addressed early to maintain team cohesion.”

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

Incorrect options:

A refers to real-time communication and is unrelated to emotional dynamics.

B is contradicted by the lack of vocal interaction.

D implies disorder or lack of structure, which is not evident here.

Answer: C

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

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

—

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 C – Ask the team to discontinue developing the component. Agile empowers the product owner to make real-time scope decisions based on changing customer needs. If a feature no longer delivers value, continuing it violates agile ' s principle of maximizing value and minimizing waste—even if partially complete.

From the PMI Agile Practice Guide:

“Agile welcomes changing requirements—even late in development. The product owner’s role is to ensure that the team focuses on work that delivers the most business value.”

(PMI Agile Practice Guide, Section 3.4 – Value Prioritization and Scope Management)

Mike Griffiths affirms:

“If a component is deemed unnecessary, even mid-development, the product owner has the authority to reprioritize the backlog and halt the work. Agile values responding to change over following a fixed plan.”

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

Incorrect options:

A suggests unnecessary bureaucracy; agile favors decentralized, empowered decision-making.

B ignores the updated feedback and would create waste.

D is redundant since the sponsor already communicated disinterest; the product owner can act.

Answer: C

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

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

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

Task boards (or visual boards) are a great way to facilitate communication within the team. By using a task board, team members can easily see what work has been completed, what is currently being worked on, and what still needs attention. This visual aid helps keep everyone on the same page, ensures that information is shared transparently, and can help identify potential bottlenecks or communication gaps. It improves collaboration and visibility, making it easier for the team to coordinate and align on tasks, leading to fewer delays in the development process.

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.

The correct answer is B – Break the story up and focus on the most valuable parts. Agile promotes progressive elaboration, and large or complex stories (epics) should be broken down into smaller, testable user stories. This practice enables clarity, faster feedback, and more accurate planning.

From the PMI Agile Practice Guide:

“Large stories (epics) should be split into smaller user stories to enable understanding, estimation, and incremental delivery. Stories should be small enough to be completed within an iteration.”

(PMI Agile Practice Guide, Section 5.3 – User Stories and Story Splitting)

Mike Griffiths states:

“When a user story is too large or unclear, the team should break it down into smaller pieces, focusing on the most valuable parts first. Story splitting is a key agile practice.”

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

Incorrect options:

A discourages collaboration and learning.

C delays the resolution unnecessarily.

D avoids solving the actual problem and abandons valuable work.

Answer: B

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

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.

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.

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

══════════

In an agile environment, the product backlog should be continuously refined based on input from all relevant stakeholders, including the customer, business, and team members. It ' s essential for the whole team to collaborate when discussing and prioritizing the backlog to ensure that stakeholder needs and feedback are incorporated throughout the process. The backlog should reflect the team ' s understanding of what is most valuable to the stakeholders and the product, allowing the team to focus on delivering the highest priority features that align with the stakeholders ' goals.

Security features are typically considered non-functional requirements (NFRs), which should be captured in the product backlog and prioritized accordingly. As per the PMI Agile Practice Guide (Section 5.1: Product Backlog) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), any requested functionality—whether business- or system-level—must be clearly defined as a backlog item so the team can plan for it.

Option A is correct: security requirements should be added to the backlog and prioritized like other features.

Option B may come later if implementation is unclear, but first, the work must be defined and logged.

Option C and D represent clarification steps but don’t directly support implementation as backlog management does.

To create a high-performing team, the project manager should foster an environment where the team is aligned on a shared vision and empowered to make decisions collaboratively. Promoting consensus-driven decision-making helps team members feel involved and respected, and a shared vision ensures that everyone is working towards the same goal. This approach encourages teamwork, open communication, and collective ownership of the project’s success, which is crucial for a high-performing team.

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

Before the workshop, the team members should read and identify relevant user stories from the product backlog that directly contribute to the goal of developing the feature for receiving and resolving customer complaints. This ensures that the stories being worked on are well-understood and aligned with the release goal.

The team should also consider the possible risks associated with each selected user story, such as technical challenges or dependencies. Additionally, they should evaluate the value each story adds to the final user (customer), ensuring that the team focuses on delivering maximum value in the release.

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 " ).

Velocity is a tool for internal team improvement and forecasting, not external benchmarking. According to the PMI Agile Practice Guide (Section 5.4: Velocity and Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), tracking velocity over time helps teams assess the impact of process changes, refine estimates, and validate their continuous improvement efforts.

Option C is correct: it focuses on team-level improvement.

Option A uses velocity inappropriately for performance review, which goes against agile principles.

Option B promotes unhealthy comparisons across teams.

Option D is partially true, but stakeholder communication is secondary to internal use.

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

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 correct answer is C – Conduct retrospectives at the end of every sprint.

According to the Agile framework, regular retrospectives are a key practice to inspect and adapt the process. If team members have concerns about the Scrum Master ' s processes, the appropriate time and space to bring up and resolve such issues is the Sprint Retrospective.

From the PMI Agile Practice Guide:

“Retrospectives are a time-boxed event that enables the team to inspect itself and create a plan for improvements to be enacted during the next iteration. It provides a structured opportunity for feedback and reflection.”

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

Mike Griffiths further adds:

“Teams must take ownership of their process. The role of the agile leader, such as a Scrum Master, is to facilitate improvement via mechanisms like retrospectives. They are not responsible for enforcing process, but for enabling continuous improvement.”

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

Why the other options are incorrect:

A may undermine the team ' s self-organization and brings hierarchy into team-level process adjustments.

B may address some confusion, but doesn’t actively involve the team in process improvement.

D is inappropriate—sprint planning is for work planning, not process feedback.

Therefore, the most agile-appropriate and validated solution is: C

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

The agile lead should evaluate the team ' s capacity and help them select user stories that align with around 80% of their available capacity for the iteration. This approach takes into account potential issues or interruptions and helps ensure the team is not overcommitting. By selecting user stories based on a realistic understanding of the team’s capacity, the team is more likely to meet their commitments and avoid incomplete work. This method promotes sustainable work practices and helps the team maintain a predictable velocity over time.

The correct answer is C – Request that the Product Owner include a spike in the next iteration ' s backlog so they can perform an initial investigation.

A spike is a time-boxed activity that allows teams to research or experiment to gain knowledge about technical or functional aspects of an upcoming feature or integration. Since the team lacks experience with the new component, using a spike will allow them to explore and reduce uncertainty before actual development begins.

From the PMI Agile Practice Guide:

“Spikes are research activities that help teams gain the knowledge needed to reduce uncertainty and risk in upcoming stories.”

(PMI Agile Practice Guide, Section 5.3 – Backlog Refinement)

Mike Griffiths writes:

“Spikes are used when the team is not confident about how to implement a story due to technical or domain uncertainty. Spikes help mitigate risk and inform estimation.”

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

Other options are suboptimal:

A involves team extension, which contradicts Agile ' s preference for stable, cross-functional teams.

B is misaligned—technical investigation is a team responsibility, not the Product Owner ' s.

D avoids learning and may compromise solution quality.

Answer: C

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

The correct answer is A – High-risk features can be prioritized to fit into releases with less work in progress. Agile emphasizes risk-driven delivery: high-risk and high-value features should be addressed early to reduce uncertainty. Managing WIP also helps improve focus and throughput.

From PMI Agile Practice Guide:

“Agile teams often deliver the highest risk or highest value items early in the project. This helps reduce uncertainty and allows for faster feedback and adaptation.”

(PMI Agile Practice Guide, Section 3.4 – Value Delivery and Risk)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Prioritizing high-risk features early is a proactive risk management strategy. Teams can reduce the likelihood of failure by discovering major issues early and correcting them while time and budget allow.”

(Mike Griffiths, Chapter 5 – Adaptive Planning)

Option B delays addressing risk.

Option C focuses on low-value items and may not satisfy customer concerns.

Option D adjusts WIP but doesn’t directly address prioritizing the risky features.

Answer: A

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

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

=========

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 B — The stakeholder who can prevent the project from achieving its goals.

Stakeholder prioritization is based on power and influence. Those who can significantly impact or block project success (positively or negatively) should be prioritized. This ensures their concerns are addressed and their support is cultivated early.

PMI Agile Practice Guide:

“Stakeholder engagement is critical in agile. The team must identify those who have the most influence over project outcomes and ensure early and frequent communication.”

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

PMBOK® Guide:

“Stakeholder prioritization involves assessing who has the greatest influence on project success.”

—

When issues recur across multiple iterations, it’s a strong indication that the root cause has not been addressed. The PMI Agile Practice Guide (Section 5.6 Retrospectives) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) recommend performing root cause analysis techniques (e.g., 5 Whys, Fishbone diagram) to ensure that the true source of recurring problems is uncovered and resolved.

Option B is correct: identifying root causes is essential to sustainable improvements.

Option A may help but doesn’t address the underlying team-level process.

Option C is useful after a solution is implemented but not the priority when the cause is unknown.

Option D is helpful for tracking, but again, ineffective if the root cause is unidentified.

The correct answer is A – Continue working on the task until it is completed. Agile teams commit to the sprint goal and are expected to deliver what they’ve planned to the best of their ability. If a task takes longer than estimated, the team inspects and adapts but generally tries to complete the committed work within the current sprint.

From the PMI Agile Practice Guide:

“Agile teams are committed to delivering the work they planned for the iteration. If estimates are off, the team inspects the impact and continues, learning from it for future planning.”

(PMI Agile Practice Guide, Section 5.3 – Iteration Planning and Commitment)

Mike Griffiths explains:

“If something takes longer than expected, the team should strive to complete it and use the experience to improve future estimation. Agile teams maintain sprint commitment integrity.”

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

Incorrect options:

B is punitive and unaligned with Agile values.

C contradicts Agile’s emphasis on stable teams and sustainable pace.

D breaks commitment and risks value delivery.

Answer: A

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

Value stream mapping is a powerful tool in Agile and Lean methodologies used to visualize and analyze the flow of materials and information across the entire process. By mapping the current state, the team can identify bottlenecks, delays, and inefficiencies, especially when multiple teams are involved in sequential activities. Once these gaps and constraints are identified, the team can work on improving the process, such as by finding ways to increase the number of systems migrated per day from two to three, thus improving overall efficiency.

Frequent feedback is key to agile success. According to the PMI Agile Practice Guide (Section 5.3: Sprint Review and Feedback) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement), the sprint review (demo) is the primary event designed to obtain feedback from stakeholders. If stakeholders are unresponsive, increasing the opportunities for engagement, such as by scheduling more demos or review checkpoints, encourages their involvement.

Option D is correct: demos provide structured opportunities to collect feedback.

Option A might increase delivery cadence but doesn ' t guarantee feedback.

Option B is inappropriate—daily stand-ups are for the team.

Option C violates role responsibilities—estimation is owned by the team, not stakeholders.

In Scrum, teams are self-organizing, meaning they are responsible for managing internal dynamics and conflicts. The scrum master should act as a servant leader by facilitating conflict resolution rather than imposing decisions.

The scrum master should mediate the situation by fostering open communication and helping the team address concerns constructively.

Encouraging team collaboration and respectful communication is key to maintaining morale.

Escalating to senior management or removing a team member should be a last resort.

Attending meetings does not directly resolve the issue but can help the scrum master observe and intervene when necessary.

By facilitating conflict resolution and supporting team self-organization, the scrum master ensures a healthy and productive work environment.

In a newly formed team, especially in a regulated environment like pharmaceuticals, guiding the team to collaborate effectively and share knowledge is essential. As the team lacks subject matter expertise, fostering an environment of continuous learning and collaboration will help them quickly build knowledge and improve their performance.

It is crucial to organize a meeting to clarify roles and responsibilities. This ensures everyone understands their individual contributions and how they relate to the team’s goals. Clear role definitions are particularly important in a cross-functional team to avoid confusion and ensure smooth collaboration.

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.

Once the team has clarity on the user stories and agrees they are ready, the next step in agile planning is to estimate them. According to the PMI Agile Practice Guide (Section 5.2: Estimating) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), agile estimation techniques like story points or Planning Poker help the team gain a shared understanding of effort, complexity, and delivery time.

Option A is correct: estimating comes before development and guides prioritization and planning.

Option B prematurely dives into task-level detail before effort is understood.

Option C skips planning and development entirely.

Option D refers to retrospective, which comes after execution, not before.

DevOps is a methodology that focuses on enhancing collaboration between development and operations teams to create a continuous feedback loop and speed up the delivery process. The key to enabling and sustaining a fast workflow is the establishment of a culture of collaboration, supported by the right tools and processes that allow for continuous delivery. This culture helps break down silos between teams, leading to faster and more efficient workflows that can continuously deliver value to customers.

The correct answer is C – Work with the team to create a solution for disseminating team knowledge throughout the company.

Agile values shared learning and continuous improvement. A lack of accessible organizational knowledge is a systemic issue. The agile practitioner should help the team implement lightweight, repeatable knowledge-sharing practices—such as wikis, communities of practice, or internal retrospectives.

From the PMI Agile Practice Guide:

“Organizational learning is an essential part of agile culture. Sharing information across teams enables continuous improvement and avoids repeated mistakes.”

(PMI Agile Practice Guide, Section 7.1 – Organizational Learning)

Mike Griffiths adds:

“Coaching agile teams includes promoting knowledge sharing mechanisms across the organization. Practices like open reviews, documentation wikis, or retrospective reports can help teams learn from each other.”

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

Why the other options are incorrect:

A suggests reporting but may become overhead without solving the core issue.

B avoids organizational improvement by isolating the team.

D brings in external help when the issue can be resolved internally.

Answer: C

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

The correct answer is B — Set the velocity to the delivered story points of the last sprint.

Agile velocity is a historical measure, not a target. It represents the amount of work a team actually completed in a previous sprint and should be used to help guide future sprint planning. Teams should not inflate, manipulate, or " game " their velocity; instead, they should use it as a basis for realistic planning.

PMI Agile Practice Guide states:

“Velocity is calculated by totaling the points for all fully completed stories. It is a measure of what the team can complete—not what it hopes to complete—and should be used as an empirical baseline for planning.”

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

Mike Griffiths further explains:

“Velocity should be based on historical data from previous sprints. Teams should not artificially inflate velocity by changing estimation practices or slicing stories merely to appear more productive.”

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

Incorrect options:

A promotes splitting for manipulation, not for clarity.

C suggests altering estimation practices for the sake of metrics.

D implies gaming the system to falsely increase velocity.

Answer: B

—

To calculate cycle time, we use Little’s Law, which states:

Where:

WIP (Work in Progress) = 50 tickets

Throughput = 200 tickets per 8-hour shift

Now, applying the formula:

The correct answer is B – Conduct story-mapping exercises to clarify deliverables and release priorities. Story mapping is a visual practice that aligns stakeholders and teams around a shared understanding of the product vision, user workflows, and incremental delivery plans.

From the PMI Agile Practice Guide:

“Story mapping is a collaborative activity used to understand the user’s journey, prioritize features, and identify releases. It is highly effective for stakeholder alignment and promoting shared understanding.”

(PMI Agile Practice Guide, Section 5.4 – Story Mapping)

Also supported by Mike Griffiths:

“Story mapping promotes visibility, alignment, and prioritization. It fosters collaboration between the team and stakeholders and helps translate business objectives into user stories.”

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

Why other options fall short:

A reverts to heavy documentation, which agile discourages.

C is a one-time event and doesn’t sustain alignment.

D focuses on adherence to process rather than collaboration and planning clarity.

Velocity is a measure of how much work a team completes in a given sprint, typically measured in story points or other units of effort. While velocity can be useful for tracking progress and forecasting future work, it has some limitations when it comes to accurate capacity planning.

Velocity can vary from sprint to sprint due to multiple factors, such as the complexity of the tasks, interruptions, or even external influences. This variability can make it difficult to predict how much work a team can handle in future sprints, leading to inaccurate capacity planning.

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 B – Review the project vision statement.

A shared vision ensures that the team and stakeholders are aligned on the purpose, value, and expected outcomes of the product. In Agile, the vision statement guides product development and ensures that decisions made during iterations are grounded in stakeholder needs.

From the PMI Agile Practice Guide:

“A clear product vision guides the team and stakeholders in understanding the product’s purpose and desired outcomes. The product vision promotes alignment and provides a foundation for ongoing decisions.”

(PMI Agile Practice Guide, Section 5.1 – Vision)

Mike Griffiths also emphasizes:

“A product vision helps ensure everyone is heading in the same direction. It’s critical to regularly revisit this vision to maintain alignment with stakeholders and the evolving product strategy.”

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

Why the other options are incorrect:

A (kick-off meetings) may help in initial orientation but doesn’t sustain alignment over time.

C contradicts Agile’s preference for lightweight documentation and ongoing collaboration.

D is general process alignment—not specific to stakeholder engagement.

Answer: B

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

A spike is a time-boxed research activity used in Agile to explore uncertainties or unknowns, such as dependencies in this case. If the product owner is unsure about the risks related to migrating to a new version of a database, they can request a spike from the team. This will allow the team to investigate the dependencies, assess potential risks, and gather the necessary information to move forward with the user story. This helps reduce uncertainty and makes it easier to make informed decisions about the next steps.

The team ' s primary role is to estimate and define the work items in the product backlog. In an Agile environment, the team collaborates with the product owner to break down user stories into manageable tasks, providing effort estimates (such as story points) to help guide future iterations. The team also works with the product owner to refine and clarify requirements when needed, ensuring that the work is well understood and ready for execution.

The correct answer is C — Introduce agile principles and processes, then make the change an experiment to obtain buy-in.

Agile transformation succeeds when it is driven through team engagement and experimentation, not top-down enforcement. Experimentation aligns with the principle of “failing fast” and encourages teams to experience the value of agile themselves before full adoption.

PMI Agile Practice Guide explains:

“To support organizational change, leaders should create safe-to-fail experiments to allow teams to explore and adopt agile in a non-threatening way. Buy-in emerges through shared learning, not forced compliance.”

(PMI Agile Practice Guide, Section 6.5 – Organizational Change and Culture)

Mike Griffiths reinforces:

“Effective agile leaders lead through influence and create an environment of experimentation and learning. Mandates create resistance, but pilots and feedback loops drive acceptance.”

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

Answer A speaks only to executive buy-in. Answer B is directive and not collaborative. Answer D imposes agile through training but skips experiential learning and feedback.

Answer: C

=================================

Agile teams embrace change and collaborate with customers to deliver value. The PMI Agile Practice Guide (Section 2.1: Agile Mindset) supports responding to change—even late in the development cycle—if it results in business value. The team should accept the new goal, replan with the product owner, and adjust scope or priority if needed, rather than resist or escalate.

Option A is correct: it reflects the agile value of responding to change and delivering early value.

Option B is too rigid and contrary to agile principles.

Option C implies a punitive model that does not align with collaborative agile contracts.

Option D introduces unnecessary cost and overhead without first trying to replan collaboratively.

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

—

Predictable flow in agile is achieved by reducing variability in story size and complexity. According to the PMI Agile Practice Guide (Section 5.7: Flow-based Agile and Kanban), working with small, similarly sized user stories increases throughput predictability and improves cycle time.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) supports breaking large stories into smaller, testable chunks as a way to stabilize delivery and forecasting.

Option A is correct: small user stories reduce variability and support predictable flow.

Option B supports testability but doesn’t directly improve flow.

Option C and D are too broad or conceptual to specifically improve predictability.

In Agile, one of the key principles is to provide continuous feedback and integration throughout the development process, ensuring that components are tested, integrated, and iterated upon regularly. By separating the work into three teams that work independently and only integrate at the end, the strategy risks delaying feedback and potentially causing integration problems. This approach could lead to significant issues when the components are eventually integrated, as they may not work together as expected due to lack of ongoing collaboration and integration. Therefore, working in parallel with proper continuous feedback and integration is crucial in Agile to minimize risks and ensure smooth delivery.

Large user stories, also known as " epic " user stories, can be challenging to manage and lead to difficulties in tracking progress and delivering value incrementally. The Scrum Master should work with the team to break down large user stories into smaller, more manageable pieces. These smaller stories can be completed within a single sprint, allowing the team to deliver value more frequently and with greater clarity. This practice aligns with Agile principles by ensuring that work is broken into digestible chunks that can be iteratively built, tested, and delivered.

A well-defined, mature Definition of Done (DoD) ensures that all aspects of a user story are completed, tested, reviewed, and integrated into the codebase. This sequence includes all necessary steps:

Unit testing ensures the code works as expected.

Meeting the acceptance criteria ensures that the business needs are met.

Business testing and functional testing confirm the product works from both the business and technical perspectives.

Code merging ensures that the feature is integrated into the main branch.

Updating documentation ensures that the product is well-documented for future reference and use.

The Scrum Master’s role as a servant leader is to support the team, not to resolve conflicts for them. It is important for the team to work through their disagreements themselves, as this fosters collaboration and improves their problem-solving skills. The Scrum Master should encourage open communication and guide the team toward healthy conflict resolution, ensuring that the disagreements are addressed constructively. This approach helps the team build trust, improves their cohesion, and strengthens their ability to handle challenges in the future.

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.

The correct answer is C – Encourage the team to more frequently interact with all stakeholders. When an agile team is struggling to meet commitments, one key cause is often a lack of communication or feedback from key stakeholders. Increasing interaction helps align the team ' s priorities, clarify requirements, and improve ownership and accountability.

From the PMI Agile Practice Guide:

“Teams that engage in regular, open communication with stakeholders are better able to align with the evolving needs of the business and take ownership of their commitments. Agile coaches support this behavior by facilitating frequent interactions and improving team dynamics.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement and 6.2 – Coaching the Agile Team)

Mike Griffiths’ PMI-ACP Exam Prep Book reinforces this:

“Encouraging frequent stakeholder interaction fosters a sense of ownership in the team. Agile coaches guide teams to seek clarity through communication rather than rely on assumptions.”

(Mike Griffiths, Chapter 4 – Team Performance and Coaching)

Why the other options are incorrect:

A – Involving the sponsor in team-level performance issues may undermine team self-organization.

B – Providing a list of deliverables doesn’t address the root cause (lack of communication or clarity).

D – Upfront product design goes against agile principles and does not improve team ownership or delivery capability.

Answer: C

The correct answer is A – Self-organize. One of the fundamental principles of agile is that teams are self-organizing and cross-functional. During iteration planning, once the stories are accepted into the sprint, the team collaborates to break down those stories into tasks and assign work among themselves based on skills and interest.

From the PMI Agile Practice Guide:

“Agile teams are self-organizing, meaning they collectively decide how to accomplish their work, rather than being directed by others. This principle supports autonomy and trust, and enhances team ownership and commitment.”

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

Mike Griffiths reinforces:

“Agile teams are trusted to manage themselves. Once user stories are selected during iteration planning, the team decomposes stories into tasks and self-assigns work collaboratively.”

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

Incorrect options:

B contradicts agile principles of self-assignment and voluntary collaboration.

C may be valuable for clarification but is not the first action after stories are added.

D identifying the Scrum Master is irrelevant to the task breakdown phase.

Answer: A

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

The Definition of Done (DoD) is a shared understanding of what it means for work to be considered complete. It is typically defined by the project sponsor and project team in collaboration. The DoD outlines the criteria that must be met for user stories, features, or tasks to be considered done, ensuring alignment between stakeholders and the development team. While the product owner, Scrum master, and stakeholders may influence the criteria, the final agreement on what constitutes " done " is determined by the project team and sponsor.

To ensure high code quality, especially for critical products, agile teams employ technical practices like pair programming and peer code reviews. The PMI Agile Practice Guide (Section 5.5: Technical Practices and Quality) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 5: Quality and Technical Excellence) support these practices as part of built-in quality—ensuring that issues are caught early in the development cycle.

Option A is correct: pair programming and peer reviews increase code quality and reduce defects early.

Option B is essential but a feedback tool—not a direct quality assurance practice.

Option C implies waterfall-style handoffs.

Option D is inefficient and risky without integrated testing or validation.

In Agile, transparency and communication within the team are key. The team member should log the concern into the risk register to formally track the issue and share it with the team at the next standup. This allows the entire team to discuss and assess the situation collaboratively, ensuring that the concern is addressed and managed collectively. This approach aligns with the self-organizing nature of Agile teams, where team members are responsible for working together to find solutions.

The correct answer is C – Non-functional requirements should have been added to the definition of done. Non-functional requirements such as performance, security, or usability criteria apply across stories and should be included in the Definition of Done (DoD) to ensure consistent delivery of quality attributes.

From the PMI Agile Practice Guide:

“The definition of done should incorporate quality standards, including non-functional requirements. This ensures these standards are consistently applied across all deliverables.”

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

Mike Griffiths further explains:

“Non-functional requirements are often best represented in the DoD so they’re applied universally. Without this, teams may deliver functionality that lacks necessary quality characteristics.”

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

Incorrect options:

A would help but isn’t sufficient for global system qualities.

B is suitable for specific stories but doesn’t ensure consistency across the product.

D is helpful but doesn’t guarantee alignment with quality standards.

Answer: C

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

The correct answer is B – Ensured the early engagement of key stakeholders. Agile emphasizes early and continuous stakeholder involvement. In this case, engaging enterprise architects and standards stakeholders early in the design process would have helped detect conflicts before sprint execution.

From the PMI Agile Practice Guide:

“Key stakeholders should be engaged early in the development cycle to ensure alignment with organizational policies, standards, and expectations.”

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

Mike Griffiths notes:

“Involving stakeholders early helps mitigate the risk of late surprises and rework. Enterprise architects should be consulted during backlog grooming or prior to sprint planning.”

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

Incorrect options:

A is reactive and escalatory.

C presumes the standards are flawed without analysis.

D ignores necessary compliance and does not solve the issue proactively.

Answer: B

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

The correct answer is B – Ask the team for suggestions. Agile teams are self-organizing. The Scrum Master should facilitate problem-solving by enabling the team to collaboratively decide how to handle bottlenecks. This approach respects the team ' s autonomy and encourages shared ownership.

From the PMI Agile Practice Guide:

“Scrum Masters facilitate team collaboration and self-organization. When problems arise, they engage the team in identifying and implementing solutions, rather than solving issues unilaterally.”

(PMI Agile Practice Guide, Section 4.3 – Servant Leadership and Team Empowerment)

Mike Griffiths explains:

“The Scrum Master’s role is to facilitate rather than direct. If a team member falls behind, the team should collectively explore options for support, ensuring accountability and transparency.”

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

Incorrect options:

A undermines team autonomy and assigns tasks, which the Scrum Master should not do.

C may help, but addressing issues privately doesn’t promote transparency.

D involves the Product Owner unnecessarily in team internal issues.

Answer: B

In Agile, continuous integration and regression testing should be part of every iteration to ensure that the product is always in a potentially shippable state. These practices help catch issues early in the development process, preventing defects from accumulating and becoming harder to fix later. By integrating and testing frequently, the team ensures that new code works with existing code and that the product maintains its quality throughout the development lifecycle. This approach aligns with Agile principles of delivering working software regularly and maintaining high-quality standards throughout each iteration.

The presence of a single point of knowledge is a significant risk in agile teams. According to the PMI Agile Practice Guide (Section 4.3.3: Team Structure and Cross-functionality) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), agile teams should avoid role silos and promote knowledge sharing. Adding another database administrator helps with both workload distribution and knowledge retention through pairing or mentoring.

Option C is correct: it ensures redundancy and knowledge spread, reducing project risk.

Option A does not address knowledge transfer or team development.

Option B removes the knowledge resource, worsening the risk.

Option D limits knowledge-sharing and still creates a bottleneck.

A quick mock-up (or prototype) is a highly effective way to visually represent the product ' s features and functionality to stakeholders. This allows stakeholders to get a tangible sense of what the product will look like and how it will work. By iterating on this mock-up and adjusting it based on feedback, the team can build consensus and gain stakeholder approval more effectively. This approach encourages active collaboration and ensures that the product aligns with stakeholder expectations early in the development process.

The daily standup is focused on ensuring the team stays synchronized on their commitments for the sprint, and it is meant to be a short meeting where team members quickly discuss what they did the previous day, what they plan to do today, and any blockers they are facing. It is not a forum for external stakeholders to ask detailed questions about the sprint backlog or delivery timelines, as this can disrupt the team ' s focus and hinder the meeting ' s efficiency.

By explaining that the standup is about synchronizing commitments, the project manager helps the business partners understand the purpose of the meeting and suggests an appropriate time and place for discussing more detailed or strategic topics.

The project manager should ensure that risks are clearly visible to all team members so that everyone is aware of potential issues and can take action as necessary. Displaying the RAID log visually makes it easy for the team to see the status of risks, assumptions, issues, and dependencies in real-time. This encourages the team to follow up on risks and keep them top of mind, facilitating more proactive management of potential threats to the sprint ' s success. This approach also helps in maintaining transparency and continuous monitoring of risks throughout the sprint.

In agile environments, planning should be flexible and adaptable to changing circumstances. Just-in-time (JIT) refinement refers to the practice of refining the backlog and details of the product features as they become more relevant, rather than attempting to plan everything upfront. This allows the team to respond to changes and new information as they emerge, which aligns with agile principles of iterative development and adaptability.

In Scrum, velocity is a metric that measures the amount of work a team can complete in a given sprint, usually measured in story points or work units. However, velocity is not a metric for team efficiency or quality. It primarily reflects the team ' s capacity to complete work within a sprint and can help forecast future work delivery once the team becomes stable. A team may have a stable velocity, but that does not necessarily mean they are producing higher-quality or more efficient deliverables.

The correct answer is C — Update current user stories.

Acceptance criteria are part of a user story’s definition and describe the specific conditions under which the story is considered complete. As user stories evolve and more clarity is gained, acceptance criteria must be updated within the user story itself to ensure mutual understanding of scope and expectations between the product owner and the development team.

According to PMI Agile Practice Guide:

“Acceptance criteria are detailed during backlog refinement and are commonly added to user stories to define the done conditions. These are updated throughout the lifecycle of the story as more details emerge.”

(PMI Agile Practice Guide, Section 5.2 — Backlog Refinement)

Mike Griffiths reinforces this:

“Acceptance criteria serve as the test conditions for confirming user stories. They are not fixed and can be elaborated collaboratively during grooming or development, and are updated directly in the user story.”

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

Other options:

A refers to adding more stories, not updating existing ones.

B (retrospectives) are used for process improvement, not for editing user stories.

D (project plan) reflects a traditional mindset and not applicable in Agile.

Answer: C

—

By moving to an iterative approach, the organization can focus more on delivering value and benefits incrementally, with each iteration producing a working product or a usable increment. This allows the team to receive feedback from stakeholders more frequently and make adjustments as needed, ensuring that the most valuable features are prioritized and delivered in a timely manner. Unlike a predictive approach, where the focus is often on completing tasks according to a strict plan, an iterative approach allows for flexibility and continuous improvement, ensuring the product better aligns with user needs and business objectives.

The correct answer is D — Periodically, at both the release and project level.

Agile planning is iterative and layered. When new requirements or constraints emerge, plans should be updated at the appropriate levels—sprint, release, and potentially the overall project level. Periodic adjustments ensure continued alignment with business needs and system dependencies.

PMI Agile Practice Guide:

“Agile planning is done at multiple levels: product vision, roadmap, release, iteration, and daily. These plans are continually updated based on new learning and stakeholder feedback.”

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

Mike Griffiths:

“Effective planning includes periodic updates at all planning horizons. Adjusting at both the project and release levels ensures strategic alignment and tactical feasibility.”

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

Incorrect options:

A misses the iterative nature of Agile planning.

B and C are too narrow in scope.

Answer: D

—

The correct answer is A – Include it in the product backlog and use a new indicator to annotate that it is technical debt. Agile teams track technical debt transparently by adding it to the product backlog. Marking it with a clear label helps the team and product owner consider it during prioritization and planning.

From the PMI Agile Practice Guide:

“Technical debt should be made visible and added to the product backlog. Teams may use tags or indicators to distinguish it and make informed prioritization decisions.”

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

Mike Griffiths emphasizes:

“Technical debt must be tracked in the backlog to avoid long-term consequences. Tagging it ensures stakeholders are aware and can prioritize its resolution appropriately.”

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

Incorrect options:

B assumes all technical debt is low priority, which may not be true.

C is incorrect; agile explicitly recommends tracking tech debt.

D introduces inconsistency and reduces visibility.

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

The correct answer is D – Write tests that will be used to know when a story has been correctly developed. This practice aligns with Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD), which are common in agile environments. Agile promotes defining “done” through clear acceptance criteria and tests before coding begins.

From PMI Agile Practice Guide:

“Agile teams use test-first practices, such as TDD or ATDD, where acceptance tests are written before development begins. This ensures that functionality is built to meet agreed expectations.”

(PMI Agile Practice Guide, Section 5.5 – Agile Testing and Quality Strategies)

From Mike Griffiths’ PMI-ACP Exam Prep Book:

“Defining acceptance criteria or tests before development is a core agile practice. It ensures the team understands what success looks like and builds quality in from the start.”

(Mike Griffiths, Chapter 6 – Problem Detection and Resolution)

Option A may be useful but is unrelated to the new requirements.

Option B is not standard—customers help define acceptance criteria but rarely write tests.

Option C skips an important quality control step and doesn’t align with test-first practices.

Answer: D

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

In Agile, flexibility and adaptability are key, especially when dealing with uncertain or changing requirements like evolving government regulations. The agile coach should ensure that the team is building the product incrementally, allowing for adjustments as needed. This way, when the regulatory changes occur, the team can adapt quickly without disrupting the entire release process. By focusing on delivering small, workable increments, the team can respond to changes more efficiently.

The correct answer is B — Create a spike story to determine what needs to be done to use the new interface.

A spike is a special user story designed to address technical uncertainty or risk. It allows the team to explore, research, or prototype solutions within a time-box. Spikes are particularly useful for investigating unknowns such as integration with vendor systems.

PMI Agile Practice Guide:

“Spikes are used for research and exploration. They help teams gain knowledge about technology, functionality, or business domain that is necessary before estimating or implementing a feature.”

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

Mike Griffiths notes:

“Spikes reduce uncertainty and are valuable tools for backlog refinement. They are especially helpful when the team is unsure how to implement a requirement or integrate external components.”

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

Other options:

A may delay addressing the issue until the next monthly meeting.

C defers the issue rather than exploring it.

D assumes outsourcing is the only solution and may remove team ownership.

Answer: B

—

When the client needs to release the product earlier than planned to start receiving revenue, the best way to accommodate this request is by focusing on delivering a minimum viable product (MVP). The MVP allows the team to prioritize the most essential features that provide value to the customer, ensuring that the product can be launched quickly, while still addressing the core needs of the business.

By focusing on the MVP, the product can still be launched on time, and the client can start receiving revenue sooner without waiting for the full product to be completed. This aligns with agile principles of delivering valuable, incremental releases.

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.

Spikes are meant for experimentation and learning, not guaranteed outcomes. According to the PMI Agile Practice Guide (Section 5.2 Spikes), if a spike does not lead to a clear solution, the team can extend or reframe it, especially when aiming for a sustainable long-term solution. Agile supports encouraging experimentation and learning from failure.

Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Problem Detection and Resolution) recommends adapting when a spike’s results are inconclusive—redefining the scope and collaborating as a team increases the chance of a valuable outcome.

Option B is correct: it continues learning and promotes team collaboration.

Option A undercuts team ownership.

Option C prioritizes a short-term fix and undermines agile values.

Option D is not needed at this early stage—root cause analysis is better for recurring or systemic issues.

The correct answer is D – Use the team ' s historical velocity to calculate a range of features that can be delivered. Agile emphasizes forecasting over commitment, and this is achieved through empirical data such as velocity. Providing a range based on historical velocity allows for realistic planning while acknowledging uncertainty.

From the PMI Agile Practice Guide:

“Agile forecasting is based on empirical data. Teams use their past velocity to forecast how much work they can complete in a given time frame. This forecast is typically expressed as a range to account for variability.”

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

Mike Griffiths supports this:

“Rather than commit to fixed scope, agile teams use historical velocity and prioritized backlogs to forecast delivery. Forecasts are probabilistic, not promises.”

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

Incorrect options:

A violates agile’s core value of responding to change over following a fixed plan.

B delays valuable forecasting data.

C implies commitment rather than forecast.

Answer: D

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

The correct answer is D — The team should reevaluate time and cost estimates to reflect the latest understanding of the work effort.

Agile supports progressive elaboration and adaptive planning. When actual effort consistently exceeds estimates, it signals a need to recalibrate estimation practices. The team should revisit their velocity, estimation techniques, and potentially re-estimate upcoming work with improved understanding.

PMI Agile Practice Guide:

“Agile uses adaptive planning, where teams update estimates based on new information. This supports better forecasting and risk management.”

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

Mike Griffiths:

“Estimation accuracy improves over time. Agile teams regularly inspect estimation practices and adjust based on historical data and team maturity.”

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

—

At this point in the planning process, the team has not yet gathered enough data to provide a precise release date. The team ' s velocity (the amount of work they can complete in each iteration) has not been established, and the team needs some iterations to stabilize and gather insights. However, they can offer a broad range based on the current understanding of the backlog and priorities. This allows the sponsor to have a rough expectation while also managing the uncertainty involved at this stage in the process.

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 probing questions to other team members to encourage dissenting viewpoints.

Agile coaches foster team collaboration and help surface diverse opinions. When one member dominates, the coach should use facilitation techniques to ensure equal voice. Encouraging quieter team members to contribute through thoughtful questions promotes balanced participation and trust.

PMI Agile Practice Guide:

“Agile coaches foster an environment of trust and collaboration. When team dynamics are unbalanced, the coach helps ensure psychological safety and equal participation.”

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

Mike Griffiths:

“Coaches use powerful questions to draw out quieter team members and help build a culture where everyone feels heard and valued.”

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

Incorrect choices:

A is extreme and non-collaborative.

B ignores the coach’s facilitative responsibilities.

D is reactive and too late.

—

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

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 correct answer is A – Create a user story for this new improvement and put it in the product backlog for prioritization and validation by the customer. Agile is iterative and feedback-driven. New requirements or enhancements identified during reviews are treated like any other backlog item: they are created as user stories, evaluated, and prioritized collaboratively.

From the PMI Agile Practice Guide:

“Feedback during review meetings may lead to new stories. These are added to the product backlog and prioritized based on value, risk, and customer need.”

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

Mike Griffiths explains:

“Agile welcomes change—even late in development. New feedback should be captured as stories, then reviewed and prioritized by the Product Owner in alignment with business goals.”

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

Incorrect options:

B assumes premature prioritization.

C implies scope creep, which contradicts agile’s flexibility.

D contradicts team empowerment and planning integrity.

Answer: A

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

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

The correct answer is D – Understand the impediments and facilitate issue resolution to enable the team to succeed.

The Agile Project Manager (or Scrum Master) acts as a servant leader by removing impediments and coaching the team toward improvement. Instead of dictating action or adjusting timeboxes, the right approach is to facilitate problem-solving and help the team meet its sprint goal.

From the PMI Agile Practice Guide:

“The Scrum Master works to remove impediments and support the team’s progress. They do not give commands but instead facilitate improvement.”

(PMI Agile Practice Guide, Section 5.2 – Roles and Responsibilities)

Mike Griffiths affirms:

“Agile leaders remove roadblocks and create an environment where the team can succeed. They support rather than direct.”

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

Other options are inappropriate:

A is command-and-control, not servant leadership.

B violates timebox principles of Scrum.

C misplaces responsibility for testing onto customers.

Answer: D

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

Sprint planning or any task-level technical meeting should involve the development team and the product owner, as they are the key players in delivering and clarifying work. According to the PMI Agile Practice Guide (Section 3.3: Agile Roles and Responsibilities) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), the Scrum Master facilitates the meeting, while the development team and product owner collaborate on the details.

Option D is correct: the core team (developers) and product owner are the correct participants for story elaboration and commitment.

Option A and C involve the customer and sponsor unnecessarily for a technical planning meeting.

Option B includes " key stakeholders, " which may be overkill unless specific business input is needed.

The correct answer is C – Ensure that members begin to self-organize as small teams with efficiently distributed skills.

Agile emphasizes self-organizing teams. When teams are too large, splitting into smaller teams is a good practice (Scrum recommends 5–9 members per team). However, rather than top-down assignment, the Scrum Master should enable and support self-organization. Teams should be encouraged to form organically while ensuring knowledge-sharing and cross-functional capabilities.

From the PMI Agile Practice Guide:

“Agile leaders support team self-organization by creating an environment of trust and encouraging the team to determine how best to accomplish their work.”

(PMI Agile Practice Guide, Section 5.2 – Team Composition)

Mike Griffiths writes:

“Agile teams are self-organizing, and the role of the leader is to facilitate the conditions for that to occur, not to direct assignments.”

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

Why other options are less appropriate:

A suggests command-and-control behavior, which is contrary to Agile values.

B makes assumptions about comfort levels and may ignore skill diversity.

D disregards team input and imposes a solution, limiting buy-in and trust.

Answer: C

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

Agile teams are self-organizing and responsible for determining how to deliver their commitments. According to the PMI Agile Practice Guide (Section 4.3.3: Self-Organizing Teams) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), the best course of action is to support the team in evaluating trade-offs—especially when innovation like a spike can enhance efficiency. The project leader should enable, not dictate decisions.

Option A is correct: it respects team autonomy while supporting innovation.

Option B discourages innovation and learning.

Option C may delay needed improvement and demotivates team initiative.

Option D removes the team ' s ability to decide and self-manage priorities.

A value stream map is a tool used to visualize the flow of materials and information through a process, identifying areas of waste and inefficiency. In this case, the business analyst ' s key observations will include wait times (delays between steps) and cycle times (time taken to complete each step in the process). By analyzing these, the business analyst can identify opportunities to streamline the process, reduce delays, and improve overall efficiency in delivering healthcare services.

The correct answer is B – Recommend an Agile delivery approach and provide information to the stakeholders on Agile values and principles.

Agile enables early and continuous delivery of valuable software, short feedback loops, and faster time to market. When competitive advantage and speed are critical, introducing Agile principles allows the organization to remain flexible, respond to change, and deliver increments faster.

From the PMI Agile Practice Guide:

“Agile approaches provide quicker feedback, faster time to market, and more opportunity to deliver business value early. They are ideal in dynamic environments with evolving customer needs.”

(PMI Agile Practice Guide, Section 1.3 – When to Use Agile)

Mike Griffiths states:

“Agile emphasizes early and continuous delivery, allowing organizations to test, learn, and adjust quickly to changes—critical for achieving business agility and competitive advantage.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 1 – Agile Mindset)

Why other options are not optimal:

A suggests a predictive mindset and planning before implementation.

C focuses only on Scrum roles, which may be too narrow for organizational-level change.

D relies on traditional governance structures that may resist Agile change.

Answer: B

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

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 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.

Kanban is an approach that focuses on visualizing and managing work in process (WIP) to ensure that there is minimal waste and that teams only work on what they can handle at any given time. It provides a flexible framework for continuous improvement, without the overhead of time-boxed iterations like in Scrum. Kanban allows teams to focus on limiting work in process, streamlining workflows, and improving efficiency while avoiding waste. This approach aligns with the organization ' s desire to minimize overhead and control WIP to maximize flow and productivity.

Agile roles are clearly defined to avoid overlap and confusion. According to the PMI Agile Practice Guide (Section 3.3 Agile Roles), the Product Owner is responsible for backlog prioritization and stakeholder communication, not managing team tasks. Task management is the domain of the self-organizing team and facilitated by the Scrum Master or Agile Project Manager.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) reinforces that resolving role confusion through discussion helps realign expectations and improve team performance.

Option C is correct: by clarifying roles and responsibilities, the agile project manager helps prevent overreach and ensures smoother collaboration.

Option A addresses the issue too late and in the wrong forum.

Option B misrepresents agile dynamics (self-organizing teams).

Option D risks team morale and doesn’t address the root cause.

Analyzing the burndown chart, we see:

Points Planned (gray squares): decreasing steadily from 50 to 0 over 10 days (ideal burn).

Points Completed (gray triangles): plateau between days 3–6, lagging significantly behind planned completion.

This indicates that the team is behind schedule, and unless they accelerate, they may fail to complete all committed work.

According to the PMI Agile Practice Guide (Section 5.4: Burndown Charts) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Monitoring Progress), such divergence between the ideal and actual burn lines indicates that the iteration is at risk.

Option A is correct: the iteration is in jeopardy due to lack of progress mid-sprint.

Option B is incorrect—scope removal would show a downward shift in planned points.

Option C is false—the team is behind, not ahead.

Option D is misleading—velocity appears inconsistent (e.g., plateau from day 3–6).

The team lead should facilitate a constructive discussion by restating both perspectives clearly, which can help ensure that all team members understand each other ' s viewpoints. Asking for more details about both approaches allows the team to analyze each method ' s pros and cons, fostering a collaborative, solution-focused discussion. Creating a chart of similarities and differences can provide a visual representation that helps the team make an informed decision, highlighting which elements from both approaches might be beneficial. This approach encourages open communication, avoids escalation, and leads to a productive exploration of options without dismissing either side.

The correct answer is C – Amount of work that can be accomplished in an iteration. To create a release plan, an agile team uses its historical or estimated velocity—how much work the team can complete in a single iteration. This information helps forecast how many iterations will be needed to complete the prioritized work in the product backlog.

From the PMI Agile Practice Guide:

“Velocity is used to determine how many iterations are required to complete the release backlog. Release planning requires an understanding of how much work can be completed per iteration to forecast delivery timelines.”

(PMI Agile Practice Guide, Section 5.3 – Iteration Planning and Velocity)

Mike Griffiths adds:

“Teams use their average velocity—the amount of work completed per iteration—as the basis for release planning. This supports predictable and empirical planning.”

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

Incorrect options:

A focuses too narrowly on a single story, not the full release.

B focuses on individual capacity, which is contrary to agile’s emphasis on team output.

D is vague; capacity is better measured by iteration.

Answer: C

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

Transparency is key in agile. The PMI Agile Practice Guide (Section 7.1 Communications) emphasizes the use of information radiators—visual displays such as task boards, burndown charts, or Kanban boards that immediately communicate project status. These tools make progress visible to all stakeholders without needing detailed documentation.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) reinforces that collocated displays or shared online boards reduce misunderstandings and keep stakeholders aligned.

Option D is correct: a public project board offers real-time visibility and promotes transparency.

Option A contradicts agile by emphasizing documentation over working software.

Option B limits visibility to a subset of stakeholders and is passive.

Option C disrupts the team’s daily focus—stand-ups are not intended for stakeholder participation.

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.

When an agile team ' s velocity is slowing down, it is essential to regularly evaluate and adjust how the team is performing. By using feedback loops in every sprint, the team lead can continuously assess the team ' s progress, identify bottlenecks, and address issues early on. These feedback loops, typically discussed in sprint retrospectives, provide an opportunity for the team to identify the root causes of challenges, such as miscommunications, and make improvements to ensure better performance in future iterations. This approach promotes ongoing reflection and adaptation, which are core principles of Agile.

The correct answer is C – Explain that the Kanban board enables the team to complete the work and increases transparency on work that is not done.

Agile values transparency, visibility, and collaboration. Kanban boards are a form of information radiator—tools that openly display the team’s workflow, work-in-progress (WIP), and progress toward goals. Their visibility helps stakeholders and the team remain aligned and encourages accountability.

From the PMI Agile Practice Guide:

“Agile teams use information radiators such as Kanban boards to provide transparency and make status, bottlenecks, and priorities visible to all. This fosters trust, communication, and quick decision-making.”

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

Mike Griffiths adds:

“Visibility into progress and issues enhances communication and alignment across stakeholders. Information radiators like task boards or Kanban boards are vital tools for agile success.”

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

Other options are inappropriate:

A and D compromise transparency and contradict agile values.

B misstates the purpose of the Kanban board—it’s not about assigning work post-completion.

Answer: C

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

The ideal way to resolve the conflict is to encourage the team to brainstorm and propose an alternative solution that meets the intent of the architect’s request (error logging) but with a solution that fits within the current release timeline. By implementing error logging at the client level, the team can still address the monitoring and logging needs without significantly delaying the release. This approach fosters collaboration, balances priorities, and focuses on delivering value within the agreed timeline.

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 methodology, particularly in Scrum, it is essential to focus on delivering value through iterative, incremental development. Rather than planning everything upfront for the entire 2-year duration, the focus should be on delivering small, manageable releases on a regular cadence, allowing for flexibility and adaptability based on feedback from stakeholders. This approach helps to ensure that the team remains responsive to changing requirements and can continually improve the product over time.

According to the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), stories are only marked complete if they meet the Definition of Done (DoD) and are accepted by the product owner and stakeholders. If the customer (or their representative) raises a legitimate concern during the review, the story should be treated as incomplete until consensus is reached or it meets expectations.

Option A is correct: if the story does not meet customer expectations, it should be reprioritized for the next sprint or refined.

Option B and D incorrectly assume that product owner or team authority overrides customer feedback.

Option C suggests discarding the story, which is inappropriate if the customer still needs the functionality.

Stakeholder feedback is critical in agile, and the goal is delivering value, not simply completing a checklist.

The correct answer is C – Ensure the team captures the technical dependencies as issues within the backlog and prioritize based on value optimization. In Agile, technical considerations are factored into backlog refinement and sprint planning. Dependencies should be visualized and managed as part of adaptive planning while still striving to deliver maximum value.

From the PMI Agile Practice Guide:

“Backlog items with technical dependencies should be identified and addressed collaboratively. Agile teams balance value with feasibility and technical constraints to optimize delivery.”

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

Mike Griffiths explains:

“While business value drives prioritization, technical constraints influence the ordering of stories. Agile planning is adaptive; dependencies and delivery risks are identified early and managed through backlog reordering.”

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

Incorrect options:

A may discard valuable features unnecessarily.

B risks accumulating technical debt and incomplete work.

D shifts responsibility away from the team and PO unnecessarily.

Answer: C

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

The correct answer is A — Suggest the product owner start by focusing on the next 2 sprints instead of 10.

Agile embraces progressive elaboration — planning is done in detail only for the near term, while long-term plans remain high level and flexible. By encouraging short-term focus, the Scrum Master helps the product owner shift from a predictive mindset to an adaptive one.

PMI Agile Practice Guide:

“Agile projects plan at multiple levels (release, iteration, and daily), focusing on near-term commitments while allowing flexibility for change. Planning multiple sprints in detail violates the principle of adaptability.”

(PMI Agile Practice Guide, Section 5.3 — Progressive Elaboration)

Mike Griffiths adds:

“Detailed long-term estimates reduce agility. The product owner should learn to prioritize work based on value, and accept that estimates beyond the next sprint or two are rough forecasts.”

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

Other options:

B undermines agile principles by reverting to waterfall planning.

C misuses the retrospective, which is team-focused.

D may alienate the product owner rather than encourage a mindset shift.

Answer: A

—

The retrospective is the agile ceremony designed for teams to inspect and adapt their process based on actual performance. According to the PMI Agile Practice Guide (Section 5.6: Retrospectives), discussing velocity issues and delivery concerns during retrospectives allows the team to collaboratively identify improvement actions.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) also notes that retrospectives are the best setting to discuss variations in velocity and refine estimation or planning practices based on empirical evidence.

Option C is correct: the retrospective is where the team adapts based on reality.

Option A may come later but doesn’t address the root issue.

Option B goes against agile principles of stable teams and empirical planning.

Option D is reactive and may mask underlying process issues.

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 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

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

In Agile, building increments and ensuring early feedback are key to delivering value quickly and meeting tight deadlines. By focusing on delivering a minimum viable product (MVP), the team can provide the customer with a version of the product that delivers essential functionality early, which allows for feedback and adjustments before the final version is released. This approach helps the team stay within the limited budget and timeline while ensuring that they are delivering the most important features first. Additionally, early customer feedback ensures that the team is on track to meet the project goals and allows for the rapid adaptation of the product.

According to the PMI Agile Practice Guide (Section 7.2.2), one of the key responsibilities of the agile practitioner is to actively engage stakeholders throughout the development cycle—not just during review meetings. Agile frameworks promote continuous collaboration and frequent feedback. Merely attending sprint reviews is passive participation and may lead to missed alignment on expectations.

Mike Griffiths also emphasizes in his PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) that stakeholder satisfaction requires more than periodic visibility—it requires ongoing interaction and inclusion in decision-making and backlog refinement sessions. This deepens shared understanding and reduces the risk of late-stage surprises.

Hence, answer B is correct because proactive stakeholder engagement with the product owner fosters mutual understanding, timely feedback, and course correction—ensuring the product aligns with expectations.

The Scrum Master should help ensure that stakeholders understand Agile principles and terms correctly to facilitate smooth decision-making. Organizing training sessions is an effective way to address misunderstandings and create awareness around Agile values. By ensuring all stakeholders are on the same page, the team can move forward with a shared understanding, which is critical for successfully implementing Agile methodologies. This approach promotes long-term buy-in and alignment, rather than simply pushing for a decision without proper education or consensus.

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

=========

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.

In Kanban, limiting work in progress (WIP) is a key practice to improve task flow and reduce bottlenecks. By restricting the number of tasks that can be worked on at any given time, the team is forced to focus on completing the tasks that are already in progress before taking on new ones. This helps reduce the accumulation of tasks in the " In Progress " column, ensures that tasks move through the workflow more efficiently, and ultimately helps to meet project timelines more effectively. It also promotes better quality, as team members can focus on fewer tasks at a time.

The correct answer is B – Discuss the issue with the team in the daily stand-up meetings. Agile emphasizes transparency, collaboration, and self-organization. The daily stand-up is an appropriate forum to raise and discuss workload distribution so the team can adjust and support each other.

From the PMI Agile Practice Guide:

“Daily stand-ups are a tool for fostering open communication, uncovering impediments, and adjusting the plan for the day. It enables the team to help each other balance workloads and remove bottlenecks.”

(PMI Agile Practice Guide, Section 5.2 – Daily Stand-Ups)

Mike Griffiths explains:

“Team members should use stand-ups to discuss challenges. If someone is overloaded, the team can identify ways to redistribute work to maintain balance and avoid burnout.”

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

Incorrect options:

A escalates the issue unnecessarily and bypasses team self-management.

C is too narrow and private for a team-based issue.

D adds administrative burden without solving the underlying problem.

Answer: B

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

A product roadmap is a high-level visual representation of a product ' s development strategy, highlighting upcoming product releases and the features or goals that will be included in each release. By displaying the roadmap, the agile project manager is ensuring that all stakeholders are aligned on what the product will deliver and when, helping to manage expectations and communicate progress. This is essential for ensuring that everyone involved in the project has a shared understanding of the product ' s direction and key milestones.

Stated understanding of the release goal

The release goal provides clarity on the purpose and objectives of the release. It helps stakeholders understand the value the team aims to deliver.

List of the user stories that will be part of the next releases

A well-defined list of user stories ensures that stakeholders know which features and functionalities are planned for upcoming releases.

The correct answer is D – Have the Product Owner explain the product vision and review the release plan with the team. One of the Product Owner’s key responsibilities is to communicate the product vision and ensure the team understands how their work aligns with business value. This fosters alignment and motivation.

From the PMI Agile Practice Guide:

“The Product Owner is responsible for communicating the product vision and roadmap. This ensures that the team understands the ‘why’ behind the work and how each piece contributes to overall business goals.”

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

Mike Griffiths adds:

“Teams need context for their work. The product owner provides this by clearly sharing the vision and maintaining a transparent roadmap.”

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

Incorrect options:

A is useful but doesn’t address the larger product context.

B may help with story structuring but doesn’t clarify vision.

C delays resolving an immediate misunderstanding.

Answer: D

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

The requirement for the home button to be recognizable is subjective and requires clarification from a design perspective. The team should consult the design team or subject matter experts (SMEs) who have expertise in user experience (UX) and interface design. These experts can provide specific guidelines or criteria for what constitutes a recognizable home button, such as color, shape, placement, or icons. This ensures that the team can create an appropriate, measurable test for the requirement.

The correct answer is D – Increase the opportunities to confirm common understanding with the client.

The rise in defects and change requests indicates a disconnect between what the team is delivering and what the customer expects. Agile emphasizes constant feedback and collaboration. Ensuring shared understanding through frequent interaction and validation reduces misunderstandings and rework.

From the PMI Agile Practice Guide:

“Frequent interactions with customers and stakeholders help teams build a shared understanding and reduce the risk of misaligned expectations and defects.”

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

Mike Griffiths explains:

“A high defect rate often results from unclear requirements. Teams should improve communication loops with stakeholders to confirm understanding before development begins.”

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

Why the other options are suboptimal:

A doesn’t address the root cause: misalignment with the client.

B is reactive and temporary, not a sustainable solution.

C may help but should be preceded by improving collaboration and understanding.

Answer: D

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

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

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

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 information radiator is a key tool in Agile that provides a real-time, visual display of the project ' s current status, including progress, completed tasks, blockers, and upcoming work. This is typically made accessible to all stakeholders and is updated regularly to ensure transparency and communication. Instead of relying on emails or meeting invites, the Scrum Master should direct the customer representative to the information radiator, as it provides the most up-to-date and easily accessible information about the project’s progress. This encourages transparency and aligns with Agile principles of open communication and visibility.