The document provides an introduction to the Scrum framework for agile software development. It outlines the key aspects of Scrum including artifacts like product and sprint backlogs, roles like the product owner and scrum master, ceremonies like sprint planning and daily standups, and metrics like velocity and burn down charts. The document emphasizes that Scrum is not a methodology but a framework that helps optimize progress through continuous adaptation using self-organizing teams.

1. Introduction to Scrum
Scrum Forum Team

2. Manifesto for Agile Software Development
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham,
Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick
• 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.
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

3. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropiate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

4. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropiate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

5. Scope
• What this is about
– Conceptual understanding of Scrum
– Understanding of the overall Scrum process
– Understand how the essential Scrum roles work together with the
ceremonies
• What this is not
– Comparison with another methodologies/framework
– How to implement Scrum in Verizon
– Scrum Experiences Implementation

6. Agenda
 Scope
Video - https://www.youtube.com/watch?v=XU0llRltyFM
 What’s Scrum?
 When is Scrum appropiate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

7. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropiate?
 Artifacts
 Scrum Flow
Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

8. What’s SCRUM?
• Scrum is not a Methodology. Scrum is a Framework for
surfacing organizational dysfunction.
• Scrum is an iterative incremental, agile software
development framework.
• Scrum doesn’t provide answers. It helps you ask better
questions.
• Scrum doesn’t actually do anything. People do things.
• Scrum seeks to optimize overall progress by making
continuous adaptations.

9. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

10. When is Scrum Appropriate?
• Scrum works best when the
problems to be solved lie in
the Complex Space.
• New Product Development
Work and Knowledge Work
both tend to exist in the
Complex Space.
• Research lies in the Chaos
space
• Maintenance lies in the
Simple Space

11. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

12. Artifacts
• Product Backlog
– Living list of Requirements
– Broken Down into User Stories
– The WHAT of the product
– ROI Prioritized
• Sprint Backlog
– Committed Backlog: A list of
tasks representing the HOW
of the system
Release
Backlog

13. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

14. Scrum Flow

15. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

16. Roles – Committed vs Involved

17. Roles
• Chickens
– Stakeholders
– Users
– Managers

18. Roles
• Pigs
– Product Owner
– Scrum Master
– Team Member

19. Scrum Flow

20. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

21. Ceremonies
• Sprint Planning Meeting (Pigs only… others silently attend)
– Suggested Timebox: 8-16 hours
• 1st part (Estrategic): Prioritize most important Product backlog items
– Owner: Product Owner
• 2nd part (Tactic): Team designs and plans the sprint
– Owner: Team
• Sprint (Team Members Only)
– Suggested Timebox: 2-4 weeks
– Owner: Team
• Daily Scrum Meeting (Scrum Master + Team Members)
– Timebox: 15 Minutes
• Answer the 3 questions
– Owner: Team
• Sprint Demo Meeting (Pigs & Chickens)
– Suggested Timebox: 4 hours
– Owner: Team and Product Owner
• Sprint Retrospective Meeting (Pigs only… others silently attend)
– Suggested Timebox: 2-4 hours
– Owner: Scrum Master

22. Scrum Flow

23. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

24. Metrics
• Release Burndown
– Amount of Work Remaining for a Release
– Basis of measurement: Story Points or
Effort hours
– Level and usage: Project level
• Sprint Burndown
– Amount of Work Remaining for a Sprint
– Basis of measurement: Effort hours
– Level and usage: Sprint level

25. Metrics
• Velocity Trend
– How much work the team can expect to complete based on prior efforts.
– Basis of measurement: Story points or “ideal engineering hours”
– Level and usage: most useful at the project level.

26. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

27. Tips
• The ScrumMaster is responsible for ensuring that the Scrum Team
adheres to Scrum values, practices, and rules.
• The ScrumMaster helps the Scrum Team understand and use self-
management and cross-functionality.
• The ScrumMaster should never be the Product Owner.
• The Product Owner is the one and only person responsible for
managing the Product Backlog
• There are no titles on Teams, and there are no exceptions to this
rule. Teams do not contain sub-Teams dedicated to particular
domains like testing or business analysis, either.
• Teams are self-organizing. No one – not even the ScrumMaster –
tells the Team how to turn Product Backlog into increments of
shippable functionality.

28. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

29. Summary
• Group of people working together very closely and self
organized
• Incentivizes changing requirements
• Timeboxing creates the rhythm that drives development
• Delivering items of highest value to the Customer First
– Don’t waste time developing something that the Customer may
never use.

30. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

31. Agenda
 Scope
 Video
 What’s Scrum?
 When is Scrum appropriate?
 Artifacts
 Scrum Flow
 Roles
 Ceremonies
 Metrics
 Tips
 Summary
 Q&A

33. Links
 SCRUM in under 10 Minutes (HD) by @hamids
https://www.youtube.com/watch?v=XU0llRltyFM
 SCRUM GUIDE By Ken Schwaber, May, 2009
http://www.scrumalliance.org/resource_download/598
 SCRUM Development Process by Ken Schwaber
http://www.jeffsutherland.org/oopsla/schwapub.pdf
 Hyperproductive Distributed Scrum Teams
http://www.youtube.com/watch?v=Ht2xcIJrAXo
 Agile Estimation / Planning
http://www.youtube.com/watch?v=fb9Rzyi8b90
http://www.youtube.com/watch?v=jeT0pOVg0EI
 SCRUM Alliance http://www.scrumalliance.org/

34. Thanks!
That was your training…