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.

A psychologically safe environment is essential for a productive retrospective, especially in the presence of team conflict. The PMI Agile Practice Guide (Section 5.6 Retrospectives) recommends reviewing working agreements or ground rules to remind the team of respectful behavior and to promote openness. This helps reset expectations and encourages participation without fear of judgment.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) emphasizes that retrospectives are about trust and transparency, and setting the tone properly enables team learning and resolution.
* Option A is correct: reviewing ground rules reinforces team norms and supports safety.
* Option B may make individuals feel singled out.
* Option C ignores the interpersonal issue and postpones resolution.
* Option D escalates unnecessarily and bypasses team ownership.

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.

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.

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