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