To understand the needs of different user types, agile teams use personas and extreme characters to represent a range of users, including edge cases. According to the PMI Agile Practice Guide (Section 5.2: Requirements and Personas) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), personas help teams build empathy and ensure that stories reflect actual user roles-not just generic assumptions.
* Option D is correct: personas and extreme characters ensure inclusive and realistic story coverage.
* Option A and B focus on communication and sequencing but not user diversity.
* Option C (process flows) is more technical and doesn't solve the misalignment with user perspectives.

The correct answer is 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.

The correct answer is A - Facilitate team agreement on the definition of done (DoD) during the chartering process.
The "Definition of Done" is a shared understanding among the team of what it means for work to be considered complete. Disputes over whether a deliverable is done usually arise due to the lack of a clearly defined and agreed-upon DoD.
From the PMI Agile Practice Guide:
"Teams should define and agree on the Definition of Done (DoD) early. This shared understanding reduces ambiguity and misalignment over when a task is complete." (PMI Agile Practice Guide, Section 5.2 - Definition of Done and Acceptance Criteria) Mike Griffiths emphasizes:
"The Definition of Done provides clarity, especially in multi-functional teams. It avoids misunderstandings and disputes about work completeness." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why other options fall short:
* B refers to a team formation stage but doesn't address the root cause of conflict.
* C and D help improve backlog clarity but don't resolve issues around completion criteria.

The best answer is A because an agile practitioner should first facilitate collaboration, uncover the root causes of disagreement, and help the teams align around a shared outcome. The issue is not simply the absence of targets or KPIs; it is a cross-functional conflict involving cost, compliance, product choices, and sustainability commitments. PMI-ACP topics emphasize collaboration, stakeholder engagement, shared vision, systems thinking, and conflict facilitation.
Option B is too directive and may increase resistance because it forces compliance without resolving the underlying concerns. Option C centralizes the decision with executives, which reduces team collaboration and does not reflect agile servant leadership. Option D may be useful later, but KPIs alone will not resolve the tension or rebuild alignment. The agile practitioner should promote a collaborative approach to solving conflict and ensure common understanding of purpose and vision.
=========

The correct answer is A - Conduct a requirements gathering workshop.
In Agile, workshops such as story-writing or backlog refinement sessions help the team and stakeholders collaboratively explore requirements. These sessions are interactive and iterative and allow for joint discovery, prioritization, and clarification of user needs.
PMI Agile Practice Guide:
"Collaborative workshops enable teams to gather requirements and clarify expectations in an iterative fashion.
They engage stakeholders in prioritizing and decomposing work into user stories." (PMI Agile Practice Guide, Section 5.2 - Backlog Refinement) Mike Griffiths writes:
"Workshops are a key practice for backlog development. They are particularly useful when initiating complex projects with minimal requirements, allowing the team to iteratively develop stories with stakeholders." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* B assumes delivery before refinement, risking misalignment.
* C places the burden on the product owner alone.
* D is waterfall-oriented and contradicts iterative backlog evolution.