Scrum Master Essentials

How Scrum is built · Product Goal, Sprint Goal and Definition of Done · empirical process control · why short Sprints cut risk · the servant leader

1. Scrum on one page: accountabilities, events and artifacts
2. Three commitments: Product Goal, Sprint Goal, Definition of Done
3. Following one feature through a Sprint
4. Empirical process control: see, check, adjust
5. Short Sprints versus long plan-driven phases
6. Case: finding a wrong turn early, not late
7. The Scrum Master as a servant leader
8. Scrum Master, project manager and team lead compared
9. A day in the life of a Scrum Master

Accountabilities · supporting the Product Owner · protecting Sprint focus · working agreements · confidentiality and neutrality

1. Accountabilities: who owns what in a Scrum Team
2. Helping the Product Owner keep the backlog transparent
3. Protecting focus: handling interruptions during the Sprint
4. Why teams need working agreements
5. A workshop to draft a working agreement
6. Example: a team agreement on one page
7. Neutrality: directing the process, not the work
8. Keeping team conversations confidential
9. Case: the manager asks what the team said

Backlog refinement · sizing and splitting items · Sprint Goal · Definition of Done · Sprint Backlog · Scrum board in Jira or on a wall

1. Backlog refinement: what it is and why it matters
2. Running a refinement session: clarify, size, split
3. Example: splitting one large story into small ones
4. Sprint Goal and Definition of Done explained
5. Writing a Sprint Goal and a Definition of Done together
6. Example: turning a vague goal into a clear one
7. The Sprint Backlog and the Scrum board explained
8. Setting up a board in Jira or on a wall
9. Keeping the board current: a daily habit

Time-boxing · agenda templates · preparation checklist · the four main events · facilitation skills · a first Retrospective

1. Time-boxing: why every event has a limit
2. Agenda templates and a preparation checklist
3. Opening, running and closing an event in person or remotely
4. The purpose of the four main Scrum events
5. Facilitation skills: questions, pauses and focus
6. Walk-through: one Sprint, four events, one facilitator
7. Why Retrospectives matter
8. Running Start-Stop-Continue step by step
9. From findings to one or two tracked improvement actions

Scrum values · coaching the team · impediments and escalation · impediment board · team health check · radar chart

1. The five Scrum values and what they mean
2. Linking roles, events and artifacts to the values
3. Coaching in practice: a team that avoids hard topics
4. What an impediment is and why it must be visible
5. Building an impediment board and tracking it
6. Escalating what the team cannot resolve
7. Why look at how a team feels
8. Running a health check: survey and radar chart
9. From the chart to an improvement conversation

Anti-patterns · first responses · Daily Stand-up case · Sprint Goal at risk · renegotiating scope · personal learning plan

1. Anti-patterns: what they are and why they appear
2. Choosing a first response to an anti-pattern
3. Example: new scope arrives in the middle of a Sprint
4. The purpose of the Daily Stand-up
5. Case study: the Stand-up that became a status report
6. Restoring the purpose: a plan for the Scrum Master
7. When a Sprint Goal is at risk
8. Renegotiating scope without extending the Sprint
9. Example: a Sprint hit by a late technical problem
10. The advanced skills ahead
11. Assessing your own strengths and gaps
12. Example: a learning plan for a new Scrum Master