An Introduction to Scrum: presented at PyTexas 2012
2 likes1,037 views
This document provides an introduction to Scrum, an agile framework for project management. It defines key Scrum roles like the Product Owner and Scrum Master. Scrum uses short iterations called sprints to incrementally develop working software. Teams self-organize during daily stand-up meetings and track progress using artifacts like the product backlog and sprint backlog. Scrum aims to deliver business value continuously through inspection and adaptation at the end of each sprint.
![47
Contact
● E-mail: tomo [at] pertpower.com
● E-mail: tomo [at] ece.tamu.edu
● E-mail: tp0x45 [at] gmail.com
● LinkedIn](https://image.slidesharecdn.com/pytexas2012-140707150106-phpapp02/85/An-Introduction-to-Scrum-presented-at-PyTexas-2012-47-320.jpg)
An Introduction to Scrum: presented at PyTexas 2012
- 1. 1 An Introduction to Scrum Presented by T. Popovic PyTexas 2012
- 2. 2 About Me ● Born in 1969, ex-YU, married, three kids ● Software developer with over 20 years experience ● Agile coach, project manager ● MSEE, CSM, CSPO ● ISO 9001 ● Open source advocate ● Retro computing
- 4. 4 Scrum in 100 words ● Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. ● It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). ● The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. ● Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
- 6. 6 We are losing the relay race Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”, Harvard Business Review, January 1986. “The… ‘relay race’ approach to product development… may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach - where a team tries to go the distance as a unit, passing the ball back and forth - may better serve today’s competitive requirements.”
- 7. 7 Scrum origins ● Jeff Sutherland – Initial scrums at Easel Corp in 1993 – IDX and 500+ people doing Scrum ● Ken Schwaber – ADM – Scrum presented at OOPSLA 96 with Sutherland – Author of three books on Scrum ● Mike Beedle – Scrum patterns in PLOPD4 ● Ken Schwaber and Mike Cohn – Co-founded Scrum Alliance in 2002, initially within the Agile Alliance
- 8. 8 Scrum has been used by ● Microsoft ● Yahoo ● Google ● Apple ● Electronic Arts ● Lockhead Martin ● Philips ● Siemens ● Nokia ● IBM ● Capital One ● BBC ● Intuit ● Nielsen Media ● First American Real Estate ● BMC Software ● Ipswitch ● John Deere ● Lexis Nexis ● Sabre ● Salesforce.com ● Time Warner ● Turner Broadcasting ● Oce
- 9. 9 Scrum has been used for ● Commercial software ● In-house development ● Contract development ● Fixed-price projects ● Financial applications ● ISO 9001-certified applications ● Embedded systems ● 24x7 systems with 99.999% uptime requirements ● the Joint Strike Fighter ● Outsourcing ● Video game development ● FDA-approved, life-critical systems ● Satellite-control software ● Websites ● Hand-held software ● Mobile phones ● Network switching applications ● ISV applications ● Some of the largest applications in use
- 10. 10 Characteristics ● Self-organizing teams ● Product progresses in a series of iterations called “sprints” (two-four weeks) ● Requirements are captured as items in a list of “product backlog” ● No specific engineering practices prescribed ● Provides simple rules to create an agile environment for delivering projects ● One of the “agile processes”
- 11. 11 The Agile Manifesto: a statement of values ● 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.” Source: http://agilemanifesto.org
- 12. 12 The process Image source: http://en.wikipedia.org/wiki/Scrum_(development)
- 13. 13 Sprint ● Scrum projects make progress in a series of “sprints” – Analogous to Extreme Programming iterations ● Typical duration is 2–4 weeks or a calendar month at most ● A constant duration leads to a better rhythm ● Product is designed, coded, and tested during the sprint
- 14. 14 Sequential vs. overlapping development Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Requirements Design Code Test
- 15. 15 No changes during a sprint ● Plan sprint durations around how long you can commit to keeping change out of the sprint Change
- 16. 16 Scrum framework •Product owner •ScrumMaster •Team Roles •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
- 17. 17 Scrum framework: roles •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts •Product owner •ScrumMaster •Team Roles
- 18. 18 Product owner ● Define the features of the product ● Decide on release date and content ● Be responsible for the profitability of the product (ROI) ● Prioritize features according to market value ● Adjust features and priority every iteration, as needed ● Accept or reject work results
- 19. 19 The ScrumMaster ● Represents management to the project ● Responsible for enacting Scrum values and practices ● Removes impediments ● Ensure that the team is fully functional and productive ● Enable close cooperation across all roles and functions ● Shields the team from external interferences
- 20. 20 The team ● Typically 5-9 people ● Cross-functional: – Programmers, testers, user experience designers, etc. ● Members should be full-time – May be exceptions (e.g., database administrator) ● Teams are self-organizing – Ideally, no titles but rarely a possibility ● Membership should change only between sprints
- 21. 21 Scrum framework: ceremonies •Product owner •ScrumMaster •Team Roles •Product backlog •Sprint backlog •Burndown charts Artifacts •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies
- 22. 22 Sprint planning Sprint planning meeting Sprint prioritization • Analyze and evaluate product backlog • Select sprint goal Sprint planning • Decide how to achieve sprint goal (design) • Create sprint backlog (tasks) from product backlog items (user stories / features) • Estimate sprint backlog in hours Sprint goal Sprint goal Sprint backlog Sprint backlog Business conditions Business conditions Team capacity Team capacity Product backlog Product backlog Techno- logy Techno- logy Current product Current product
- 23. 23 Sprint planning ● Team selects items from the product backlog they can commit to completing ● Sprint backlog is created – Tasks are identified and each is estimated (1-16 hours) – Collaboratively, not done alone by the ScrumMaster ● High-level design is considered As a vacation planner, I want to see photos of the hotels. As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
- 24. 24 The daily Scrum ● Parameters – Daily – Up to 15-minutes – Stand-up ● Not for problem solving – Whole world is invited – Only team members, ScrumMaster, product owner, can talk ● Helps avoid other unnecessary meetings
- 25. 25 Everyone answers 3 questions ● The daily scrum questions: – What did you do yesterday? – What will you do today? – Is anything in your way? ● These are not status for the ScrumMaster – They are commitments in front of peers
- 26. 26 The sprint review ● Team presents what it accomplished during the sprint ● Typically takes the form of a demo of new features or underlying architecture ● Informal – 2-hour prep time rule – No slides ● Whole team participates ● Invite the world
- 27. 27 Sprint retrospective ● Periodically take a look at what is and is not working ● Typically 15–30 minutes ● Done after every sprint ● Whole team participates – ScrumMaster – Product owner – Team – Possibly customers and others
- 28. 28 Start / Stop / Continue ● Whole team gathers and discusses what they’d like to: – Start doing – Stop doing – Continue doing This is just one of many ways to do a sprint retrospective.
- 29. 29 Scrum framework: artifacts •Product owner •ScrumMaster •Team Roles •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
- 30. 30 Product backlog ● The requirements ● A list of all desired work on the project ● Ideally expressed such that each item has value to the users or customers of the product ● Prioritized by the product owner ● Re-prioritized at the start of each sprint
- 31. 31 A sample product backlog Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a reservation. 5 As a guest, I want to change the dates of a reservation 3 As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8 Improve exception handling 8 ... 30 ... 50 lbs
- 32. 32 Sprint goal / theme ● A short statement of what the work will be focused on during the sprint ● Examples: – Make the application run on SQL server in addition to Oracle. – Make the website open nicely on mobile devices. – Support more technical indicators than company ABC with real-time streaming data. – Bug fixing, hmmm....
- 33. 33 Managing the sprint backlog ● Individuals sign up for work of their own choosing – Work is never assigned ● Estimated work remaining is updated daily ● Any team member can add, delete or change the sprint backlog ● Work for the sprint emerges ● If work is unclear, define a sprint backlog item with a larger amount of time and break it down later ● Update work remaining as more becomes known
- 34. 34 A sprint backlog Tasks Mon Tue Wed Thu Fri Code the user interface 8 4 8 Code the middle tier 16 12 10 4 Test the middle tier 8 16 16 11 8 Write online help 12 Write the foo class 8 8 8 8 8 Add error logging 8 4
- 36. 36 Scrum task board ● Backlog items ● To Do ● In progress ● Testing ● Finished, done!? Image source: http://en.wikipedia.org/wiki/Scrum_(development)
- 37. 37 Quick look at user stories ● Templates (“index card format”): – “As a <role>, I want <goal/desire> so that <benefit>” – "As a <role>, I want <goal/desire>” – "In order to <receive benefit> as a <role>, I want <goal/desire>" ● Acceptance criteria (COS1, COS2, ...) ● Support materials (UI design, references, …) ● Ready!? Good info: http://en.wikipedia.org/wiki/User_story
- 38. 38 One more look at the whole thing
- 39. 39 Scrum Tools (some...) ● Index cards ● Post It stickers ● Dry erase boards ● Cork boards ● Stapler ● Coffeemaker ● Smartphone ● RallyDev ● ScrumDo ● Acunote ● Collabnet ● Scrumwise ● VersionOne ● AgileBuddy ● GoogleDoc, Office
- 40. 40 How do I start the darn thing? ● What if there is no backlog? ● New product: little project before the project – Identify main users and user roles – Identify main features, capture 80% of possible release – Vision, feasibility study ● Existing product: is there a backlog? – Assess the technical dept – Create enough to get you going
- 41. 41 Scalability ● Typical individual team is 7 ± 2 people – Scalability comes from teams of teams ● Factors in scaling – Type of application – Team size – Team dispersion – Project duration ● Scrum has been used on multiple 500+ person projects
- 42. 42 Scaling through the Scrum of scrums
- 43. 43 Scrum of scrums of scrums
- 44. 44 A Scrum reading list ● Agile and Iterative Development: A Manager’s Guide by Craig Larman ● Agile Estimating and Planning by Mike Cohn ● Agile Project Management with Scrum by Ken Schwaber ● Agile Retrospectives by Esther Derby and Diana Larsen ● Agile Software Development Ecosystems by Jim Highsmith ● Agile Software Development with Scrum by Ken Schwaber and Mike Beedle ● Scrum and The Enterprise by Ken Schwaber ● User Stories Applied for Agile Software Development by Mike Cohn ● Lots of weekly articles at www.scrumalliance.org
- 45. 45 Where to go next? ● www.scrumalliance.org ● www.scrum.org ● www.mountaingoatsoftware.com/scrum ● scrumdevelopment@yahoogroups.com
- 46. 46 Attribution ● This presentation is based largely on the slides provided in redistributable presentation “An Introduction to Scrum” by Mike Cohn, Mountain Goat Software, LLC
- 47. 47 Contact ● E-mail: tomo [at] pertpower.com ● E-mail: tomo [at] ece.tamu.edu ● E-mail: tp0x45 [at] gmail.com ● LinkedIn