1. Scrum
in 10 slides
by Pierre Mengal – Scrum In Ten Slides v2.0 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported License. Copyright © Pierre Mengal - Cartoons artworks licensed under copyright © by cartoon solutions

2. Scrum Overview

3. The Product Owner Responsible for the product backlog
and maximizing the product ROI.
Sole person responsible for managing the product backlog
Clearly expresses backlog items
Orders them by value
Ensures visibility & transparency of the backlog

4. The Development Team
Responsible for delivering a potentially shippable
increment of working software.
Self-organized
Cross functional
Defines practices
3 to 9 persons
No title

5. The Scrum Master Responsible for the scrum process
Serves the product owner, the development team and the organization
Leads the organization in its Scrum adoption
Fascilitate Scrum events
Removes impediments

6. The Product Backlog
Single source of requirements for any changes to be
made to the product.
Dynamic list that is never complete
Ordered: value, risk, priority & necessity
Refined by the Scrum Team (max 10%)
Higher ordered items clearer & detailed
Estimated by the Development Team

7. The Definition of Done Used to assess when work is complete on the
product increment.
Defined by the Scrum Team or the Organization
Unique for the whole team
Must allow immediate release
Expands as Scrum Teams mature to increase quality

8. The Sprint Planning Two part time boxed meeting: 8h/1m sprint.
Defines what will be delivered in the increment
Team selects items from the product backlog
and defines a sprint goal
Defines how the increment will be achieved
Items are converted into tasks & estimated

9. The Daily Scrum 15 minute time-boxed event for the Team
to synchronize activities and focuses on progress
Toward the Sprint Goal.
What I did yesterday that helped the Team to meet the Sprint Goal?
What will I do today to help?
Do I see obstacles that prevents me or the Team from meeting the Sprint Goal?

10. The Sprint Review 4 hour time-boxed meeting
Product owner identifies what has been done
Team discusses what went well, what problems it
ran into & those that were solved
Team demonstrates what it has done in a demo
Product owner discusses the backlog as it stands
Entire group collaborates on what to do next

11. The Sprint Retrospective
Improves the process.
Inspect how the last Sprint went with regards to people, relationships, process & tools
Identify and order the major items that went well
and potential improvements; and,
Create a plan for implementing improvements

12. Further Reading The Official Scrum Guide http://www.scrum.org/|