This document provides an overview of Scrum and its key aspects. It describes the Scrum framework, including roles like the Product Owner, Scrum Master, and self-organizing cross-functional Team. It outlines the core Scrum meetings like Sprint Planning, Daily Stand-up, Sprint Review and Retrospective. It also discusses Scrum artifacts like the Product Backlog, Sprint Backlog and Product Increment. The document emphasizes that Scrum is for product development, breaking problems into smaller pieces, and improving through inspection and adaptation in short cycles.

1. Scrum Masterclass
Summer of Tech 2015
@antboobier
anthony@nomad8.com
Ant Boobier

3. Version One agile survey 2012

4. New, new product development teams

5. Scrum Framework

6. Empiricism
Karen Greaves and Samantha Laing

7. Scrum’s 3-5-3 formation

8. Commitment
Potentially Shippable
2 - 4Weeks
No Changes
(In Duration or Deliverables)
Scrum framework

9. Roles

10. Product Owner
Stakeholder
management Makes sure business
benefits delivered
Translates the vision
into a Product Backlog
Accepts or rejects the work
Prioritises features
and adjusts scope
Responsible for
reporting, tracking
and forecasting

11. Building the Right thing

12. Scrum Master
Helps resolve impediments
Facilitates Scrum meetings
Ensures that the
process is followed
Shields the team from
external interferences
Enables close co-
operation across all roles
and functions and
removes barriers
Ensures that the team
is fully functional and
productive

13. Cultivating a great team

14. The Team
Own quality and
ensures they build “the
thing Right”
Succeeds or fails together
cross-functional
Self- Organised
(organise themselves
and their work within
the Sprint)
Direct contact
with users and
stakeholders
autonomous
Co-located

15. Building the thing Right
7 +/- 2!

16. Meetings

17. 1. What 2. How
Sprint Planning
Team Commitment
When?
Duration?
Who?
Start of Sprint
@ 2 hours
SM, Team, PO
(for part 1)
• How will the chosen work
get done?
• Design, Solutioning
• Plan Tasks
• Agree Sprint Backlog
• What can be done in this
Sprint?
• Sprint Goal
• Select Product Backlog
items

18. Daily Stand Up
1. What did I do yesterday?
2. What will I do today? 3. Do I see any issues?
to help achieve the Sprint Goal…
When?
daily, same time
Duration?
15 mins
Team, SM, PO
Who?

19. • Only show working tested software
• Update on progress and release
• Feedback
Product
When?
duration?
who?
end of Sprint
@ 1 hour
people who
have feedback
SM, PO, Team
Review

20. Process
When?
duration?
who?
after Review
@ 1 hour
SM, Team,
Retrospective
• Continuous improvement
• Inspect how are we working as a
team
• Agree on 1 - 2 actions that team
can implement to improve the way
they work

21. Artefacts

22. Jeff Patton, Agile and Asteroids champion

23. Product Backlog
1 - 2 Sprints
Sprints 3 - 6
Sprints 7 - x
Small and defined items
Prioritised
ordered list of everything that might be needed in the product

24. Sprint Backlog
makes visible all of the work that the Development Team
identifies as necessary to meet the Sprint Goal.

25. Product Increment
Working tested
software
Ready to ship
Definition
of Done

26. Scrum is…
• Product development
• A cross-functional team that succeeds and fails together
• Breaking big problems into smaller ones
• Inspecting and adapting through short feedback loops
• Transparency and visibility of progress
• Improving over time

27. Snowflakes exercise

28. Score card

29. Recommended next steps:
• Watch Agile Product Ownership in a
nutshell video, by Henrik Kniberg
• Watch Spotify Engineering culture
parts 1 and 2
• Read more on our blog at
nomad8.com
…be agile!

30. Twitter it !
#SoT2015
@antboobier
@summeroftech
#SoT2015

31. @antboobier
anthony@nomad8.com