Correct Answer:

A distant Product Owner represents arisk to value delivery, transparency, and empiricism. While the Product Owner has provided a Product Backlog for the Sprint, lack of collaboration during the Sprint undermines learning and informed decision-making. As a Scrum Master, the focus should be oncoaching, enabling collaboration, and addressing systemic impediments, not substituting for the Product Owner.
1. Make the Impact Transparent
The Scrum Master should help make the impact of the Product Owner's absencevisible:
* Reduced ability to clarify Product Backlog Items,
* Slower decision-making when discoveries occur,
* Increased risk to the Sprint Goal and product value.
This transparency should be established through respectful conversations with the Product Owner and, if needed, through Scrum events such as the Sprint Retrospective.
2. Coach the Product Owner on Accountability
The Scrum Guide states that the Product Owner is accountable formaximizing valueandProduct Backlog management, which requires ongoing collaboration with Developers. The Scrum Master should coach the Product Owner to understand that handing over a backlog at Sprint Planning isnot sufficientand that availability during the Sprint is essential for empiricism.
3. Enable Better Collaboration Without Replacing the Product Owner
The Scrum Master should help create opportunities for collaboration, such as:
* Encouraging regular clarification moments during the Sprint,
* Improving Product Backlog refinement so fewer questions remain unanswered,
* Helping Developers prepare focused questions to use limited Product Owner availability effectively.
However, the Scrum Master mustnot take over Product Owner responsibilities, as this would blur accountabilities.
4. Address Organizational Causes
If the Product Owner's distance is due to workload, role confusion, or organizational pressure, this becomes an organizational impediment. The Scrum Master should raise this issue with leadership and help the organization understand the risk of an unavailable Product Owner to product outcomes.

Correct Answer:

The situation described directly touches on several coreScrum Values, which guide behavior and collaboration within Scrum Teams. In particular, the values ofCourage, Respect, and Opennessare most prominently involved.
First, the value ofCourageis demonstrated by the junior developer. Speaking up about feeling unheard, especially in front of more experienced colleagues, requires personal courage. Scrum encourages team members to be brave in raising difficult or uncomfortable issues so that problems can be addressed rather than ignored. Without courage, important impediments to collaboration and effectiveness would remain hidden.
Second, the situation highlights a lack ofRespectin team interactions. Scrum emphasizes that Scrum Team members respect each other as capable, independent individuals. Interrupting a colleague or disregarding their input-regardless of seniority-undermines this value. Respect is essential for effective collaboration and for creating an environment where all team members can contribute fully.
Third, the value ofOpennessis central to this scenario. Scrum Teams are expected to be open about challenges, feedback, and differing perspectives. Openness also means being receptive to ideas from all team members, independent of role, experience level, or background. Disregarding input from a junior developer contradicts Scrum's emphasis on openness and reduces the quality of decision-making.

Correct Answer:

When Developers raise the lack of certain knowledge or expertise as an impediment, the Scrum Master must address the situation in a way that reinforcesScrum principles, especiallycross-functionality, empiricism, and self-management, while also supporting value delivery.
First, it is essential to verify whether this is truly animpediment. In Scrum, an impediment is something the team cannot resolve on its own. As a Scrum Master, I would facilitate a discussion with the Developers and, if appropriate, the Product Owner to inspect whether the expertise is genuinely required to achieve the desired outcome. In some cases, the scope or approach can be adapted, or the Product Backlog Item can be refined so that alternative solutions are viable. This conversation may reveal that the need for specialized knowledge is less critical than initially assumed.
Second, if the expertise is indeed necessary, the Scrum Master should encourage the team to address the issue as across-functional Scrum Team. Scrum expects teams to have, or acquire, all skills needed to deliver value. Therefore, I would ask the Developers how they couldlearn or acquire the necessary knowledge themselves. Possible options include allocating time for learning, research, training, experimenting, or building a prototype. These activities can be planned as part of the Sprint Backlog and support long-term team capability.
Third, the Scrum Master can help the team make effective use ofoutside expertise without undermining self- management. During Sprint Planning or refinement, the team may consult internal or external experts to gain insights, validate approaches, or reduce uncertainty, while still retaining ownership of the work and the Sprint Backlog.
Finally, if none of these options resolve the impediment, the Scrum Master has a responsibility tohelp the organization support the Scrum Team. This may involve facilitating access to expertise from elsewhere in the organization or, if necessary, from outside the organization. The Scrum Master does not solve the problem personally but works to remove organizational barriers so the team can proceed.

Correct Answer:

When a Development Team is distributed across different physical locations and faces logistical overhead just to start theDaily Scrum, this situation represents animpediment to effective inspection and adaptation. As a Scrum Master, the appropriate action is toenable the team to inspect and adapt more effectively, not to control or manage logistics on their behalf.
1. Help the Team Establish a Stable and Simple Daily Scrum Setup
The Scrum Master should work with the Development Team toinspect and improve how the Daily Scrum is conducted. This may include:
* Agreeing on afixed time and virtual location,
* Standardizing tools (e.g., always the same conferencing solution),
* Reducing setup effort so the event can start on time and remain within its 15-minute timebox.
This supports transparency and reduces unnecessary waste.
2. Remove or Reduce Organizational and Technical Impediments
If logistical difficulties stem from organizational constraints-such as lack of proper tooling, inadequate rooms, or unreliable communication infrastructure-the Scrum Master shouldaddress these as impediments.
This may involve working with IT or management to provide stable tools that enable smooth collaboration.
3. Coach the Team Toward Self-Management
Rather than running the Daily Scrum or handling logistics personally, the Scrum Master shouldcoach the Developers to self-managehow they organize the event. The goal is for the team to own and continuously improve the Daily Scrum in a way that fits their distributed context.