Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×
Nächste SlideShare
ICT implants
ICT implants
Wird geladen in …3

Hier ansehen

1 von 46 Anzeige

Weitere Verwandte Inhalte

Aktuellste (20)



  1. 1. SCRUM Jeremy Thomas Development Manager Consumer Media active.com
  2. 2. <ul><li>SCRUM is a collaborative approach to building software. Testers, engineers, product developers and even IT work together from start to finish. </li></ul>
  3. 3. <ul><li>SCRUM acknowledges that chaos is present in most system development projects. SCRUM maximizes the amount of chaos a project can embrace and still be successful through collaboration . </li></ul>
  4. 4. <ul><li>chaos = changing market demands, evolving requirements, miscommunication, misinterpretation. </li></ul>
  5. 5. <ul><li> waterfall and chaos don’t get along. </li></ul>
  6. 6. <ul><li>waterfall wants order, predictability, known outcomes, benchmarks. Waterfall wants to predict the future . </li></ul>
  7. 7. <ul><li>and because we’re so in touch with the future, we can anticipate how users will use the system six months from now. </li></ul>
  8. 8. <ul><li>so let’s put together a 300 page requirements document with all of the functionality we can think of. </li></ul>
  9. 9. <ul><li>then we’ll throw it at the code monkeys, I mean engineering team, and project managers to build our system for us. </li></ul>
  10. 10. <ul><li>the project managers, with their hierarchical command and control structure, will divide the work among disparate groups. </li></ul>
  11. 11. <ul><li>these groups will work independently , reporting status back to the command and control center once a week or so. </li></ul>
  12. 12. <ul><li>and three months later, when it comes time for the modules these groups built to talk to each other, they’ll find they speak different languages and can’t communicate . </li></ul>
  13. 13. <ul><li>so they’ll work 80 hour weeks for the next month to fix that little problem. </li></ul>
  14. 14. <ul><li>oh yeah, and they’ll have to push out the project deadline by two months to compensate. </li></ul>
  15. 15. <ul><li>the system will finally be integrated, speaking one universal language, and the engineers will have a celebratory beer . </li></ul>
  16. 16. <ul><li>but then on Monday, when the business takes its first peek at the new system, they’ll organize an emergency meeting with the team leads. </li></ul>
  17. 17. <ul><li>because the system won’t look like what they envisioned five months ago when they predicted the future. </li></ul>
  18. 18. <ul><li>and between now and then things have changed , the business’ customers have demanded new features. </li></ul>
  19. 19. <ul><li>at the meeting the project managers and engineers will defend their positions , citing section numbers in the 300 page requirements document and saying “scope creep” a lot. </li></ul>
  20. 20. <ul><li>concessions will be made, and the company will deliver a product that nobody wants to use. </li></ul>
  21. 21. <ul><li>and they’ll do this after being two months late and over budget . </li></ul>
  22. 22. <ul><li>or we could use SCRUM . </li></ul>
  23. 23. <ul><li>SCRUM divides projects into manageable sprints . </li></ul>
  24. 24. <ul><li>a sprint is a two to four week period where something of business value is delivered at the end. </li></ul>
  25. 25. <ul><li>the project team is involved from start to finish. Design, testing and coding can all happen on the same day . </li></ul>
  26. 26. <ul><li>testers, developers, marketers and product managers intermingle becoming one big happy family. </li></ul>
  27. 27. <ul><li>communication is constant. </li></ul>
  28. 28. <ul><li>each day a 15 to 30 minute SCRUM meeting is held. Managers can watch, but they cannot talk. </li></ul>
  29. 29. <ul><li>during the meeting, each team member answers three questions : </li></ul><ul><ul><li>what did I do since the last SCRUM meeting? </li></ul></ul><ul><ul><li>what has impeded my work? </li></ul></ul><ul><ul><li>what will I do before the next SCRUM meeting? </li></ul></ul>
  30. 30. <ul><li>inter-departmental collaboration </li></ul><ul><li>+ frequent communication </li></ul><ul><li>= transparency . </li></ul>
  31. 31. <ul><li>transparency = reduced risk, better product. </li></ul>
  32. 32. <ul><li>requirements are delivered not in 300 page documents but as user stories . </li></ul>
  33. 33. <ul><li>user stories describe user experiences and have enough detail for SCRUM Masters to estimate effort ( size ). </li></ul>
  34. 34. <ul><li>A sample user story is “A consumer can upload and play videos on the website” </li></ul>
  35. 35. <ul><li>A sample user story is “A consumer can upload and play videos on the website” </li></ul>
  36. 36. <ul><li>The SCRUM team then adds detail to the user story during the course of the project and clarifies ambiguity . </li></ul>
  37. 37. <ul><li>User stories emphasize verbal communication . </li></ul>
  38. 38. <ul><li>“ Entrée comes with choice of soup or salad and bread”. </li></ul>
  39. 39. <ul><li>Does this mean: </li></ul><ul><li>Soup or (salad and bread) </li></ul><ul><li>(Soup or salad) and bread </li></ul><ul><li>http://www.mountaingoatsoftware.com/article_view/27-advantages-of-user-stories-for-requirements </li></ul>
  40. 40. <ul><li>The SCRUM Master has Authority over what details are permissible. His goal is to deliver at the end of the Sprint. </li></ul>
  41. 41. <ul><li>He has no friends . He makes the business prioritize. He makes the developers compromise. </li></ul>
  42. 42. <ul><li>At the end of the sprint the team shows off what they’ve done to the rest of the business. </li></ul>
  43. 43. <ul><li>The stakeholders already knew what they were getting and are happy . </li></ul>
  44. 44. <ul><li>The developers are happy too because they built something the business can use. </li></ul>
  45. 45. <ul><li>And everybody goes home to rest . Well at least until the next sprint begins... </li></ul>