Introduzione a Scrum


Published on

Un primo assaggio di Scrum

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Introduzione a Scrum

  1. 1. Scrum AgileIntroduzioneIng. Felice 04 Febbraio 2013
  2. 2. AGENDAWhy Scrum?AgileHow to use ScrumSCRUM - 2Introduzione
  3. 3. SCRUM IN 10 PAROLE… but not only An Empirical Methodology for Maximizing ROI of Software Development ProjectsSCRUM - 3Introduzione
  4. 4. SCRUM IN 10 PAROLE… but not onlyScrum is an agile process that allows us to focus on delivering the highest businessvalue in the shortest time.It allows us to rapidly and repeatedly inspect actual working software (every two weeksto one month).The business sets the priorities. Teams self-organize to determine the best way todeliver the highest priority features.Every two weeks to a month anyone can see real working software and decide to releaseit as is or continue to enhance it for another sprint.SCRUM - 4Introduzione
  5. 5. LE ORIGININot only one 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 AllianceSCRUM - 5Introduzione
  6. 6. LE ORIGINITimeline1995: • analysis of common software development processes  not suitable for empirical, unpredictable and non-repeatable processes • Design of a new method: Scrum by Jeff Sutherland & Ken Schwaber • Enhancement of Scrum by Mike Beedle & combination of Scrum with Extreme Programming1996: • introduction of Scrum at OOPSLA conference2001: • publication “Agile Software Development with Scrum” by Ken Schwaber & Mike BeedleSuccessful appliance of Scrum in over 50 companiesFounders are members in the Agile AllianceSCRUM - 6Introduzione
  7. 7. CHI LO USA?Many MoreMicrosoft IntuitYahoo Nielsen MediaGoogle First American Real EstateElectronic Arts BMC SoftwareHigh Moon Studios IpswitchLockheed Martin John DeerePhilips Lexis NexisSiemens SabreNokia Salesforce.comCapital One Time WarnerBBC Turner BroadcastingIntuit OceSCRUM - 7Introduzione
  8. 8. PERCHE’ LO SI USA?Many MoreCommercial software FDA-approved, life-critical systemsIn-house development Satellite-control softwareContract development WebsitesFixed-price projects Handheld softwareFinancial applications Mobile phonesISO 9001-certified applications Network switching applicationsEmbedded systems ISV applications24x7 systems with 99.999% uptime requirements Some of the largest applications in usethe Joint Strike FighterVideo game developmentSCRUM - 8Introduzione
  9. 9. AGILE4 VALORI Individuals and interactions Individuals and interactions over Process and tools Process and tools Working software Working software over Comprehensive documentation Comprehensive documentation Customer collaboration Customer collaboration over Contract negotiation Contract negotiation Responding to change Responding to change over Following a plan Following a plan Source: www.agilemanifesto.orgSCRUM - 9Introduzione
  10. 10. PROJECT NOISE LEVELNever Anarchy Far from Agreement Anarchy Complex Requirements Co m pl ica te d Simple Close to Agreement Technology Close to Certainty Far from Certainty Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.SCRUM - 10Introduzione
  11. 11. CARATTERISTICHEAn ExampleSelf-organizing teams No specific engineering practices prescribedProduct progresses in a series of month-long Uses generative rules to create an agile environment“sprints” for delivering projectsRequirements are captured as items in a list of One of the “agile processes”“product backlog”SCRUM - 11Introduzione
  12. 12. SCRUM IN ONE PICTUREIs all there!SCRUM - 12Introduzione
  13. 13. SPRINTOptimizing the whole• 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 sprintSCRUM - 13Introduzione
  14. 14. SEQUENTIAL VS. OVERLAPPING DEVELOPMENT Never more waterfall Requirements Design Code Test Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. SCRUM - 14 Introduzione
  15. 15. FREEZED SPRINT No more change after day “zero” Change Plan sprint durations around how long you can commit to keeping change out of the sprint SCRUM - 15 Introduzione
  16. 16. SCRUM FRAMEWORKThree elements Roles •Product owner •ScrumMaster Ceremonies •Team Members •User •Sprint planning •Stakeholder •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown chartsSCRUM - 16Introduzione
  17. 17. SCRUM FRAMEWORKThree elements Sprint planning meeting Team capacity Team capacity Sprint prioritization Product • Analyze and evaluate product backlog Sprint Sprint Product • Select sprint goal goal backlog backlog goal Business Business conditions Sprint planning conditions • Decide how to achieve sprint goal (design) • Create sprint backlog (tasks) from product Current Current backlog items (user stories / features) Sprint Sprint product product • Estimate sprint backlog in hours backlog backlog Technology TechnologySCRUM - 17Introduzione
  18. 18. SCRUM FRAMEWORKRoles Roles •Product owner •ScrumMaster •Team Members •User •StakeholderSCRUM - 18Introduzione
  19. 19. ROLES: PRODUCT OWNER First • 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 SCRUM - 19 Introduzione
  20. 20. ROLES: SCRUM MASTER Second • 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 SCRUM - 20 Introduzione
  21. 21. ROLES: THE TEAM Third • 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 SCRUM - 21 Introduzione
  22. 22. SCRUM FRAMEWORKCeremonies Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meetingSCRUM - 22Introduzione
  23. 23. CEREMONIES: SPRINT PLANNIG First • 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 Code the middle tier (8 hours) As aavacation planner, II As vacation planner, Code the user interface (4) want to see photos of want to see photos of Write test fixtures (4) the hotels. the hotels. Code the foo class (6) Update performance tests (4) SCRUM - 23 Introduzione
  24. 24. CEREMONIES: THE DAILY SCRUM Second • 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 SCRUM - 24 Introduzione
  25. 25. CEREMONIES: THE DAILY SCRUM Everyone answers 3 questions 1 • These are not What did you do yesterday? What did you do yesterday? status for the ScrumMaster 2 • They are What will you do today? What will you do today? commitments in front of 3 peers Is anything in your way? Is anything in your way? SCRUM - 25 Introduzione
  26. 26. CEREMONIES: THE SPRINT REVIEW Third • 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 SCRUM - 26 Introduzione
  27. 27. CEREMONIES: SPRINT RETROSPECTIVE Fourth • 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 SCRUM - 27 Introduzione
  28. 28. CEREMONIES: START/STOP/CONTINUE Fifth Whole team gathers and discusses what they’d like to Start doing Start doing e t on o j us s t i s i s w ay Th any Stop doing Stop doing t of m a sp r in e . Continue doing do pectiv Continue doing re tros SCRUM - 28 Introduzione
  29. 29. SCRUM FRAMEWORKArtifacts Artifacts •Product backlog •Sprint backlog •Burndown chartsSCRUM - 29Introduzione
  30. 30. CEREMONIES: PRODUCT BACKLOG First • 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 This is the This is the product backlog product backlog SCRUM - 30 Introduzione
  31. 31. CEREMONIES: PRODUCT BACKLOG A sample product backlog SCRUM - 31 Introduzione
  32. 32. CEREMONIES: THE SPRINT GOAL Second Life Sciences Database Application Support features necessary for population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real- time, streaming data. SCRUM - 32 Introduzione
  33. 33. CEREMONIES: MANAGING THE SPRINT BACKLOG Third • 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 SCRUM - 33 Introduzione
  34. 34. CEREMONIES: MANAGING THE SPRINT BACKLOG Third Tasks Tasks Mon Mon Tues Tues Wed Wed Thur Thur Fri FriCode the user interface 8 4 8Code the middle tier 16 12 10 4Test the middle tier 8 16 16 11 8Write online help 12Write the foo class 8 8 8 8 8Add error logging 8 4 SCRUM - 34 Introduzione
  36. 36. CEREMONIES: MANAGING THE SPRINT BACKLOG Third Tasks Tasks Mon Tues Wed Thur Fri Mon Tues Wed Thur FriCode the user interface 8 4 8Code the middle tier 16 12 10 7Test the middle tier 8 16 16 11 8Write online help 12 SCRUM - 36 Introduzione
  37. 37. CEREMONIES: MANAGING THE SPRINT BACKLOG Third 50 40 30 Hours 20 10 0 Mon Tue Wed Thu Fri SCRUM - 37 Introduzione
  38. 38. CEREMONIES: SCALABILITY Fourth • 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 SCRUM - 38 Introduzione
  39. 39. SCALING THROUGH THE SCRUM OF SCRUMS @Scale SCRUM - 39 Introduzione
  40. 40. Riferimenti Book and Web Resources Mike Cohn Mike Cohn (720) 890-6110 (office) (720) 890-6110 (office) ) but you must credit the You can remove this (or any slide and source somewhere in your presentation. Use the logo for exam ple) or include a company name (as at bottom left, ons (or all) of your slide somewhere saying that porti presentation are from this source. Thanks. SCRUM - 40 Introduzione
  41. 41. Riferimenti Book and Web Resources Agile and Iterative Development: A Manager’s Guide Agile Software Development with Scrum by Ken by Craig Larman Schwaber and Agile Estimating and Planning by Mike Cohn Mike Beedle Agile Project Management with Scrum by Ken Scrum and The Enterprise by Ken Schwaber Schwaber Succeeding with Agile by Mike Cohn Agile Retrospectives by Esther Derby and Diana User Stories Applied for Agile Software Development Larsen by Mike Cohn Agile Software Development Ecosystems by Jim Highsmith SCRUM - 41 Introduzione
  42. 42. ABOUT MEget in touch Felice Pescatore, Agile Software Architect Email: @SCRUM - Introduzione Cell. 392/7157684 Disciplined Agile Delivery Italy GroupSCRUM - 42Introduzione
  43. 43. THANKS FOR WATCHINGSCRUM - 43Introduzione