Pass the PMI Agile PMI-ACP Questions and answers with ValidTests

Sprint reviews are a crucial Scrum event for obtaining early feedback from stakeholders, which allows the team to inspect the progress and adapt the product accordingly. By skipping sprint reviews in favor of only release reviews, the team loses the opportunity to make adjustments and improvements throughout the project. The scrum master should emphasize the importance of regular feedback and ensure the team stays aligned with Scrum principles for continuous improvement and value delivery.

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.

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

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

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

Option Cis usefulaftera solution is implemented but not the priority when the cause is unknown.

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

The correct answer is C – The users can help the team understand if the feature adds value, avoiding the risk of building the wrong product.

Prototyping in agile serves as a lightweight modeling technique that supports discovery and stakeholder validation. It helps clarify uncertain requirements, encourages collaboration, and ensures that the solution being developed meets user needs and delivers value.

From the PMI Agile Practice Guide:

“Prototypes allow teams to explore solutions before committing to full development. They support value delivery by engaging users early to verify what is needed.”

(PMI Agile Practice Guide, Section 5.2 – Exploring and Confirming Requirements)

Also:

“Engaging stakeholders in early solution validation through techniques such as wireframes or mockups reduces the risk of developing the wrong product.”

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

Mike Griffiths reinforces this approach:

“Prototyping enhances discovery. It supports feedback loops that validate whether a feature adds value before it's built—especially useful when requirements are unclear.”

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

Why other options are less correct:

A is a secondary benefit but not the primary goal of prototyping.

B is speculative and does not reflect the sponsor's actual recommendation.

D misrepresents the purpose of prototyping, which is for discovery, not accelerated deployment.

Answer: C

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

The correct answer is B – Retrospective meeting.

The retrospective is a key Agile ceremony dedicated to continuous improvement. It provides a safe space for the team to reflect on what went well, what didn’t, and how to improve. When morale is low or conflicts arise, retrospectives help surface issues and co-create solutions.

From the PMI Agile Practice Guide:

“Retrospectives are a vital part of continuous improvement. They are used to inspect team processes, relationships, and interactions to find ways to work more effectively.”

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

Mike Griffiths emphasizes:

“The retrospective is the heartbeat of improvement. It is where the team reflects, adjusts, and grows. Conflict and low morale are ideal triggers for a meaningful retrospective.”

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

Other options explained:

A (Standup) is for daily coordination, not reflection.

C (Demo) is customer-facing and not a morale tool.

D (Offsite) may help later, but is not a formal Agile method for resolving internal team issues.

Answer: B

The Scrum retrospective is the appropriate place for the team to reflect on what went well and what didn’t, including the missed sprint goals. The Scrum master should facilitate an open and constructive discussion about the impediments faced during the sprint, such as the unavailability of the specialist, and help the team find ways to avoid or mitigate similar issues in future sprints. This helps the team continuously improve and ensures that they are better prepared for future challenges.

The agile lead is emphasizing the importance of creating a safe environment for disagreement, which encourages constructive conflict. In Agile, this is crucial because it allows team members to openly express differing opinions and perspectives. Such discussions often lead to better decision-making by surfacing various viewpoints and potential solutions. When teams feel safe to disagree, it fosters creativity, innovation, and problem-solving without fear of retribution. This aligns with Agile principles of collaboration, transparency, and continuous improvement.

According to thePMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance)andMike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery), stories areonly 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 asincompleteuntil consensus is reached or it meets expectations.

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

Option BandDincorrectly assume that product owner or team authority overrides customer feedback.

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

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

As a servant leader, the agile coach’s role is to support and empower the team, helping them overcome obstacles that hinder their progress. In this case, the coach should focus on identifying and removing any impediments that are slowing down the work, whether they are technical, process-related, or communication-based. This approach enables the team to work more efficiently, enhances their ability to self-organize, and ensures they can deliver high-quality results. Simply adjusting the work plan or assigning more resources may not address the underlying issues, and a command-and-control approach is counterproductive in an Agile environment.

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.