Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum in the Wild at #dpc10

1,684 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Scrum in the Wild at #dpc10

  1. 1. SCRUM in the Wild Photo taken by Maree Reveley (aka Somerslea)
  2. 2. Technical Lead at Unet B.V. Mike van Riel ● ● Using PHP for 8 years http://www.joind.in/talk/view/1756 @mvriel ● Working with SCRUM for 3 years 2 / 35
  3. 3. Introduction 3 / 35
  4. 4. Who are you? Photo taken by Xavier de Cock 4 / 35
  5. 5. What is SCRUM? http://www.flickr.com/photos/darwinbell/ 5 / 35
  6. 6. Framework, not methodology http://www.flickr.com/photos/vinayshivakumar/3194015535/ 6 / 35
  7. 7. Believe http://www.flickr.com/photos/jstar/207421635/ 7 / 35
  8. 8. Traditional METHODS vs. SCRUM 8 / 35
  9. 9. Waterfall ● Originates from hardware industry ● Set in stone, not flexible ● No feedback ● False feeling of knowing ● Works with large teams 9 / 35
  10. 10. One release to rule them all 10 / 35
  11. 11. SCRUM ● Originates from product development ● Timeboxed iterations ● Maximum feedback ● Provides great insight ● Seldom works with large teams http://blog.3months.com/2010/01/10/illustrating-scrum-a-new-and-improved-scrum-diagram/ 11 / 35
  12. 12. Release early, release often 12 / 35
  13. 13. History http://www.flickr.com/photos/kevan/ 13 / 35
  14. 14. Hirotaka Takeuchi & Ikojiru Nonaka http://www.flickr.com/photos/kevan/ 14 / 35
  15. 15. Ken Schwaber, Jeff Sutherland, John Scumniotales & Jeff McKenna http://www.flickr.com/photos/kevan/ 15 / 35
  16. 16. Why did we choose to go for scrum ● Previous method did not fulfill our wishes ● Requirements change fast and hard ● We wanted more introspection and control ● Small team, 6 developers and 1 project manager ● Manageable intermittant releases ● To not reinvent the wheel http://www.flickr.com/photos/sravi_in/3171545912/ 16 / 35
  17. 17. How did we implement it? http://www.flickr.com/photos/suttonhoo22/2512983749/ 17 / 35
  18. 18. One step at a time 18 / 35
  19. 19. 19 / 35
  20. 20. ROLES 20 / 35
  21. 21. 21 / 35
  22. 22. Planning poker http://www.flickr.com/photos/june29/3754566093/ 22 / 35
  23. 23. 23 / 35
  24. 24. Sprint backlog http://www.flickr.com/photos/oberazzi/318947873/ 24 / 35
  25. 25. http://www.flickr.com/photos/roolrool/4468175996/ 25 / 35
  26. 26. Burndown chart http://www.flickr.com/photos/oberazzi/318947873/ 26 / 35
  27. 27. http://www.flickr.com/photos/jnicho02/2805260361/ 27 / 35
  28. 28. http://www.flickr.com/photos/porras/3084218023/ 28 / 35
  29. 29. http://www.flickr.com/photos/elecnix/4120841676/ 29 / 35
  30. 30. 30 / 35
  31. 31. What more is there? http://www.flickr.com/photos/albany_tim/3536902765/ 31 / 35
  32. 32. Obstacles http://www.flickr.com/photos/foxypar4/1004464889/ 32 / 35
  33. 33. Questions? http://www.flickr.com/photos/oberazzi/318947873/ 33 / 35
  34. 34. Conclusion http://www.flickr.com/photos/mugley/2214327028/ 34 / 35
  35. 35. Mike van Riel mike.vanriel@naenius.com @mvriel http://blog.naenius.com http://www.joind.in/talk/view/1756 Links ● http://www.scrumalliance.org/ ● http://www.youtube.com/watch?v=IyNPeTn8fpo, Presentation by Ken Schwaber at Google ● http://www.infoq.com/minibooks/scrum-xp-from-the-trenches, Free book ● http://en.wikipedia.org/wiki/Scrum_(development), The Wikipedia article about SCRUM ● http://www.meetup.com/nlscrum/, Dutch SCRUM user group ● http://www.mountaingoatsoftware.com/, Mountain goat software Tools ● http://www.danube.com/scrumworks, ScrumWorks ● http://www.atlassian.com/software/jira/, Jira ● http://www.pivotaltracker.com/, Pivotal Tracker ● http://docs.google.com/, Google docs 35 / 35

×