This document provides an overview of Scrum, an agile framework for managing product development. It discusses the Scrum roles of Product Owner, Team, and Scrum Master. The key Scrum ceremonies are planning, daily stand-ups, sprint reviews, and retrospectives. Scrum uses short iterations called sprints to incrementally deliver working software. The document recommends starting with a short initial sprint length and identifying the Product Owner, Scrum Master, and cross-functional Team.

1. Scrum – 101
Gal Zellermayer

2. WIIFM
What’s In It For Me?

3. Agenda
Who am I? The old world Agile
•The agile
manifesto
Scrum
•Basic
Concepts
•Roles
•Ceremonies
What did we
not cover?
•English
•Japanese
How to start? Q&A

4. GAL ZELLERMAYER
gal.zellermayer@gmail.com
@g_zelly
R&D manager @ vmware
Scrum Master, Team Leader, Group
Manager

7. Agile
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

8. The Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
http://agilemanifesto.org/principles.html

9. Scrum

11. Scrum in a Nutshell
“Scrum is an iterative and incremental agile software
development framework for managing product development”
http://en.wikipedia.org/wiki/Scrum_(software_development)

12. Why Scrum is (almost) THE BEST
• Predictable
• Visible
• Quality
• Dynamic
• Inspect and Adopt

13. Scrum Basic Building Blocks
• Sprint
• Story
• Backlog

14. Scrum Process

15. The Login Page Example
The Login Page Example

16. How does it work?
3 Roles:
• Product Owner
• Team
• Scrum Master
4 Ceremonies
• Planning
• Dailies
• Demo
• Retrospective

17. Accountable for
ensuring that the
team delivers value
to the business
Estimates the work
that can be done in
a sprint
Decides how many
work can be
accomplished in a
version
Creates and
maintains a
prioritized backlog
of user stories
The Product Owner
Accountable for
ensuring that the
team delivers value
to the business
Estimates the work
that can be done in
a sprint
Decides how many
work can be
accomplished in a
version
Creates and
maintains a
prioritized backlog
of user stories

18. Deliver high
quality product
Prioritize the work Test the product
Estimate the work
Commit to the
amount of work
that can be done
in a sprint/version
The Team
Deliver high
quality product
Prioritize the work Test the product
Estimate the work
Commit to the
amount of work
that can be done
in a sprint/version

19. Remove impediments
Micro managing the
team members work
Removing the barriers
between the
development Team and
the Product Owner
Teach the Product
Owner how to maximize
return on investment
(ROI)
Keep information about
the Team’s progress up
to date and visible to all
parties
The Scrum Master
Remove impediments
Micro managing the
team members work
Removing the barriers
between the
development Team and
the Product Owner
Teach the Product
Owner how to maximize
return on investment
(ROI)
Keep information about
the Team’s progress up
to date and visible to all
parties

20. Planning
• Duration: < 1 hour
• When? First day of the sprint
• Who? The team and the PO
• Goal: Team plans sprint, estimates work, commit to the content.
• Verify goal: After the planning each team member has work to do; PO
can plan next sprint.

21. Daily
• Duration: <15 minutes
• Who? The team (PO is optional)
• How? Standup meeting
• When? Every day
• 3 questions:
• What Have I done yesterday?
• What am I doing today?
• What are my impediments?

22. Demo / Sprint Review
• Duration: <1 hour
• Who? All
• When? Last day of the sprint
• What?
• Team demonstrates their work in the last sprint
• Only DONE stories are shown
• The PO gives feedback to the team

23. DONE
is
DONE
is
DONE

24. Retrospective
• Duration: <1 hour
• Who? Just the team
• When? Last day of the sprint (after the demo)
• 3 questions:
• What have we done well?
• What should we improve?
• How do we improve?

25. Why Scrum is (almost) THE BEST
• Predictable
• Visible
• Quality
• Dynamic
• Inspect and Adopt

26. How to Start?

27. Decide Sprint Length
• Short sprints (1-2 weeks):
• More agile
• More room for inspect and adopt
• Long sprints:
• Easier for PO
• Easier to adopt
• More like the old world

28. Who is the PO?
• Create the backlog
• Focus on this sprint
• What do you want to achieve?
• Break it to stories
• Prioritize it
• Put it on sticky notes
• Check out what INVESTmeans?

29. Who is the Scrum
Master?
• Schedule the planning for Sunday
• Schedule a daily standup meeting
• Schedule the demo and the retrospective
• Make sure sprint backlog is ready
• Prepare a scrum board and notes

32. Who is the Team?
• 2-9 people
• Includes all necessary
functions to complete sprint
goals

33. What Have We Not Covered (in English)?
• INVEST
• Estimation & Story Points
• Burn-down charts

34. What Have We Not Covered (in Japanese)?
• Kabnan
• Kaizen
• Gemba

36. WABI SABI
gal.zellermayer@gmail.com
@g_zelly
http://galzellermayer.blogspot.com/