The scrum master should first remind the team of the purpose and goals of each scrum event (such as the daily standup, sprint planning, sprint review, and retrospective) to ensure that they remain focused on their intended outcomes. The scrum master can then implement a policy that ensures discussions that deviate from the scope of the event are stopped. This approach keeps the team on track, prevents time-wasting conversations, and helps maintain the efficiency of the events.
This method empowers the team to stay focused on what is essential for each event and encourages self- management while still providing room for relevant discussions. In doing so, the team can achieve the desired outcomes of each scrum event without unnecessary delays.

The correct answer is B - Ensure there is a balanced mix of people who are experts and members with broad experience based on the work to be performed and determine training needs.
Scrum encourages cross-functional, self-organizing teams with complementary skills. Building a balanced team that reflects both depth and breadth of experience ensures optimal delivery while enabling team learning.
From PMI Agile Practice Guide:
"Agile teams are cross-functional. The team may need T-shaped skills-members with deep expertise in one area and a willingness to broaden knowledge in other areas. Creating balanced teams with knowledge diversity leads to better collaboration and learning." (PMI Agile Practice Guide, Section 4.1 - Building Agile Teams) Mike Griffiths adds:
"Team selection should prioritize diversity of skill sets and the ability to collaborate, not just performance history. The goal is a team that can deliver value collectively, not as individuals." (Mike Griffiths, Chapter 4 - Team Performance) Why the other options are not suitable:
* A may reduce team diversity and discourage healthy conflict resolution.
* C may not be feasible in distributed environments and is not a strict requirement.
* D focuses on individual velocity contributions, which contradicts Agile's team-based delivery focus.

The correct answer is D because organizational transformation to agile requires more than process changes- it requires a shift in mindset. Training teams on agile values and principles builds a shared foundation and helps foster commitment to agile ways of working.
From PMI Agile Practice Guide:
"Agile transformation requires attention to both practices and mindset. Leaders must help teams embrace agile values, empower decision-making, and promote an agile culture through education and active support." (PMI Agile Practice Guide, Section 2.1 - Organizational Change and Transformation) From PMBOK Guide - 7th Edition:
"Successful transformation begins with people understanding the why and how of agile. Change cannot happen effectively without adequate training and communication." (PMBOK Guide 7th Ed., Principle 1 - Be a Diligent, Respectful, and Caring Steward) From Mike Griffiths' PMI-ACP Exam Prep Book:
"Agile success is rooted in the team's understanding of core principles. Agile leaders must invest in developing a strong foundational mindset, as well as practices. Education is a critical enabler of sustainable agile adoption." (Mike Griffiths, Chapter 1 - Agile Principles and Mindset) Option A is a partial strategy but doesn't ensure cultural transformation.
Option B is necessary but not sufficient-buy-in alone won't change behavior.
Option C is tactical and useful but doesn't address team-wide mindset change.

A value stream map is an effective tool for identifying and visualizing the flow of work and the associated delays or handoffs in a process. By mapping out the entire value stream, the team can identify inefficiencies, waste, and bottlenecks, which helps them target areas for improvement. This allows the team to optimize the workflow by reducing unnecessary handovers and delays, which is in line with their goal of improving efficiency.

The correct answer is C - Schedule a story grooming session with the product owner before sprint planning.
Story grooming (backlog refinement) ensures that stories are ready, appropriately detailed, and understood before planning.
From the PMI Agile Practice Guide:
"Backlog refinement sessions are a key practice where the team, facilitated by the Scrum Master, ensures that backlog items are well-defined and sized appropriately for future planning. These sessions reduce ambiguity and promote shared understanding." (PMI Agile Practice Guide, Section 5.3 - Backlog Refinement) Mike Griffiths adds:
"Backlog refinement allows stories to be clarified, split, and estimated ahead of planning. Agile practitioners ensure backlog items meet the Definition of Ready (DoR) before sprint planning." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning) Incorrect options:
* A delays collaboration and is too passive.
* B lacks product owner involvement.
* D is a sizing technique, not a requirement clarification method.