Uploaded byAdrian Treacy
Thezenofscrum1 090221154550 Phpapp01
Scrum is an agile framework for managing complex work. It is iterative and incremental, promotes transparency and adaptation, and limits work in progress. The core Scrum roles are the Product Owner, Development Team, and Scrum Master. The Scrum process involves sprints, daily stand-ups, sprint planning and review meetings, and retrospectives to continuously improve. Scrum aims to deliver value to customers faster through self-organizing cross-functional teams and empiricism.
More Related Content
Similar to Thezenofscrum1 090221154550 Phpapp01
Thezenofscrum1 090221154550 Phpapp01
- 1. The Zen ofScrum Jurgen Appelo – jurgen@noop.nl version 3 picture by ePi.Longo
- 2. Problems Agenda Agile Scrum Roles Scrum Process Hot Issues Results
- 3. Problems photo by Jule_Berlin with traditional software development
- 4. Traditional Phased development Anticipated results Up-frontdesign picture by jasonb42882
- 5. Requirements Not Clear Fearto go to the next phase Analysis paralysis
- 6. Requirements Change Change getsmore and more expensive Customers don’t get what they want
- 7. Project Takes TooLong 32% of projects delivered successfully Long duration defers revenue (Source: Standish Report 2009)
- 8. No Time forTesting Quality assurance gets crunched Late integration means late failures
- 9. Time Wasted onJunk 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.
- 12. Process Complexity (M) Chaotic projects Agile projects Structured projects
- 14. 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
- 15.
- 16.
- 17. Scrum picture by KiwiFlickr
- 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. picture by OnTask The Goal of Scrum Manage Complexity, Unpredictability and Change through Visibility, Inspection and Adaptation
- 21. Scrum picture by exfordy Roles
- 22. Product Owner Owner of project vision picture by Official Star Wars Blog Represents the customer
- 23. Product Owner Define features (accordingto 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 picture by ewen and donabel Self-organized - Full-time
- 25. The Team Define tasks Estimateeffort 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 Facilitatethe team Support the process Manage management
- 28. Pigs and Chickens ProductOwner Users Scrum Master Managers Team Members Marketing
- 29.
- 30. Product Backlog Express value Defer decisions picture by juhansonin
- 31. Product Backlog sample from Eclipse.org
- 32. Product Backlog Owned byProduct 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 Better to describe Publicly as user stories visible
- 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 Smallreversible steps User’s perspective
- 38. Sprint Planning (Part1) Strategical level planning Prioritize/select features Discuss acceptance criteria Verify understanding ½ - 1 hour per sprint/week
- 39. Sprint Planning (Part2) 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.
- 42. Sprint Backlog Owned bythe team Team allocates work No additions by others
- 43. Daily Scrum The heartbeatof Scrum picture by Hamed Saber
- 44. Daily Scrum Commitment andaccountability Say what you do, do what you say Whole world is invited picture by Hamed Saber
- 45. Daily Scrum What Idid 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. Sprint Task Board picture by Mountain Goat Software
- 47. Definition of Done Avoidthe 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 pictureby NibiruTech
- 49. Sprint Review Satisfy Product Owner picture by oskay Get feedback on product
- 50. Sprint Review Informal, no slides Whole team participates The world is invited picture by oskay
- 51. Sprint Review Preparation needed Showcomplete 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 processand product Whole team participates
- 54. Sprint Retrospective What tostart doing What to stop doing What to continue doing (Product Owner not required)
- 55. Features -40 -20 100 120 0 20 40 60 80 7-1-08 14-1-08 21-1-08 28-1-08 4-2-08 11-2-08 18-2-08 Scope change 25-2-08 Features Remaining 3-3-08 10-3-08 17-3-08 Scope Target 24-3-08 31-3-08 Burn Down Chart 7-4-08 14-4-08
- 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 picture by kelsey e. Inspect and Adapt
- 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.
- 63. Scrum vs. XP pictureby extremeprogramming.org
- 64. Scrum vs. RUP pictureby WittmannClan.com
- 65. Scrum vs. PRINCE2 pictureby Mike Spain
- 66. Scrum vs. Kanban pictureby Lean Software Engineering
- 67. Scaled Scrum (Scrum of Scrums) picture by Mountain Goat Software
- 68.
- 69. Results effects of applying Scrum
- 70. Managed Uncertainty Rolling waveplanning Simpler mini-projects lowers risk
- 71. Flexible Scope Allow changesat fixed intervals Releases enable learning
- 72. Faster Delivery Shorter timeto market Value delivered in increments
- 73. Higher Quality Testing happenscontinuously Process improvement built-in
- 74. Eliminated Waste Nothing isdesigned that is not built Nothing is built that is not used
- 75. Increased Visibility All problemsare made visible Progress is running tested software
- 76. More Fun, HappyTeams picture by woodleywonderworks
- 77.
- 78. Disclaimer No Engineering Practices Looks Simple, Is Hard No Silver Bullet Not Complete Takes Time picture by a2gemma
- 79.
- 80. Sites www.scrumalliance.org www.scrum.org www.mountaingoatsoftware.com www.agilesoftwaredevelopment.com www.noop.nl picture by VistaICO
- 81. slideshare.net/jurgenappelo @jurgenappelo (twitter) noop.nl (blog) jurgenappelo.com(site) management30.com (book)
- 82.
- 83. This presentation wasinspired 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. http://creativecommons.org/licenses/by-nd/3.0/