The core principle at play is self-management. The Scrum Guide mandates that Scrum Teams are self-managing, meaning they determine how to best accomplish their work. The logistical arrangements for the Daily Scrum, an event owned by the Developers, fall squarely within this domain. The Scrum Master's role is to be a servant-leader who coaches the team in self-management and Scrum principles. Intervening by providing a solution or escalating the issue would undermine the team's autonomy and accountability. The most appropriate action is to empower the Developers to identify and implement their own solution, thereby strengthening their self-management capabilities.

B. Ask the Developers to alternate who is responsible for meeting setup.

This is a prescriptive solution. The Scrum Master should not dictate how the team solves its problems, as this undermines their self-management and ownership.

C. Set up the meeting and tell the Scrum Team that is how it will be done.

This is a command-and-control anti-pattern. It removes responsibility from the team and positions the Scrum Master as an administrator or manager, which contradicts their true role.

D. Inform management and ask them to solve it.

This is an inappropriate escalation. The team is fully capable of resolving this internal logistical issue. Escalating it disempowers the team and misrepresents the issue as an impediment they cannot solve.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Page 5

"Scrum Team" section: "Scrum Teams are self-managing

meaning they internally decide who does what

when

and how." This directly supports allowing the team to solve their own logistical problems.

Page 7

"Scrum Master" section: "The Scrum Master serves the Scrum Team in several ways

including: Coaching the team members in self-management and cross-functionality;" This defines the Scrum Master's coaching role rather than a directive one.

Page 9

"Daily Scrum" section: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team." This establishes the Developers' ownership of the event and

by extension

its logistics.