The correct answer is C — Conducted an end-of-phase demonstration.

Agile emphasizes continuous feedback. Regular demonstrations (e.g., sprint reviews or product demos) allow stakeholders, including the customer, to inspect the product increment and provide real-time feedback. Had the team demoed the product, they might have discovered the deficiencies before release.

PMI Agile Practice Guide states:

“A demo or review allows stakeholders to inspect the product increment and provide feedback. Demonstrations reduce the risk of unmet expectations and confirm that the team is building the right product.”

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

Mike Griffiths writes:

“Agile avoids large, end-of-phase validations. Instead, customer feedback is solicited at the end of every iteration through structured demos. This allows for early course correction and alignment with expectations.”

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

Other options:

A is a waterfall artifact and not aligned with agile workflows.

B is analysis-heavy and doesn’t ensure real stakeholder feedback.

D (retrospective) improves process, not product validation.

Answer: C

The correct answer is B — Create a spike story to analyze the impact of the threshold requirement on current stories.

A “spike” is a research activity used in Agile to investigate a technical or functional uncertainty. In this case, the performance threshold requires exploration to understand its impact on multiple backlog items. Creating a time-boxed spike allows the team to analyze without prematurely committing to changes.

PMI Agile Practice Guide describes spikes as:

“A spike is a user story for time-boxed research or exploration. Teams use spikes when they need more information to estimate or deliver a story.”

(PMI Agile Practice Guide, Section 5.2 — Types of Backlog Items)

Mike Griffiths adds:

“When a new requirement introduces uncertainty, such as performance constraints, creating a spike helps the team determine scope, risk, and impact before incorporating it into backlog stories.”

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

Other options:

A prematurely alters acceptance criteria before understanding the impact.

C leans toward big upfront design (non-agile).

D skips the exploration phase and directly breaks into tasks.

Answer: B

—

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

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

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

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

The correct answer is A – Reduced or improper customer collaboration.

One of the core principles of Agile is continuous collaboration with the customer. If multiple feature changes are only identified during a late-stage review, it typically indicates that the customer was not involved sufficiently throughout the development process.

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

“Customer collaboration over contract negotiation.”

“Working software is delivered frequently… with a preference to the shorter timescale.”

And from the PMI Agile Practice Guide:

“Ongoing engagement with the customer helps align product features with actual needs and reduce surprises during late-stage reviews.”

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

Mike Griffiths also emphasizes:

“When customers are involved in iteration reviews and backlog grooming, their evolving needs are captured in real time. Surprises during release reviews usually reflect a failure of ongoing communication.”

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

Other options don’t directly address the root cause:

B may contribute, but customer collaboration is the key differentiator in agile.

C and D are traditional causes of waterfall-style failure, not typically root causes in agile.

Answer: A

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

The correct answer is C — Facilitate team brainstorming of the risks resulting from complexity for the risk register.

Technical complexity introduces risks that must be identified and managed early. Agile leaders support teams by facilitating collaborative risk identification, not by dictating solutions. Brainstorming sessions help surface concerns and lead to proactive mitigation strategies.

PMI Agile Practice Guide:

“Risks are best identified through team collaboration. Facilitated risk identification sessions encourage broad participation and lead to better awareness and ownership of potential issues.”

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

Mike Griffiths:

“In agile projects, technical risks are treated early. Collaborative identification and visibility are key to creating a risk-adjusted delivery plan.”

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

Incorrect options:

A is valid long-term, but brainstorming comes first for awareness.

B limits risk planning to a fixed period (Sprint 0), which may not be enough.

D promotes innovation but not structured risk identification.

Answer: C

—

The daily stand-up (daily Scrum) is a time-boxed coordination meeting where each team member answers the three key questions: What did I do yesterday? What will I do today? Are there any blockers? According to the PMI Agile Practice Guide (Section 5.3: Daily Stand-ups) and Scrum Guide, in-depth discussions should be taken offline to avoid disrupting the stand-up’s purpose.

Option A is correct: deferring detailed conversations maintains stand-up focus.

Option B may derail the time-boxed meeting.

Option C overreacts and undermines team self-management.

Option D might be appropriate later but not during the stand-up.

In this case, the risk description for " Incomplete requirements specification " has been identified as a high likelihood and high impact risk. To mitigate this, the most appropriate strategy would be to conduct thorough requirements analysis and validation. This ensures that the integration of the new tool with the customer relationship management system aligns with the business objectives and avoids misunderstandings or gaps in the product requirements, which could cause delays or rework later in the project. This step addresses the core challenge of ensuring the product meets the business needs and integrates smoothly with existing systems.

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.

After the product vision is communicated, the product owner should ensure that the product backlog is prioritized so the team can focus on delivering the most valuable features first. According to the PMI Agile Practice Guide (Section 5.1 Product Backlog and Vision Alignment), prioritizing the backlog helps teams understand the product roadmap and plan their efforts accordingly.

Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) reinforces that the product owner’s key responsibility is backlog prioritization, not task management or detailed design.

Option C is correct: prioritizing the backlog enables the team to understand and plan the roadmap.

Option A and B are too detailed for the product owner and move into the team ' s domain.

Option D is a team responsibility, not the product owner’s.

The correct answer is C – Share information via interactive methods such as a brainstorming session.

Agile promotes collaboration, continuous stakeholder engagement, and open communication. When a stakeholder lacks understanding, the practitioner should use interactive techniques like brainstorming, user story workshops, or product visioning sessions. These methods foster transparency, build trust, and allow stakeholders to co-create the product vision.

From the PMI Agile Practice Guide:

“Effective stakeholder engagement relies on interactive communication methods such as workshops, demos, and feedback sessions to ensure alignment and transparency.”

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

Mike Griffiths notes:

“Interactive, face-to-face collaboration provides the richest communication. Agile favors dialogue over documentation to enhance shared understanding.”

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

Why the other options are less ideal:

A (status emails) are passive and limited in effectiveness.

B may violate Scrum guidelines—daily standups are not intended for stakeholders.

D delays engagement and limits collaboration to after-the-fact review.

Answer: C

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