The Zen of Scrum

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

8 comments

Comments 1 - 8 of 8 previous next Post a comment

  • + meddah meddah 2 months ago
    Thanks Jurgen! Great presentation!
  • + sunnyside David Abbott 9 months ago
    Many, many thanks for graciously making this available on your Blog
    David
  • + jurgenappelo Jurgen Appelo 9 months ago
    Hi everyone,

    YOU CAN DOWNLOAD THE PRESENTATION FROM MY BLOG:

    http://www.noop.nl/2009/02/the-zen-of-scrum.html

    (until SlideShare fixed the Download error problem)
  • + dcaron Denise Caron 9 months ago
    For the download error, just send a note to slideshare, I had that problem once and they had to do something to fix it.

    Great slides!
  • + vinthai vinthai 9 months ago
    great presentation but cannot download!
  • + jenshoffmann Jens Hoffmann 9 months ago
    great stuff!
  • + jurgenappelo Jurgen Appelo 9 months ago
    I don’t know. I also get an error message when trying to download the presentation. I have notified the SlideShare support people.
  • + sunnyside David Abbott 9 months ago
    any reason why this excellent presentation won’t download/
Post a comment
Embed Video
Edit your comment Cancel

68 Favorites

The Zen of Scrum - Presentation Transcript

  1. The Zen of Scrum Jurgen Appelo – jurgen@noop.nl version 2 picture by ePi.Longo
  2. Agenda Problems Agile Scrum Roles Scrum Process Hot Issues Results
  3. Problems with traditional software development photo by Jule_Berlin
  4. Traditional
    • Phased development
    • Anticipated results
    • Up-front design
    picture by jasonb42882
  5. Requirements Not Clear
    • Fear to go to the next phase
    • Analysis paralysis
  6. Requirements Change
    • Change gets more and more expensive
    • Customers don’t get what they want
  7. Project Takes Too Long
    • 34% of projects delivered successfully
    • Long duration defers revenue
    • (Source: Standish Report 2003)
  8. No Time for Testing
    • Quality assurance gets crunched
    • Late integration means late failures
  9. Time Wasted on Junk
    • 52% of requirements implemented
    • 64% of functionality rarely used
    • (Source: Standish Report 2003)
  10. Poor Progress Visibility
    • % Task complete not sufficient
    • Average overrun 43%
    • (Source: Standish Report 2003)
  11. Agile software development
  12. Process Complexity (M) Agile projects Chaotic projects Structured projects
  13. Agile Manifesto http:// www.agilemanifesto.org Warning! ugly page
  14. Agile Principles
    • Satisfy the Customer
    • Welcome Change
    • Deliver Frequently
    • Work as a Team
    • Motivate People
    • Communicate Face-to-Face
    • Measure Working Software
    • Maintain Constant Pace
    • Excel at Quality
    • Keep it Simple
    • Evolve Designs
    • Reflect Regularly
  15. Agile Adoption Has Your Organization Adopted One or More Agile Techniques? Agile Adoption Survey 2008 http:// www.ambysoft.com/scottAmbler.html
  16. Agile Adoption
  17. Scrum picture by Kiwi Flickr
  18. The Gurus
    • Ken Schwaber
    • Jeff Sutherland
    • Mike Beedle
    • Mike Cohn
  19. 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
  20. The Goal of Scrum
    • Manage Complexity, Unpredictability and Change
    • through Visibility, Inspection and Adaptation
    picture by OnTask
  21. Scrum Roles picture by exfordy
  22. Product Owner
    • Owner of project vision
    • Represents the customer
    picture by Official Star Wars Blog
  23. Product Owner
    • Define features (according to vision)
    • Prioritize features (according to ROI)
    • Pick release dates
    • Give feedback
    • Manage stakeholders
    • Accept or reject results
  24. The Team
    • Small (5–9 people)
    • Colocated - Cross-functional
    • Self-organized - Full-time
    picture by ewen and donabel
  25. The Team
    • Define tasks
    • Estimate effort
    • Develop product
    • Ensure quality
    • Evolve processes
  26. Scrum Master
    • Servant leader
    • Team protector
    • Troubleshooter
    • Scrum guide
    picture by Orange Beard
  27. Scrum Master
    • Remove impediments
    • Prevent interruptions
    • Facilitate the team
    • Support the process
    • Manage management
  28. Pigs and Chickens Product Owner Scrum Master Team Members Users Managers Marketing
  29. Scrum Process
  30. Product Backlog
    • Express value
    • Defer decisions
    picture by juhansonin
  31. Product Backlog sample from Eclipse.org
  32. 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
  33. Product Backlog Includes rough estimates Prioritized by value & risk Publicly visible Better to describe as user stories
  34. 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
  35. Sprints Timeboxed – Frozen features Variable scope – Shippable result
  36. Sprint Planning
    • Team capacity, Product backlog,
    • Current product, Business, Technologies
    Goal = + picture by Darcy McCarty
  37. Sprint Planning
    • Face-to-face communication
    • Small reversible steps
    • User’s perspective
  38. Sprint Planning (Part 1)
    • Strategical level planning
    • Prioritize/select features
    • Discuss acceptance criteria
    • Verify understanding
    • ½ - 1 hour
    • per sprint/week
  39. 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
  40. Sprint Backlog
    • Breakdown of business value into assignable tasks
    picture by oskay
  41. Sprint Backlog
  42. Sprint Backlog
    • Owned by the team
    • Team allocates work
    • No additions by others
  43. Daily Scrum
    • The heartbeat of Scrum
    picture by Hamed Saber
  44. Daily Scrum
    • Commitment and accountability
    • Say what you do, do what you say
    • Whole world is invited
    picture by Hamed Saber
  45. 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
  46. Task Board picture by Mountain Goat Software Sprint
  47. 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
  48. Sprint Burn Down picture by NibiruTech
  49. Sprint Review
    • Satisfy Product Owner
    • Get feedback on product
    picture by oskay
  50. Sprint Review
    • Informal, no slides
    • Whole team participates
    • The world is invited
    picture by oskay
  51. Sprint Review
    • Preparation needed
    • Show complete features
    • Accept or reject results
    • 1-2 hours
    • per sprint/week
  52. Sprint Retrospective
    • Evolve the process
    picture by kevindooley
  53. Sprint Retrospective
    • Reflect on process and product
    • Whole team participates
  54. Sprint Retrospective
    • What to start doing
    • What to stop doing
    • What to continue doing
    • (Product Owner not required)
  55. Burn Down Chart Scope change
  56. Burn Up Chart Scope keeps expanding Pipeline gets fatter
  57. Release Planning
    • Plan features in sprints and releases
    • Releases depend on accepted sprints
    picture by Sviluppo Agile
  58. Release Sprints
    • Usability testing
    • Documentation
    • Help files
    • Packaging
    pictures by VistaICO
  59. 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
  60. Sprints
    • Steady pull of business value
    • Inspect and Adapt
    picture by kelsey e.
  61. 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.
  62. Hot Issues
  63. Scrum vs. XP picture by extremeprogramming.org
  64. Scrum vs. RUP picture by WittmannClan.com
  65. Scrum vs. PRINCE2 picture by Mike Spain
  66. Scrum vs. Kanban picture by Lean Software Engineering
  67. Scaled Scrum (Scrum of Scrums) picture by Mountain Goat Software
  68. Distributed Scrum
  69. Results effects of applying Scrum
  70. Managed Uncertainty
    • Rolling wave planning
    • Simpler mini-projects lowers risk
  71. Flexible Scope
    • Allow changes at fixed intervals
    • Releases enable learning
  72. Faster Delivery
    • Shorter time to market
    • Value delivered in increments
  73. Higher Quality
    • Testing happens continuously
    • Process improvement built-in
  74. Eliminated Waste
    • Nothing is designed that is not built
    • Nothing is built that is not used
  75. Increased Visibility
    • All problems are made visible
    • Progress is running tested software
    • More Fun, Happy Teams
    picture by woodleywonderworks
  76. Preconditions
    • Empowerment
    • Discipline
    • Courage
    • Stamina
    • Passion
    • Coaching
    • Stable Teams
    • Cross-Functional
    • Available Customer
    picture by mpov
  77. Disclaimer
    • No Engineering Practices
    • Looks Simple, Is Hard
    • No Silver Bullet
    • Not Complete
    • Takes Time
    picture by a2gemma
  78. Books
  79. Sites
    • www.scrumalliance.org
    • www.controlchaos.com
    • www.mountaingoatsoftware.com
    • www.jeffsutherland.com
    • www.implementingscrum.com
    • www.agilesoftwaredevelopment.com
    • www.noop.nl
    picture by VistaICO
  80. Q & A picture by - bast -
  81. @jurgenappelo
  82.  
    • 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 [email_address] .
    http://creativecommons.org/licenses/by-nd/3.0/

+ Jurgen AppeloJurgen Appelo, 9 months ago

custom

8847 views, 68 favs, 29 embeds more stats

The ultimate presentation about Scrum, the world's more

More info about this document

CC Attribution-NoDerivs LicenseCC Attribution-NoDerivs License

Go to text version

  • Total Views 8847
    • 7318 on SlideShare
    • 1529 from embeds
  • Comments 8
  • Favorites 68
  • Downloads 1044
Most viewed embeds
  • 902 views on http://www.noop.nl
  • 256 views on http://www.projectwizards.net
  • 196 views on http://agilblog.locaweb.com.br
  • 85 views on http://www.betterprojects.net
  • 24 views on http://letsme.com

more

All embeds
  • 902 views on http://www.noop.nl
  • 256 views on http://www.projectwizards.net
  • 196 views on http://agilblog.locaweb.com.br
  • 85 views on http://www.betterprojects.net
  • 24 views on http://letsme.com
  • 10 views on http://www.blog.lapidarium42.de
  • 6 views on http://www.tekkie.ro
  • 5 views on http://localhost:8888
  • 5 views on http://www.pmtoolbox.com
  • 4 views on http://www.hanrss.com
  • 3 views on http://gestaolideranca.blogspot.com
  • 3 views on http://fredpalma.com
  • 3 views on http://takacsot.blog.hu
  • 3 views on http://presentations.tumblr.com
  • 3 views on http://www.letsme.com
  • 3 views on http://static.slideshare.net
  • 2 views on http://wiki
  • 2 views on http://confluence.enkigames.com
  • 2 views on https://dare.cib.intranet.db.com
  • 2 views on http://udreka.pl
  • 2 views on http://www.stuartmathews.com
  • 1 views on http://translate.googleusercontent.com
  • 1 views on http://pyovevlibrary.blogspot.com
  • 1 views on http://74.125.47.132
  • 1 views on http://wiki.tibra.com.au
  • 1 views on http://www.slideshare.net
  • 1 views on http://feeds2.feedburner.com
  • 1 views on http://nooperation.typepad.com
  • 1 views on http://www.agglom.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories