The document discusses essential tools for agile teams. It outlines seven key tools: (1) processes like Scrum and Kanban which define how teams work; (2) measurements like burn down charts which provide visibility; (3) source control to manage code versions; (4) continuous integration to continually build and test code; (5) automated testing to frequently test code quality; (6) code inspection to review code quality; and (7) feedback through reviews, retrospectives, and pairing to improve team collaboration and output. The document emphasizes how these tools help teams work together effectively through practices like test-driven development.

1. Essentielle
værktøjer for
det agile team
Casper Wilstrup
Partner, BestBrains
BestBrains
4. november 2013

10. Det første værktøj
En proces

11. Procesværktøjer
Proces
→
Værktøj →
hvordan vi arbejder
noget vi bruger til at løse en opgave

12. Procesværktøj
Ordinerende
Adaptiv
Grafik fra Henrik Kniberg, ”Kanban and Scrum”

13. Scrum

15. Kanban

16. 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

18. Kanban og Scrum
Kniv eller gaffel – hvad er bedst?

19. Det andet værktøj
Målinger

20. Empiri
Grafik fra Henrik Kniberg, ”Kanban and Scrum”

21. Empiri
Grafik fra Henrik Kniberg, ”Kanban and Scrum”

22. Burn-down Charts

23. Burn-up Charts

24. Cumulative Flow Diagrams

25. Det tredje værktøj
Source Control

26. “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

30. Det fjerde værktøj
Continuous Integration
(and delivery)

38. Det femte værktøj
Automatiske tests

39. ✗ Manual testing
✗ »Expensive« bug fixes
✗ Reluctance to change smelly code
✗ Unnecessary complexity
Time

40. ✓ 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

41. ✓ 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

43. Hvorfor er det så svært?

44. Hvorfor er det så svært?
No test
No test
Less time
Less time
Less refactoring
More bugs
More complexity

45. More test
More time
Fewer bugs

46. Tests der kan automatiseres
Unit tests
Integration tests
System tests
Acceptance tests
API tests
Performance tests
Monitoring tests
…

47. Test Driven Development
2. Make it run
1. Write a failing test
3. Refactor

48. Behaviour Driven Development
2. Make it run
1. Write a failing test
3. Refactor

55. Det sjette værktøj
Kodeinspektion

57. Det syvende værktøj
Feedback

58. Feedback - review

59. Feedback - retrospectives

60. Feedback - pairing

61. 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
...

62. Essentielle
værktøjer for
det agile team
Diskussion
BestBrains
4. november 2013

63. Essentielle
værktøjer for
det agile team
Tak for i dag
BestBrains
4. november 2013