Embed Size (px)
DESCRIPTION
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
Citation preview
Scrumin 10 slides
by Pierre Mengal – www.mindfulhacker.comScrum In Ten Slides v1.1 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported License.
Copyright © Pierre Mengal - Cartoons artworks licensed under copyright © by cartoon solutions
Scrum Overview
The Product OwnerResponsible for the product backlogand maximizing the product ROI.• Represents the users• Clearly expresses backlog items• Orders them by value• Ensures visibility
The Development TeamResponsible for delivering a potentially shippableincrement of working software.• Self-organized• Cross functional• Developer as title• Defines practices• 4 to 9 persons
The Scrum MasterResponsible for the scrum process
• Removes impediments• Facilitates scrum events• Facilitates communication
The Product BacklogSingle source of requirements for any changes to bemade to the product.
• Living list that is never complete• Ordered: value, risk, priority & necessity• Estimated by the team
The Definition of DoneUsed to assess when work is complete on theproduct increment.
• Defined by the product owner• Unique for the whole team• Must allow immediate release• Quality increases with maturity
The Sprint PlanningTwo part time boxed meeting: 8h/1m sprint. 1. Defines what will be delivered in the increment• Team selects items from the product backlog and defines a sprint goal
2. Defines how the increment will be achieved• Items are converted into tasks & estimated
The Daily Scrum15 minute time-boxed event for the Teamto synchronize activities.
• What has been accomplished since last meeting?• What will be done before the next meeting?• What obstacles are in the way?
The Sprint Review4 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
The Sprint RetrospectiveImproves the process.
• Inspect how the last Sprint went• Identify and order the major items that went well and potential improvements; and,• Create a plan for implementing improvements
Further Reading
The Official Scrum Guidehttp://www.scrum.org/
[email protected] | http://www.mindfulhacker.com
