Scrum Feb 11, 2012 Sao Paulo, Brasil #CPBR5 Carlos.Crosetti@gmail.com 1
Agenda Scope Whai is Scrum Artifacts Scrum Flow Roles Ceremonies Metrics Tips Summary Resources Real life project example (no slide, demo) Scrum Wing 3D Tour (code.google.com, search SW3D ) Q&A 2
Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 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. 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
Scope What this is about Conceptual understanding of Scrum Understanding of the overall Scrum process How the essential Scrum roles work together with the ceremonies What this is not Comparison with another methodologies/framework How to implement Scrum 4
What is 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 actually do anything. People do things. Scrum is ideally for projects with rapidly changing or highly emergent requirements. 5
Artifacts Product Backlog Living list of Requirements ROI Prioritized Broken down into User Stories Product features Sprint Backlog Committed Backlog broken down into Tasks 6
Scrum Flow 7
Roles Chickens Stakeholders Users Managers Pigs Product Owner Scrum Master Team Member 8
Ceremonies Sprint Planning Meeting (Pigs only others silently attend) Sprint (Team Members Only) Timebox: 15 Minutes Answer the 3 questions Owner: Scrum Master Sprint Demo Meetings (Pigs & Chickens) Suggested Timebox: 2-4 weeks Owner: Scrum Team Daily Scrum Meeting (Scrum Master + Team Members) Suggested Timebox: 8-16 hours 1st part: Prioritize most important Product backlog items 2nd part: Team designs and plans the sprint Owner: Product Owner Suggested Timebox: 4 hours Owner: Product Owner Sprint Retrospective Meeting (Pigs only others silently attend) Suggested Timebox: 2-4 hours Owner: Scrum Master 9
Metrics Release Burndown Amount of Work Remaining for a Release Basis of measurement: 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 (Showing a real-life example later on) 10
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. 11
Tips The ScrumMaster is responsible for ensuring that the Scrum Team adheres to Scrum values, practices, and rules. helps the Scrum Team understand and use self-management and cross-functionality. should never be the Product Owner. The Product Owner is the only person responsible for managing the Product Backlog Teams are self-organizing. No one not even the ScrumMaster tells the Team how to turn Product Backlog into increments of shippable functionality. 12
Summary Group of people working together very closely and self organized Accepts 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. 13
Resources Scrum in under 10 Minutes (HD) by @hamids http://www.youtube.com/watch?v=q5k7a9yeoui Scrum guide by Ken Schwaber http://www.scrumalliance.org/resource_download/598 Scrum Development Process by Ken Schwaber http://www.jeffsutherland.org/oopsla/schwapub.pdf Agile Estimation / Planning http://www.youtube.com/watch?v=fb9rzyi8b90 Metodologías ágiles de direción de proyectos, por Alejandro Gabay http://campus.ort.edu.ar/extension/descargar/articulos/195172/ Scrum Alliance http://www.scrumalliance.org/ Tool: ScrumWorks http://www.danube.com/scrumworks Tool: Agilo http://www.agile42.com/cms/pages/agilo/ Tool: IceSCRUM http://www.icescrum.org/ Tool: SW3D http://code.google.com/p/scrum-wing-3d/ 14
#CPBR5 campuseros: Thank You! 0 @ccrosetti 15