Scrum Master role in a nutshell - basic interactions, outputs and facilitation skills

1. Scrum Master
in a really small practical nutshell
Cátia Oliveira - Scrumplicity.net 1

2. The usual suspects
• Scrum Team = PO+SM+Dev Team
• Dev Team = Cross Functional Team
• Stakeholders = everyone else out of Scrum
Team
PO- Product Owner , SM- Scrum Master
Cátia Oliveira - Scrumplicity.net 2

3. Scrum Master Role
- Scrum Guide
• Responsible for ensuring Scrum is understood and
enacted.
– Scrum Masters do this by ensuring that the Scrum Team
adheres to Scrum theory, practices, and rules.
• The Scrum Master is a servant-leader for the Scrum
Team.
• The Scrum Master helps those outside the Scrum Team
understand which of their interactions with the Scrum
Team are helpful and which aren’t.
• The Scrum Master helps everyone change these
interactions to maximize the value created by the
Scrum Team.
Cátia Oliveira - Scrumplicity.net 3

4. SM service to the Product Owner
- Scrum Guide
• Finding techniques for effective Product Backlog
management;
• Clearly communicating vision, goals, and Product
Backlog items to the Development Team;
• Teaching the Scrum Team to create clear and
concise Product Backlog items;
• Understanding long-term product planning in an
empirical environment;
• Understanding and practicing agility; and,
• Facilitating Scrum events as requested or
needed.
Cátia Oliveira - Scrumplicity.net 4

5. SM Service to the Development Team
- Scrum Guide
• The Scrum Master serves the Development Team in
several ways, including:
– Coaching the Development Team in self-organization and
cross-functionality;
– Teaching and leading the Development Team to create high-value
products;
– Removing impediments to the Development Team’s
progress;
– Facilitating Scrum events as requested or needed; and,
– Coaching the Development Team in organizational
environments in which Scrum is not yet fully adopted and
understood.
Cátia Oliveira - Scrumplicity.net 5

6. SM service to the Organization
- Scrum Guide
• Leading and coaching the organization in its Scrum
adoption;
• Planning Scrum implementations within the
organization;
• Helping employees and stakeholders understand and
enact Scrum and empirical product development;
• Causing change that increases the productivity of the
Scrum Team; and,
• Working with other Scrum Masters to increase the
effectiveness of the application of Scrum in the
organization.
Cátia Oliveira - Scrumplicity.net 6

7. Events & Artifacts
• Sprint Planning
• Daily Stand up
• PB Refinement
• Sprint Demo
• Retrospective
PB- Product Backlog
• Product Backlog
• Product Burndown
• Sprint Backlog
• Sprint Burndown
• Team Metrics
Cátia Oliveira - Scrumplicity.net 7

8. Scrum Framework
Cátia Oliveira - Scrumplicity.net 8

9. Sprint Planning – Part 1
PART 1 - Know what’s next
- Set Time and Space
- Are Items Ready for Planning? (DoR)
- Facilitate Session
- Keeping Timebox
- Ensure Team knows what’s next to do
- Review Definition of Done (DoD)
- Clear out the Acceptance criteria
- Agree the Sprint Goal
DoR- Definition of Ready
For Scrum Team
Cátia Oliveira - Scrumplicity.net 9

10. Sprint Planning – Part 2
For Dev Team
PART 2 - Plan & Commit
- Set Time and Space
- Keep Timebox
- Help breaking Items into manageable tasks (< 1 working day)
- Facilitate Decisions & Commitments
- Facilitate Estimation technique
- Help building Sprint Backlog & the Burndown for the sprint
- Ask questions: set the tone for brainstorm and explore
different perspectives
Cátia Oliveira - Scrumplicity.net 10

11. Daily Scrum
For Scrum Team
• Explain why Daily Scrum is Important (review, sync,
plan, transparency)
• Daily Scrum is for the Scrum Team
• Help team choosing time & place
• Help team keeping timebox
• Help team improving synchronization and planning
• Help team updating Sprint Backlog and Burndown
• Help team do the daily for them, not for you or anyone
else but them
Cátia Oliveira - Scrumplicity.net 11

12. Product Backlog Refinement
For Scrum Team
• Set Time and Space
• Explain Purpose of PB Refinement
• Help PO preparing (him to decide which Items will be
refined)
• Help Scrum Team improve communication (hint –
use Specification by example)
• Help Dev team choosing Reference User Story
• Help Dev Team using Planning Poker to estimate
remaining US
• Help PO organizing and improving PB
PB- Product backlog PO- Product Owner
Cátia Oliveira - Scrumplicity.net 12

13. Sprint DEMO
• Set Time and Space
• Revisit Sprint Goal
• Facilitate session
• Keep time box and focus on Done
For everyone !
Cátia Oliveira - Scrumplicity.net 13

14. Team Metrics
• Burndown Chart
• Velocity
• Metrics helping the team to improve
( by showing where the waste is, or making
quality, Technical debt values transparent..)
• Example :
– Efficiency ratio = Sum of all Value Adding tasks/Sum of ALL tasks
– Correction Demand = (tasks or stories related to correction) /All of The Demand (Value and
Correction)
Cátia Oliveira - Scrumplicity.net 14

15. What’s your career Path
• Learn
• Read
• Practice
• Collaborate with other SM’s
• Join groups/ conversations/ meetups
• Discuss, contribute
• Dare to disagree
Cátia Oliveira - Scrumplicity.net 15

16. And this, it’s just the beginning, the basic of your
Scrum Master career.
If you are not doing these things, you are
something else, not a Scrum Master.
Cátia Oliveira - Scrumplicity.net 16

17. Now go and make some magic!
Cátia Oliveira - Scrumplicity.net 17