Scrum101
36
Scrum – 101 Gal Zellermayer
Transcript of Scrum101
Scrum – 101Gal Zellermayer
WIIFM
What’s In It For Me?
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
Who am I?http://galzellermayer.blogspot.com/
http://il.linkedin.com/in/galzellermayer@g_zelly
AgileWe are uncovering better ways of developingsoftware by doing it and helping others do it.
Through this work we have come to value:
The Agile ManifestoIndividuals 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
Scrum
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)
Why Scrum is (almost) THE BEST
• Predictable• Visible• Quality• Dynamic• Inspect and Adopt
Scrum Basic Building Blocks
• Sprint• Story• Backlog
Scrum Process
The Login Page Example
The Login Page Example
How does it work?
3 Roles:• Product Owner • Team• Scrum Master
4 Ceremonies• Planning• Dailies• Demo• Retrospective
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
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
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
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.
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?
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
DONE
is
DONE
is
DONE
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?
Why Scrum is (almost) THE BEST
• Predictable• Visible• Quality• Dynamic• Inspect and Adopt
How to Start?
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
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?
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
Who is the Team?
• 2-9 people
• Includes all necessary functions to complete sprint goals
What Have We Not Covered (in English)?• INVEST• Estimation & Story Points• Burn-down charts
What Have We Not Covered (in Japanese)?• Kabnan• Kaizen• Gemba
Q&A
![[JWAP-2] DI & Spring](https://static.fdocuments.us/doc/165x107/53fd90328d7f72a81c8b4981/jwap-2-di-spring.jpg)
