Introduction to scrum
Download as PPT, PDF0 likes438 views
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines common Scrum events like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also explains main Scrum artifacts like the product backlog, sprint backlog, and burn down charts that are used to track work. The document aims to explain the basic concepts, roles, events, and artifacts that make up the Scrum framework.
Introduction to scrum
- 1. Semen Cirit 26/Feb/2016 Presented by An Introduction to Scrum
- 2. • 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. Scrum in 100 words
- 3. Scrum has been used by: •Microsoft •Yahoo •Google •Electronic Arts •High Moon Studios •Lockheed Martin •Philips •Siemens •Nokia •Capital One •BBC •Intuit •Intuit •Nielsen Media •First American Real Estate •BMC Software •Ipswitch •John Deere •Lexis Nexis •Sabre •Salesforce.com •Time Warner •Turner Broadcasting •Oce
- 4. 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 • Video game development • FDA-approved, life-critical systems • Satellite-control software • Websites • Handheld software • Mobile phones • Network switching applications • ISV applications • Some of the largest applications in use
- 5. Characteristics • Self-organizing teams • Product progresses in a series of month-long “sprints” • Requirements are captured as items in a list of “product backlog” • No specific engineering practices prescribed • Uses generative rules to create an agile environment for delivering projects • One of the “agile processes”
- 6. Project noise level Simple Complex Anarchy Com plicated Technology RequirementsFar from Agreement Close to Agreement Closeto Certainty Farfrom Certainty Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.
- 7. Scrum Cancel Gift wrap Return Sprint 2-4 weeks Return Sprint goal Sprint backlog Potentially shippable product increment Product backlog CouponsGift wrap Coupons Cancel 24 hours
- 8. Putting it all together Image available at www.mountaingoatsoftware.com/scrum
- 9. Sprints • 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
- 10. 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
- 11. No changes during a sprint • Plan sprint durations around how long you can commit to keeping change out of the sprint Change
- 12. Scrum framework •Product owner •ScrumMaster •Team Roles •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
- 13. Scrum framework •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts •Product owner •ScrumMaster •Team Roles
- 14. 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
- 15. 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 • Shield the team from external interferences
- 16. 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)
- 17. The team • Teams are self-organizing • Ideally, no titles but rarely a possibility • Membership should change only between sprints
- 18. •Product owner •ScrumMaster •Team Roles Scrum framework •Product backlog •Sprint backlog •Burndown charts Artifacts •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies
- 19. 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 TechnologyTechnology Current product Current product
- 20. Sprint planning Two part time boxed meeting: 8h/4w sprint. 1.Defines what will be delivered in the increment Team selects items from the product backlog and defines a sprint goal 1.Defines how the increment will be achieved •Items are converted into tasks & estimated Participants: BO, PO, SM, development team 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)
- 21. The daily scrum • Parameters • Daily • 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
- 22. Everyone answers 3 questions • These are not status for the ScrumMaster • They are commitments in front of peers What did you do yesterday?What did you do yesterday? 1 What will you do today?What will you do today? 2 Is anything in your way?Is anything in your way? 3
- 23. 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
- 24. 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
- 25. Start / Stop / Continue • Whole team gathers and discusses what they’d like to: Start doingStart doing Stop doingStop doing Continue doingContinue doing This is just one of many ways to do a sprint retrospective.
- 26. Grooming Backlog refinement •Middle of the sprint is a good time for grooming •Treat the backlog grooming meeting just like the first part of the Sprint Planning Meeting •Make sure the PO knows that, during all of this sprint's backlog grooming sessions, they will be expected to present enough work to last about 2 Sprints *beyond* the current sprint. •Make sure everyone understands that estimates and Product backlog order are not final until a PBI has been accepted into a sprint. •Definitely feel free to split PBI's during this meeting. •Don't be afraid to discuss a couple of items that are further needs break down on backlog •Don't be afraid to introduce late breaking PBI's.Try to minimize them, but embrace them when they happen Participants: PO, SM, development team + additional business unit
- 27. •Product owner •ScrumMaster •Team Roles Scrum framework •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
- 28. 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 • Reprioritized at the start of each sprint • Living list that is never complete • Ordered: value, risk, priority & necessity • Estimated by the team This is the product backlog This is the product backlog
- 29. Definition of Done Used to assess when work is complete on the product increment. •Defined by the product owner or relavant person (Business or Enterprise Owner) •Unique for the whole team •Must allow immediate release •Quality increases with maturity
- 30. 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
- 31. The sprint goal • A short statement of what the work will be focused on during the sprint Database Application Financial services Life Sciences Support features necessary for population genetics studies. Support more technical indicators than company ABC with real-time, streaming data. Make the application run on SQL Server in addition to Oracle.
- 32. Managing the sprint backlog • Individuals sign up for work of their own choosing • Work is never assigned • Estimated work remaining is updated daily
- 33. Managing the sprint backlog • 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. A sprint backlog TasksTasks Code the user interface Code the middle tier Test the middle tier Write online help Write the foo class MonMon 8 16 8 12 8 TuesTues 4 12 16 8 WedWed ThurThur 4 11 8 4 FriFri 8 8 Add error logging 8 10 16 8 8
- 35. A sprint burndown chartHours
- 36. Hours 40 30 20 10 0 Mon Tue Wed Thu Fri TasksTasks Code the user interface Code the middle tier Test the middle tier Write online help MonMon 8 16 8 12 TuesTues WedWed ThurThur FriFri 4 12 16 7 11 8 10 16 8 50