Scrum

2,612 views

Published on

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

No Downloads
Views
Total views
2,612
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
128
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Scrum

  1. 1. Scrum An introduction Tricode Professional Services www.tricode.nl 03-04-2009 Sander van Beek
  2. 2. What is Scrum? <ul><li>An adaptive framework that can be understood and implemented in a few days </li></ul><ul><li>Optimized for new product development </li></ul><ul><li>A collaborative effort involving developers and customers in ongoing dialog </li></ul><ul><li>A management wrapper around existing engineering practices, driving incremental improvements. </li></ul>
  3. 3. What is Scrum NOT? <ul><li>Entirely new </li></ul><ul><li>A silver bullet </li></ul><ul><li>Scrum does not handle </li></ul><ul><ul><li>Raises, promotions, job titles </li></ul></ul><ul><ul><li>A team member is incompetent, lazy, etc </li></ul></ul><ul><ul><li>Half the team is in India </li></ul></ul><ul><ul><li>PRINCE2, CMMI, ISO9000, Sarbanes Oxley, etc </li></ul></ul><ul><ul><li>The scrum master is allergic to cats </li></ul></ul>
  4. 4. Small teams, short iterations, clear goals
  5. 5. Scrum process
  6. 6. Artifacts
  7. 7. The product backlog <ul><li>Contains user stories (!= use cases) </li></ul><ul><ul><li>As a ... I want ... so that i can ... (functionality) </li></ul></ul><ul><li>Each user story contains </li></ul><ul><ul><li>Description </li></ul></ul><ul><ul><li>Estimate </li></ul></ul><ul><ul><li>Definition of done (DoD) </li></ul></ul><ul><ul><li>Business value </li></ul></ul><ul><li>Prioritized on </li></ul><ul><li>business value </li></ul>
  8. 8. The sprint backlog <ul><li>User stories split up into tasks </li></ul><ul><li>Every sprint must yield something to demonstrate -> vertical slice of the product (e.g. Only hello world is enough) </li></ul><ul><li>Tasks include analyse, design, build, test </li></ul>
  9. 9. Burndown chart <ul><li>Shows progress, work to be done, work added </li></ul><ul><li>Velocity </li></ul>
  10. 10. Roles
  11. 11. Roles in scrum <ul><li>Product owner </li></ul><ul><li>Scrum master (!= project manager) </li></ul><ul><li>Scrum team </li></ul>
  12. 12. Product owner <ul><li>Single point of contact for stakeholders </li></ul><ul><li>Synthesizes interests of stakeholders </li></ul><ul><li>Makes business decisions </li></ul><ul><li>Keeps eye on business value </li></ul><ul><li>Accepts or rejects result of a sprint </li></ul><ul><li>Decides wether to ship </li></ul>
  13. 13. Scrum master <ul><li>Facilitates the Scrum process </li></ul><ul><li>Takes away impediments, shields team </li></ul><ul><li>Helps team self organizing </li></ul><ul><li>Helps product owner with prioritizing </li></ul><ul><li>Advocates improved engineering practices </li></ul><ul><li>Has NO authority </li></ul>
  14. 14. Scrum team <ul><li>Cross functional (designers, developers, testers, etc) </li></ul><ul><li>Self organizing </li></ul><ul><li>Autonomous </li></ul><ul><li>Held responsible for commitments </li></ul><ul><li>+/- 7 members (min 5, max 9) </li></ul>
  15. 15. Meetings
  16. 16. Meetings in scrum
  17. 17. Sprint planning meeting <ul><li>Add estimates to user stories </li></ul><ul><li>Moving PBI’s to spring backlog </li></ul>
  18. 18. Daily scrum <ul><li>Timeboxed to max 15 minutes </li></ul><ul><li>Stand up meeting </li></ul><ul><li>3 questions: </li></ul><ul><ul><li>What did I do yesterday? </li></ul></ul><ul><ul><li>What will I do to today? </li></ul></ul><ul><ul><li>What problems did I encounter that prevent me from doing my work? </li></ul></ul>
  19. 19. Sprint review <ul><li>Present the sprint product </li></ul><ul><li>Includes stakeholders </li></ul><ul><li>Approval of backlog items implemented </li></ul><ul><li>New feature requests added to product backlog </li></ul>
  20. 20. Sprint retrospective <ul><li>What went well / what could be improved </li></ul><ul><li>Silent writing </li></ul><ul><li>Combined with coach meeting? </li></ul>
  21. 21. Backlog refinement <ul><li>Every time when changes occur on the backlog </li></ul><ul><li>Scrum master advises on dependencies </li></ul>
  22. 22. Now you know Scrum!
  23. 23. When to use Scrum?
  24. 24. Scrum vs Waterfall
  25. 25. Scrum vs Waterfall (2) <ul><li>feedback loop </li></ul>
  26. 26. Timeboxing <ul><li>Requirements </li></ul><ul><li>Time (fixed) </li></ul><ul><li>People (fixed) </li></ul>
  27. 27. Technical debt
  28. 28. Converging burndown chart
  29. 29. Planning & estimation <ul><li>Estimation poker </li></ul><ul><li>S, M, L, XL (epic) </li></ul><ul><li>Relative distances </li></ul><ul><li>Learning from others </li></ul>
  30. 30. Stories <ul><li>Non technical! </li></ul><ul><li>Definition of done </li></ul>
  31. 31. Stories (2)
  32. 32. Good practices that go with scrum <ul><li>Continuous refactoring </li></ul><ul><li>Test driven development </li></ul><ul><ul><li>Unit tests vs System tests </li></ul></ul><ul><li>Continuous integration </li></ul><ul><li>Pair programming </li></ul>
  33. 33. Advantages of Scrum for the business <ul><li>Maximize business value </li></ul><ul><li>Early warning when deadlines will not be met (if you fail fail as early as possible) </li></ul><ul><li>Better end product </li></ul><ul><li>A working product very quickly </li></ul>
  34. 34. Advantages of Scrum for developers <ul><li>Clear goals </li></ul><ul><li>Focus on your real work </li></ul><ul><li>Choose the work you like </li></ul><ul><li>Responsability </li></ul><ul><li>Not a peon </li></ul>

×