The Zen of Scrum                        Jurgen Appelo – jurgen@noop.nl                                    version 3picture...
Problems        AgendaAgileScrum RolesScrum ProcessHot IssuesResults
Problemsphoto by Jule_Berlin                       with traditional software                             development
TraditionalPhased developmentAnticipated resultsUp-front design   picture by jasonb42882
Requirements Not ClearFear to go to the next phaseAnalysis paralysis
Requirements ChangeChange gets more and more expensiveCustomers don’t get what they want
Project Takes Too Long32% of projects delivered successfullyLong duration defers revenue(Source: Standish Report 2009)
No Time for TestingQuality assurance gets crunchedLate integration means late failures
Time Wasted on Junk52% of requirements implemented64% of functionality rarely used(Source: Standish Report 2003)
Poor Progress Visibility% Task complete not sufficientAverage overrun 43%(Source: Standish Report 2003)
Agile  softwaredevelopment
Process Complexity (M)                        Chaotic                        projects                     Agile           ...
Agile Principles1.    Satisfy the Customer2.    Welcome Change3.    Deliver Frequently4.    Work as a Team5.    Motivate P...
Agile Adoption
Agile Adoption
Scrumpicture by Kiwi Flickr
The GurusKen Schwaber        Jeff Sutherland                     Mike Beedle                               Mike Cohn
Scrum Usage       Commercial software - In-house development       Contract development - Fixed-price projects       Finan...
picture by OnTask                    The Goal                    of Scrum     Manage Complexity, Unpredictability and Chan...
Scrumpicture by exfordy                     Roles
Product    Owner                                      Owner of project visionpicture by Official Star Wars Blog   Represen...
ProductOwnerDefine features (according to vision)Prioritize features (according to ROI)Pick release datesGive feedbackMana...
The                                       Team                                  Small (5–9 people)                        ...
The TeamDefine tasksEstimate effortDevelop productEnsure qualityEvolve processes
ScrumMaster          Servant leader         Team protector         Troubleshooter            Scrum guide                 p...
ScrumMasterRemove impedimentsPrevent interruptionsFacilitate the teamSupport the processManage management
Scrum Process
Product Backlog                  sample from Eclipse.org
Product BacklogOwned by Product OwnerHigh-level requirementsExpressed as business valueNot complete, nor perfectExpected t...
Product Backlog                     Includes rough                       estimatesPrioritized by value & riskBetter to des...
User StoriesAs a <user> I want <functionality> ( so that <benefit> )As a librarian I want to be able to search for books b...
Sprints  Timeboxed – Frozen featuresVariable scope – Shippable result
Sprint PlanningTeam capacity, Product backlog,Current product, Business, Technologies          +Goal                      ...
Sprint PlanningFace-to-face communicationSmall reversible stepsUser’s perspective
Sprint Planning (Part 1)Strategical level planningPrioritize/select featuresDiscuss acceptance criteriaVerify understandin...
Sprint Planning (Part 2)Tactical level planningDefine sprint backlog itemsEstimate sprint backlog itemsUse velocity (Yeste...
Sprint Backlog                           Breakdown of                      business value into                        assi...
Sprint Backlog
Sprint BacklogOwned by the teamTeam allocates workNo additions by others
Daily ScrumThe heartbeat of Scrum                         picture by Hamed Saber
Daily ScrumCommitment and accountabilitySay what you do, do what you sayWhole world is invited                            ...
Daily ScrumWhat I did since last meetingWhat I will do until next meetingWhat things are in my wayOnly the team talksNot t...
Sprint         Task Board   picture by Mountain Goat Software
Definition of DoneAvoid the 90% syndromeCoded, commented, checked in, integrated, reviewed, unit tested, deployed to test ...
Sprint Burn Downpicture by NibiruTech
Sprint Review                      Satisfy Product Ownerpicture by oskay                    Get feedback on product
Sprint Review                   Informal, no slides                   Whole team participates                   The world ...
Sprint ReviewPreparation neededShow complete featuresAccept or reject results1-2 hoursper sprint/week
Sprint     Retrospective                         Evolve the processpicture by kevindooley
SprintRetrospectiveReflect on process and productWhole team participates
Sprint RetrospectiveWhat to start doingWhat to stop doingWhat to continue doing(Product Owner not required)
Burn Down Chart     Scope    change
Burn Up Chart  Scope keeps   expanding      Pipeline gets         fatter
Release Planning        Plan features in sprints and releases        Releases depend on accepted sprintspicture by Svilupp...
Release Sprints        Usability testing        Documentation        Help files        Packagingpictures by VistaICO
Sprint Termination        Only in extreme cases        Team terminates: cannot meet sprint goal        Product Owner termi...
Sprints                       Steady pull of business valuepicture by kelsey e.        Inspect and Adapt
Sprints                        Driven by Product Owner                            Small reversible steps                  ...
Results    effects of applying Scrum
Managed UncertaintyRolling wave planningSimpler mini-projects lowers risk
Flexible ScopeAllow changes at fixed intervalsReleases enable learning
Faster DeliveryShorter time to marketValue delivered in increments
Higher QualityTesting happens continuouslyProcess improvement built-in
Eliminated WasteNothing is designed that is not builtNothing is built that is not used
Increased VisibilityAll problems are made visibleProgress is running tested software
More Fun, Happy Teamspicture by woodleywonderworks
PreconditionsEmpowermentDisciplineCourageStaminaPassionCoachingStable TeamsCross-FunctionalAvailable Customer             ...
Disclaimer                     No Engineering Practices                        Looks Simple, Is Hard                      ...
Q&Apicture by -bast-
Sites        www.scrumalliance.org        www.scrum.org        www.mountaingoatsoftware.com        www.agilesoftwaredevelo...
This presentation was inspired by the works of many people, and Icannot possibly list them all. Though I did my very best ...
Thezenofscrum1 090221154550-phpapp01
Upcoming SlideShare
Loading in …5
×

Thezenofscrum1 090221154550-phpapp01

533 views
475 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
533
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Thezenofscrum1 090221154550-phpapp01

    1. 1. The Zen of Scrum Jurgen Appelo – jurgen@noop.nl version 3picture by ePi.Longo
    2. 2. Problems AgendaAgileScrum RolesScrum ProcessHot IssuesResults
    3. 3. Problemsphoto by Jule_Berlin with traditional software development
    4. 4. TraditionalPhased developmentAnticipated resultsUp-front design picture by jasonb42882
    5. 5. Requirements Not ClearFear to go to the next phaseAnalysis paralysis
    6. 6. Requirements ChangeChange gets more and more expensiveCustomers don’t get what they want
    7. 7. Project Takes Too Long32% of projects delivered successfullyLong duration defers revenue(Source: Standish Report 2009)
    8. 8. No Time for TestingQuality assurance gets crunchedLate integration means late failures
    9. 9. Time Wasted on Junk52% of requirements implemented64% of functionality rarely used(Source: Standish Report 2003)
    10. 10. Poor Progress Visibility% Task complete not sufficientAverage overrun 43%(Source: Standish Report 2003)
    11. 11. Agile softwaredevelopment
    12. 12. Process Complexity (M) Chaotic projects Agile projects Structured projects
    13. 13. Agile Principles1. Satisfy the Customer2. Welcome Change3. Deliver Frequently4. Work as a Team5. Motivate People6. Communicate Face-to-Face7. Measure Working Software8. Maintain Constant Pace9. Excel at Quality10. Keep it Simple11. Evolve Designs12. Reflect Regularly
    14. 14. Agile Adoption
    15. 15. Agile Adoption
    16. 16. Scrumpicture by Kiwi Flickr
    17. 17. The GurusKen Schwaber Jeff Sutherland Mike Beedle Mike Cohn
    18. 18. Scrum Usage Commercial software - In-house development Contract development - Fixed-price projects Financial applications - ISO 9001-certified applications Embedded systems - 24x7 systems with 99.999% uptime Joint Strike Fighter - Video game development FDA-approved, life-critical systems - Web sites Satellite-control software - Handheld software Mobile phones - Network switching applications ISV applications - Some of the largest applications in usehttp://www.mountaingoatsoftware.com
    19. 19. picture by OnTask The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation
    20. 20. Scrumpicture by exfordy Roles
    21. 21. Product Owner Owner of project visionpicture by Official Star Wars Blog Represents the customer
    22. 22. ProductOwnerDefine features (according to vision)Prioritize features (according to ROI)Pick release datesGive feedbackManage stakeholdersAccept or reject results
    23. 23. The Team Small (5–9 people) Colocated - Cross-functionalpicture by ewen and donabel Self-organized - Full-time
    24. 24. The TeamDefine tasksEstimate effortDevelop productEnsure qualityEvolve processes
    25. 25. ScrumMaster Servant leader Team protector Troubleshooter Scrum guide picture by Orange Beard
    26. 26. ScrumMasterRemove impedimentsPrevent interruptionsFacilitate the teamSupport the processManage management
    27. 27. Scrum Process
    28. 28. Product Backlog sample from Eclipse.org
    29. 29. Product BacklogOwned by Product OwnerHigh-level requirementsExpressed as business valueNot complete, nor perfectExpected to change & evolveLimited view into the future
    30. 30. Product Backlog Includes rough estimatesPrioritized by value & riskBetter to describe Publicly as user stories visible
    31. 31. User StoriesAs a <user> I want <functionality> ( so that <benefit> )As a librarian I want to be able to search for books by publication year
    32. 32. Sprints Timeboxed – Frozen featuresVariable scope – Shippable result
    33. 33. Sprint PlanningTeam capacity, Product backlog,Current product, Business, Technologies +Goal = picture by Darcy McCarty
    34. 34. Sprint PlanningFace-to-face communicationSmall reversible stepsUser’s perspective
    35. 35. Sprint Planning (Part 1)Strategical level planningPrioritize/select featuresDiscuss acceptance criteriaVerify understanding½ - 1 hourper sprint/week
    36. 36. Sprint Planning (Part 2)Tactical level planningDefine sprint backlog itemsEstimate sprint backlog itemsUse velocity (Yesterday’s Weather)Share commitment½ - 1 hourper sprint/week
    37. 37. Sprint Backlog Breakdown of business value into assignable taskspicture by oskay
    38. 38. Sprint Backlog
    39. 39. Sprint BacklogOwned by the teamTeam allocates workNo additions by others
    40. 40. Daily ScrumThe heartbeat of Scrum picture by Hamed Saber
    41. 41. Daily ScrumCommitment and accountabilitySay what you do, do what you sayWhole world is invited picture by Hamed Saber
    42. 42. Daily ScrumWhat I did since last meetingWhat I will do until next meetingWhat things are in my wayOnly the team talksNot to Scrum MasterNo problem solvingMax 15 minutesStanding up
    43. 43. Sprint Task Board picture by Mountain Goat Software
    44. 44. Definition of DoneAvoid the 90% syndromeCoded, commented, checked in, integrated, reviewed, unit tested, deployed to test environment, passed user acceptance test & documented...= DONE DONE
    45. 45. Sprint Burn Downpicture by NibiruTech
    46. 46. Sprint Review Satisfy Product Ownerpicture by oskay Get feedback on product
    47. 47. Sprint Review Informal, no slides Whole team participates The world is invitedpicture by oskay
    48. 48. Sprint ReviewPreparation neededShow complete featuresAccept or reject results1-2 hoursper sprint/week
    49. 49. Sprint Retrospective Evolve the processpicture by kevindooley
    50. 50. SprintRetrospectiveReflect on process and productWhole team participates
    51. 51. Sprint RetrospectiveWhat to start doingWhat to stop doingWhat to continue doing(Product Owner not required)
    52. 52. Burn Down Chart Scope change
    53. 53. Burn Up Chart Scope keeps expanding Pipeline gets fatter
    54. 54. Release Planning Plan features in sprints and releases Releases depend on accepted sprintspicture by Sviluppo Agile
    55. 55. Release Sprints Usability testing Documentation Help files Packagingpictures by VistaICO
    56. 56. Sprint Termination Only in extreme cases Team terminates: cannot meet sprint goal Product Owner terminates: priority change Work reverted to end of prior sprint Raises visibility of problemspicture by VistaICO
    57. 57. Sprints Steady pull of business valuepicture by kelsey e. Inspect and Adapt
    58. 58. Sprints Driven by Product Owner Small reversible steps Welcome change Cross-functional team Include design and testing Maintain constant pace Share commitment High quality, DONE Get feedback “Fail fast”picture by kelsey e.
    59. 59. Results effects of applying Scrum
    60. 60. Managed UncertaintyRolling wave planningSimpler mini-projects lowers risk
    61. 61. Flexible ScopeAllow changes at fixed intervalsReleases enable learning
    62. 62. Faster DeliveryShorter time to marketValue delivered in increments
    63. 63. Higher QualityTesting happens continuouslyProcess improvement built-in
    64. 64. Eliminated WasteNothing is designed that is not builtNothing is built that is not used
    65. 65. Increased VisibilityAll problems are made visibleProgress is running tested software
    66. 66. More Fun, Happy Teamspicture by woodleywonderworks
    67. 67. PreconditionsEmpowermentDisciplineCourageStaminaPassionCoachingStable TeamsCross-FunctionalAvailable Customer picture by mpov
    68. 68. Disclaimer No Engineering Practices Looks Simple, Is Hard No Silver Bullet Not Complete Takes Timepicture by a2gemma
    69. 69. Q&Apicture by -bast-
    70. 70. Sites www.scrumalliance.org www.scrum.org www.mountaingoatsoftware.com www.agilesoftwaredevelopment.com www.noop.nlpicture by VistaICO
    71. 71. This presentation was inspired by the works of many people, and Icannot possibly list them all. Though I did my very best to attributeall authors of texts and images, and to recognize any copyrights, ifyou think that anything in this presentation should be changed,added or removed, please contact me at jurgen@noop.nl.http://creativecommons.org/licenses/by-nd/3.0/

    ×