Scrum

An introduction to Scrum. I held it at university today.

Transcript

1. Lucas Dohmen 290333 Scrum An a ile software development method
2. A ile • Bein adaptive • Iterative development • Minimize need for meetin s • a ilemanifesto.or • Different methodolo ies to reach it
3. A ile Methodolo ies • Lean and Kanban, adapted from TPS • Scrum • XP, Kent Beck • Crystal, Alistair Cockburn • Tools: TDD, Pair Pro rammin , Continuous Inte ration, Continuous Deployment…
4. History of Scrum • OOPSLA in 1995, Ken Schwaber and Jeff Sutherland • A ile Manifesto, 2001
5. Empirical process control: Three Pillars Transparency Inspection Adaption
6. “ Everyone must understand what “Done” means. The Scrum Guide
7. Product Backlo • Ordered list of everythin that mi ht be needed • Requirements, Chan es • Evolves durin the project • Ordered by value, risk, priority, necessity
8. The Scrum Team • Product Owner • Development Team • Scrum Master • Ancillary roles: Stake Holders, Mana ers…
9. Development Team • Work on the product • Mana e their own work • All skills necessary to increment the product • The entire team is accountable for the whole • Sole responsible for estimations • 3 to 9 people
10. Product Owner • Maximize value of the product and work of development team • Sole person to mana e the product backlo • Mana e it, order it and make it visible • Ensure the development team understands the items • One person, not a committee
11. Scrum Master • Ensure that scrum is understood and the team adheres to it • Mana es interaction with outside world • Coachin , helpin with the process • Facilitate scrum events as requested
12. • Time boxed: One month or less • No chan es durin a sprint that affect the sprint oal or composition of the team • But: The scope may be clarified or re- ne otiated • Each sprint finishes a oal • Only the product owner can cancel a sprint The Sprint
13. Sprint Backlo • Set of items selected from product backlo for the sprint • Modified by Development Team durin sprint • Hi hly visible
14. Scrum Events Sprint Plannin Meetin < 8 hours Daily Scrums < 15 minutes Sprint Review < 4 hours Sprint Retrospective < 3 hours For one-month sprints
15. Sprint Plannin Meetin • Basis is the product backlo • Two parts, each the half of the time: • What will be done? • How will it be done? • The result is the sprint backlo
16. Daily Scrums • Last 24 hours, next 24 hours • Point out obstacles • Only the development team
17. Sprint Review • At the end of the sprint • Informal meetin • What was done, what was not done? • What could be done next?
18. Sprint Retrospective • After the Sprint Review • Look at the process • Inspection: People, Relationships, Tools
19. Tools • JIRA Green Hopper • Addons for Redmine, Chilliproject • and many more
20. Sources • The Scrum Guide, Ken Schwaber and Jeff Sutherland, 2011 • A ile Softwareentwicklun – Ein Überblick, Hennin Wolf and Arne Roock, 2009