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.

Essentielle værktøjer for det agile team

486 views

Published on

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

  • Be the first to like this

Essentielle værktøjer for det agile team

  1. 1. Essentielle værktøjer for det agile team Casper Wilstrup Partner, BestBrains BestBrains 4. november 2013
  2. 2. Det første værktøj En proces
  3. 3. Procesværktøjer Proces → Værktøj → hvordan vi arbejder noget vi bruger til at løse en opgave
  4. 4. Procesværktøj Ordinerende Adaptiv Grafik fra Henrik Kniberg, ”Kanban and Scrum”
  5. 5. Scrum
  6. 6. Kanban
  7. 7. Development Roadmap Roadmap Areas User stories (Features) Breakdown Validate Done Estimate Value, Effort Backlog Develop Deploy to test Todo Doing Review Done Development Tasks Verify
  8. 8. Kanban og Scrum Kniv eller gaffel – hvad er bedst?
  9. 9. Det andet værktøj Målinger
  10. 10. Empiri Grafik fra Henrik Kniberg, ”Kanban and Scrum”
  11. 11. Empiri Grafik fra Henrik Kniberg, ”Kanban and Scrum”
  12. 12. Burn-down Charts
  13. 13. Burn-up Charts
  14. 14. Cumulative Flow Diagrams
  15. 15. Det tredje værktøj Source Control
  16. 16. “At my first job, we had a Source Control department. When you had your code ready to go, you took your floppy disks to the nice ladies in Source Control, they would take your disks, duly update the library, and build the customer-ready product from the officially reposed source.” - Miles Duke
  17. 17. Det fjerde værktøj Continuous Integration (and delivery)
  18. 18. Det femte værktøj Automatiske tests
  19. 19. ✗ Manual testing ✗ »Expensive« bug fixes ✗ Reluctance to change smelly code ✗ Unnecessary complexity Time
  20. 20. ✓ Timed saved on manual testing ✓ Old bugs do not re-appear ✓ New bugs discovered early ✓ Enables refactoring ✓ Improves design first time with automated testing ✗ Manual testing ✗ »Expensive« bug fixes ✗ Reluctance to change smelly code ✗ Unnecessary complexity Time
  21. 21. ✓ Timed saved on manual testing ✓ Old bugs do not re-appear ✓ New bugs discovered early ✓ Enables refactoring ✓ Improves design with automated testing first time with automated testing ✗ Manual testing ✗ »Expensive« bug fixes ✗ Reluctance to change smelly code ✗ Unnecessary complexity Time
  22. 22. Hvorfor er det så svært?
  23. 23. Hvorfor er det så svært? No test No test Less time Less time Less refactoring More bugs More complexity
  24. 24. More test More time Fewer bugs
  25. 25. Tests der kan automatiseres Unit tests Integration tests System tests Acceptance tests API tests Performance tests Monitoring tests …
  26. 26. Test Driven Development 2. Make it run 1. Write a failing test 3. Refactor
  27. 27. Behaviour Driven Development 2. Make it run 1. Write a failing test 3. Refactor
  28. 28. Det sjette værktøj Kodeinspektion
  29. 29. Det syvende værktøj Feedback
  30. 30. Feedback - review
  31. 31. Feedback - retrospectives
  32. 32. Feedback - pairing
  33. 33. Feedback – peer assessment Jesper Rasmus Mette Thomas C++ 3 2 3 3 OpenGL 2 3 1 2 DB2 1 0 0 1 Qt 2 1 2 3 Boost 3 2 2 3 Windows 1 2 3 2 Linux 3 1 1 3 UX design 2 0 0 1 Javascript 1 1 2 1 Net prog 2 2 2 2 1 2 2 Java Test 2 2 ...
  34. 34. Essentielle værktøjer for det agile team Diskussion BestBrains 4. november 2013
  35. 35. Essentielle værktøjer for det agile team Tak for i dag BestBrains 4. november 2013

×