Mastering scrum

2,870 views

Published on

Mastering scrum

  1. 1. Mastering Agile GEERT.THEYS@ALTAGE-CONSULT.COM VERSION Beta http://www.flickr.com/photos/fengschwing/3278956517/Thursday 16 December 2010
  2. 2. AgendaThursday 16 December 2010
  3. 3. Agenda The ancient ways Different Agile Styles Scrum Style Results How to test your ScrumThursday 16 December 2010
  4. 4. To improve our kungfu we need to know what went wrong. Po: I know youre trying to be all mystical and Kung Fu- ey, but could you tell me where were going?Thursday 16 December 2010
  5. 5. Traditional Software DevelopmentThursday 16 December 2010
  6. 6. Traditional Software Development Plan everything Stick to the Plan Follow the processThursday 16 December 2010
  7. 7. Building the wrong thing We assume: The customer knows what he wants The Developers know how to build it Nothing will change during executionThursday 16 December 2010
  8. 8. Most IT projects fail 23% 28% What is definition of Succes? Standish Group used : on-time, on-budget and with most of the expected features 49% This is not succes but a failure in estimation. Project success is more about whether the software delivers value thats greater than the cost of the resources put into it - but thats very tricky Succes Challenged to measure. (Martin Fowler) failThursday 16 December 2010
  9. 9. What are the different Agile styles?Thursday 16 December 2010
  10. 10. Scrum & XP Scrum Team Daily Scrum Product Backlog XP Sprint Backlog Collective Whole team Coding Standard Burndown Ownership Chart Customer Pair Planning Refactoring Tests Programming Game Sprint Planning Continous Sustainable Meeting Simple Integration Pace Design Product Owner Metaphor Small Releases Scrum Master Sprint Demo http://blog.crisp.se/henrikkniberg/Thursday 16 December 2010
  11. 11. Agile Assumes We assume: The customer discovers what he wants The developers discovers how to build it Things change on the way http://www.flickr.com/photos/b2tse/3960471608/sizes/o/Thursday 16 December 2010
  12. 12. Let’s focus on SCRUMThursday 16 December 2010
  13. 13. Agile Mind Accepts that predicatbility in business Tries to be predictable software is impossible Fixes Time, Price and scope on projects Time and price are fixed but not the scope Measures succes of project by their Success of the project is measured by the value conformance to plan it gives to the customer Values Methodology and its processes Values people more than the more than the people process, hence it accepts a process instead Resist Change in software requirements and Welcomes Change in software requirements development process and development process Sees the system specification as the generated Sees the system specification as the documentation development codeThursday 16 December 2010
  14. 14. Three Legs Transparancy Inspection Adaption http://www.flickr.com/photos/chrisafer/2427399932/sizes/l/Thursday 16 December 2010
  15. 15. Scrum Roles http://www.flickr.com/photos/clintjcl/305229885/Thursday 16 December 2010
  16. 16. Product OwnerThursday 16 December 2010
  17. 17. Product Owner Must have authority to manage the product log The product owner is not a comitteeThursday 16 December 2010
  18. 18. The TeamThursday 16 December 2010
  19. 19. The Team Self Organised - Cross functional - max 9 membersThursday 16 December 2010
  20. 20. Scrum MasterThursday 16 December 2010
  21. 21. Scrum Master Teaches Scrum by coaching an leading it Removes all impedimentsThursday 16 December 2010
  22. 22. Chicken and PigThursday 16 December 2010
  23. 23. Chicken and Pig Users Product owner Managers Scrum Master Others The TeamThursday 16 December 2010
  24. 24. Scrum ProcessThursday 16 December 2010
  25. 25. Product Backlog First person Shooter Singe Player Multiplayer Player Cooperative Missions Tutorial Online Control Gameplay Split Screen Death Storyline AI MatchThursday 16 December 2010
  26. 26. Product BacklogThursday 16 December 2010
  27. 27. Product Backlog Owned by the product owner Never complete Best-understood requirements Evolves Sorted in order of priorityThursday 16 December 2010
  28. 28. SprintsThursday 16 December 2010
  29. 29. Sprint Planning Defining the sprint length and goal What are we going to build How are we going to build it When will it be “done”Thursday 16 December 2010
  30. 30. Sprint Backlog Owned by the team Team allocates tasks No additions from outside the teamThursday 16 December 2010
  31. 31. TaskboardThursday 16 December 2010
  32. 32. Sprint BurndownThursday 16 December 2010
  33. 33. Daily Standup http://www.flickr.com/photos/jonnimont/3763340830/Thursday 16 December 2010
  34. 34. Daily Standup Answer: What did I do and what am I going to do? Comitment to the team not the Scrum Master Take responsibility on your own work! MAX : 15 and don’t sit down! http://www.flickr.com/photos/jonnimont/3763340830/Thursday 16 December 2010
  35. 35. Sprint Review Everybody is welcome No mockups - Show working code Get feedback on your product Accept or Reject featuresThursday 16 December 2010
  36. 36. Done? Avoid 90% problem General concensus needed what is done... Done should be clear to everyone!Thursday 16 December 2010
  37. 37. Sprint RetrospectiveThursday 16 December 2010
  38. 38. Sprint Retrospective Evolution Good Bad Do more Do LessThursday 16 December 2010
  39. 39. ResultsThursday 16 December 2010
  40. 40. Incremental Change Deliver feature by feature - Highest value first Quick Results - Quick Fail Shorter time to marketThursday 16 December 2010
  41. 41. Flexibility Respond easily to change No danger of missing a deadlineThursday 16 December 2010
  42. 42. Higher Quality Continous testing Continous integration Inspect - AdaptThursday 16 December 2010
  43. 43. More fun - happy teams http://www.flickr.com/photos/mcanevet/289262598/ http://www.flickr.com/photos/32034590@N04/4657598751/Thursday 16 December 2010
  44. 44. Grading your mastery http://www.flickr.com/photos/mcanevet/289262598/Thursday 16 December 2010
  45. 45. Shu-Ha-Ri stages of learning Shu = Follow the rules Ha = Change the rules Ri = Never mind the rulesThursday 16 December 2010
  46. 46. Scrum.orgThursday 16 December 2010
  47. 47. ScrumAlliance Graduate Proffesional Guide Certified Product Owner Certified Scrum Proffesional Certified Scrum Trainer Certified Scrum Master Certified Scrum Developer Certified Scrum CoachThursday 16 December 2010
  48. 48. Questions?Thursday 16 December 2010
  49. 49. slideshare.net/geerttheys twitter/toadi be.linkedin.com/in/gtheys geert.theys@altage-consult.com geerttheys geerttheys.comThursday 16 December 2010
  50. 50. 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 prevention should be changed added or removed, please contact me at geert.theys@altage-consult.com http://creativecommons.org/licenses/by-nd/3.0/Thursday 16 December 2010

×