The Zen of Scrum

82,248
-1

Published on

The ultimate presentation about Scrum, the world's leading project management framework for agile software development.

http://www.noop.nl
http://www.jurgenappelo.com

30 Comments
411 Likes
Statistics
Notes
No Downloads
Views
Total Views
82,248
On Slideshare
0
From Embeds
0
Number of Embeds
94
Actions
Shares
0
Downloads
9,402
Comments
30
Likes
411
Embeds 0
No embeds

No notes for slide

The Zen of Scrum

  1. The Zen of Scrum Jurgen Appelo – jurgen@noop.nl version 4 picture by ePi.Longo
  2. Jurgen Appelo writer, speaker, entrepreneur... www.jurgenappelo.com
  3. Get my new book for FREE! m30.me/ss
  4. Problems Agile Scrum Roles Scrum Process Hot Issues Results Agenda
  5. Problems with traditional software development photo by Jule_Berlin
  6. Traditional Phased development Anticipated results Up-front design picture by jasonb42882
  7. Requirements Not Clear Fear to go to the next phase Analysis paralysis
  8. Requirements Change Change gets more and more expensive Customers don’t get what they want
  9. Project Takes Too Long 32% of projects delivered successfully Long duration defers revenue (Source: Standish Report 2009)
  10. No Time for Testing Quality assurance gets crunched Late integration means late failures
  11. Time Wasted on Junk 52% of requirements implemented 64% of functionality rarely used (Source: Standish Report 2003)
  12. Poor Progress Visibility % Task complete not sufficient Average overrun 43% (Source: Standish Report 2003)
  13. Agile software development
  14. Process Complexity (M) Agile projects Chaotic projects Structured projects
  15. Agile Principles 1. Satisfy the Customer 2. Welcome Change 3. Deliver Frequently 4. Work as a Team 5. Motivate People 6. Communicate Face-to-Face 7. Measure Working Software 8. Maintain Constant Pace 9. Excel at Quality 10. Keep it Simple 11. Evolve Designs 12. Reflect Regularly
  16. Agile Adoption
  17. Agile Adoption
  18. Scrum picture by Kiwi Flickr
  19. The Gurus Ken Schwaber Jeff Sutherland Mike Beedle Mike Cohn
  20. 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 use http://www.mountaingoatsoftware.com
  21. The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation picture by OnTask
  22. Scrum Roles picture by exfordy
  23. Product Owner Owner of project vision Represents the customerpicture by Official Star Wars Blog
  24. Product Owner Define features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results
  25. The Team Small (5–9 people) Colocated - Cross-functional Self-organized - Full-timepicture by ewen and donabel
  26. The Team Define tasks Estimate effort Develop product Ensure quality Evolve processes
  27. Scrum Master Servant leader Team protector Troubleshooter Scrum guide picture by Orange Beard
  28. Scrum Master Remove impediments Prevent interruptions Facilitate the team Support the process Manage management
  29. Pigs and Chickens Product Owner Scrum Master Team Members Users Managers Marketing
  30. Scrum Process
  31. Product Backlog Express value Defer decisions picture by juhansonin
  32. Product Backlog sample from Eclipse.org
  33. Product Backlog Owned by Product Owner High-level requirements Expressed as business value Not complete, nor perfect Expected to change & evolve Limited view into the future
  34. Product Backlog Includes rough estimates Prioritized by value & risk Publicly visible Better to describe as user stories
  35. User Stories As a <user> I want <functionality> ( so that <benefit> ) As a librarian I want to be able to search for books by publication year
  36. Sprints Timeboxed – Frozen features Variable scope – Shippable result
  37. Sprint Planning Team capacity, Product backlog, Current product, Business, Technologies Goal = + picture by Darcy McCarty
  38. Sprint Planning Face-to-face communication Small reversible steps User’s perspective
  39. Sprint Planning (Part 1) Strategical level planning Prioritize/select features Discuss acceptance criteria Verify understanding ½ - 1 hour per sprint/week
  40. Sprint Planning (Part 2) Tactical level planning Define sprint backlog items Estimate sprint backlog items Use velocity (Yesterday’s Weather) Share commitment ½ - 1 hour per sprint/week
  41. Sprint Backlog Breakdown of business value into assignable tasks picture by oskay
  42. Sprint Backlog
  43. Sprint Backlog Owned by the team Team allocates work No additions by others
  44. Daily Scrum The heartbeat of Scrum picture by Hamed Saber
  45. Daily Scrum picture by Hamed Saber Commitment and accountability Say what you do, do what you say Whole world is invited
  46. Daily Scrum What I did since last meeting What I will do until next meeting What things are in my way Only the team talks Not to Scrum Master No problem solving Max 15 minutes Standing up
  47. Task Board picture by Mountain Goat Software Sprint
  48. Definition of Done Avoid the 90% syndrome Coded, commented, checked in, integrated, reviewed, unit tested, deployed to test environment, passed user acceptance test & documented... = DONE DONE
  49. Sprint Burn Down picture by NibiruTech
  50. Sprint Review Satisfy Product Owner Get feedback on productpicture by oskay
  51. Sprint Review picture by oskay Informal, no slides Whole team participates The world is invited
  52. Sprint Review Preparation needed Show complete features Accept or reject results 1-2 hours per sprint/week
  53. Sprint Retrospective Evolve the process picture by kevindooley
  54. Sprint Retrospective Reflect on process and product Whole team participates
  55. Sprint Retrospective What to start doing What to stop doing What to continue doing (Product Owner not required)
  56. Burn Down Chart -40 -20 0 20 40 60 80 100 120 7-1-08 14-1-08 21-1-08 28-1-08 4-2-08 11-2-08 18-2-08 25-2-08 3-3-08 10-3-08 17-3-08 24-3-08 31-3-08 7-4-08 14-4-08 Features Features Remaining Scope Target Scope change
  57. Burn Up Chart Scope keeps expanding Pipeline gets fatter
  58. Release Planning Plan features in sprints and releases Releases depend on accepted sprints picture by Sviluppo Agile
  59. Release Sprints Usability testing Documentation Help files Packaging pictures by VistaICO
  60. 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 problems picture by VistaICO
  61. Sprints Steady pull of business value Inspect and Adaptpicture by kelsey e.
  62. Sprints picture by kelsey e. 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”
  63. Hot Issues
  64. Scrum vs. XP picture by extremeprogramming.org
  65. Scrum vs. RUP picture by WittmannClan.com
  66. Scrum vs. PRINCE2 picture by Mike Spain
  67. Scrum vs. Kanban picture by Lean Software Engineering
  68. Scaled Scrum (Scrum of Scrums) picture by Mountain Goat Software
  69. Distributed Scrum
  70. Results effects of applying Scrum
  71. Managed Uncertainty Rolling wave planning Simpler mini-projects lowers risk
  72. Flexible Scope Allow changes at fixed intervals Releases enable learning
  73. Faster Delivery Shorter time to market Value delivered in increments
  74. Higher Quality Testing happens continuously Process improvement built-in
  75. Eliminated Waste Nothing is designed that is not built Nothing is built that is not used
  76. Increased Visibility All problems are made visible Progress is running tested software
  77. More Fun, Happy Teams picture by woodleywonderworks
  78. Preconditions Empowerment Discipline Courage Stamina Passion Coaching Stable Teams Cross-Functional Available Customer picture by mpov
  79. Disclaimer No Engineering Practices Looks Simple, Is Hard No Silver Bullet Not Complete Takes Time picture by a2gemma
  80. Books
  81. Sites www.scrumalliance.org www.scrum.org www.mountaingoatsoftware.com www.agilesoftwaredevelopment.com www.noop.nl picture by VistaICO
  82. picture by -bast- Q & A
  83. @jurgenappelo slideshare.net/jurgenappelo noop.nl linkedin.com/in/jurgenappelo jurgen@noop.nl
  84. www.management30.com
  85. http://creativecommons.org/licenses/by-nd/3.0/ This presentation was inspired by the works of many people, and I cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights, if you think that anything in this presentation should be changed, added or removed, please contact me at jurgen@noop.nl.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×