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.

The correct answer is C - The team should have conducted more demonstrations with the product owner during the iteration.
Continuous feedback is essential in Agile. Regular product demos or interim check-ins during the sprint (not just at the end) allow the product owner to validate progress and course-correct early. This ensures that expectations are aligned and surprises are avoided at the sprint review.
PMI Agile Practice Guide:
"Stakeholder feedback should be gathered continuously throughout the sprint. Regular engagement and interim demos reduce the risk of misalignment at iteration end." (PMI Agile Practice Guide, Section 5.7 - Reviews and Demos) Mike Griffiths:
"Waiting until the sprint review to validate features with the product owner increases risk. Frequent collaboration and demonstrations ensure the work remains on target." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A is helpful but doesn't guarantee alignment.
* B is testing-focused and misses early collaboration.
* D places all responsibility on the product owner, ignoring shared ownership.

The correct answer is B - Lack of shared knowledge of user stories.
Distributed teams face challenges in collaboration, knowledge sharing, and communication. Without regular interaction, team members may not fully understand user stories, acceptance criteria, or customer needs. This leads to misalignment and potentially lower-quality outputs.
From the PMI Agile Practice Guide:
"Distributed teams face barriers to communication and knowledge sharing. Agile teams must use collaboration tools and practices to ensure that all members share an understanding of the user stories and priorities." (PMI Agile Practice Guide, Section 2.3 - Agile Team Communication) Mike Griffiths explains:
"Remote Agile teams must work harder to ensure clarity in user stories and maintain shared understanding.
Without this, misunderstandings increase."
(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance)
Other options:
* A (frequent integration) is a benefit, not a risk.
* C is irrelevant to Agile effectiveness.
* D is less common with Agile roles clearly defined (PO, SM, Dev Team).

Capturing and reviewing lessons learned is a vital practice in both agile and traditional environments.
According to the PMI Agile Practice Guide (Section 5.6: Retrospectives) and PMBOK Guide (Lessons Learned Register), continuous learning from project execution helps teams and organizations improve predictability, quality, and efficiency.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) highlights the importance of documenting insights and feeding them into future projects for organizational maturity.
* Option A is correct: creating and reviewing a lessons learned repository supports organizational learning and better delivery.
* Option B confuses issue tracking with structured learning.
* Option C removes responsibility from the team-agile encourages team ownership of improvement.
* Option D is helpful in some contexts but is not a repeatable organizational improvement tool like a lessons learned repository.