Scrum Master ensures the event happens but doesn't control how it happens - that's up to the developers. It lines up with Servant Leadership, supports team self-management while ensures the event occurs, focuses on enabling rather than controlling, maintains Scrum Framework without overstepping, and allows developers to own how they conduct the event.

Scrum Guide Reference:

"The Scrum Master ensures that the Developers have the meeting, but the Developers are responsible for conducting it."

Key Responsibilities:

1. Developers Own the Daily Scrum
   • They organize and run the meeting (typically timeboxed to 15 minutes).
   • They use it to inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
   • The format (e.g., "Three Questions," walking the board) is up to the Developers.
2. Scrum Master’s Duty
   • Ensures the Event Happens: The Scrum Master makes sure the Developers hold the Daily Scrum, but they do not need to attend unless actively participating as a Developer (e.g., in a small team).
   • Coaches Effectiveness: If the meeting becomes status-reporting or dysfunctional, the Scrum Master intervenes to reinforce its purpose (e.g., "Are we aligning on the Sprint Goal?").
   • Removes Impediments: If external parties disrupt the Daily Scrum, the Scrum Master shields the team.

The Sprint Goal defines the intended outcome or objective of a Sprint.

During Sprint Planning, the Scrum Team collaboratively creates this goal after the Developers forecasts which Product Backlog items it can deliver in the upcoming Sprint.