Different tools that agile team can use to quickly move discussions to resolution, quickly estimate work, to measure fine-grained progress and more.

1. Agile Tools
Roy van de Water
Saturday, April 20, 13

2. Pairing
Saturday, April 20, 13

3. 2 Humans
1 Computer
Saturday, April 20, 13

4. Detectives
Saturday, April 20, 13

5. Pilots
Saturday, April 20, 13

6. Pair LOUD
Saturday, April 20, 13

7. Argument is
Good
Saturday, April 20, 13

8. Don’t be afraid
to be dumb
Saturday, April 20, 13

9. If you don’t
know anything,
Drive
Saturday, April 20, 13

10. Explain like I’m
5
Saturday, April 20, 13

11. It will be slower
Saturday, April 20, 13

12. It’s worth it
Saturday, April 20, 13

13. Increase Code
Quality
Saturday, April 20, 13

14. Prevent
Information
Silos
Saturday, April 20, 13

15. The hit-by-a-bus
test
Saturday, April 20, 13

16. Techniques:
Saturday, April 20, 13

17. Ping Pong
Pairing
Saturday, April 20, 13

18. A**hole Driven
Development
Saturday, April 20, 13

19. Promiscuous
Pairing
Saturday, April 20, 13

20. Driver switch on
timer
Saturday, April 20, 13

21. Decider
Saturday, April 20, 13

22. I propose
Saturday, April 20, 13

23. 1..2..3..
Saturday, April 20, 13

24. Saturday, April 20, 13

25. Nobody speaks
Saturday, April 20, 13

26. Absolute no?
Saturday, April 20, 13

27. What will it take
to get you in?
Saturday, April 20, 13

28. Re-propose or
withdraw
Saturday, April 20, 13

29. Every Decision
is Unanimous
Saturday, April 20, 13

30. No saboteurs
Saturday, April 20, 13

31. No unnecessary
discussion
Saturday, April 20, 13

32. Core Protocols
Saturday, April 20, 13

33. Meal Decider
Saturday, April 20, 13

34. Timebox
Saturday, April 20, 13

35. Prevent the
Rabbit Hole
Saturday, April 20, 13

36. Say what you
will do
Saturday, April 20, 13

37. Set a small
timebox
Saturday, April 20, 13

38. Use a central
timer
Saturday, April 20, 13

39. Black Box
Build login page
Saturday, April 20, 13

40. Red Box
Build login page
Saturday, April 20, 13

41. You have to ask
for help
Saturday, April 20, 13

42. Planning
Poker
Saturday, April 20, 13

43. Steps:
Saturday, April 20, 13

44. Read the User
Story out loud
Saturday, April 20, 13

45. 1..2..3
Saturday, April 20, 13

46. Everyone votes
at once
Saturday, April 20, 13

47. Outliers speak
Saturday, April 20, 13

48. Dissent
indicates a lack
of shared
Saturday, April 20, 13

49. Discuss, don’t
negotiate
Saturday, April 20, 13

50. Revote
Saturday, April 20, 13

51. Take the higher
estimate
Saturday, April 20, 13

52. Estimate stories
in isolation
Saturday, April 20, 13

53. Vote relative to
the other stories
in the backlog
Saturday, April 20, 13

54. Avoid too much
detail
Saturday, April 20, 13

55. Don’t worry if
they’re wrong
Saturday, April 20, 13

56. Stay low tech
Saturday, April 20, 13

57. Force quiet
team members
to contribute
Saturday, April 20, 13

58. Variation: No
discussion till
2nd time
through
Saturday, April 20, 13

59. Tasking Poker
Saturday, April 20, 13

60. Use blocks of
time instead of
points
Saturday, April 20, 13

61. Scrum
Saturday, April 20, 13

62. One Product
Owner
Saturday, April 20, 13

63. Scum Master is
not a developer
Saturday, April 20, 13

64. Cross-functional
Team
Saturday, April 20, 13

65. Backlog
grooming
Saturday, April 20, 13

66. Larger stories
farther out
Saturday, April 20, 13

67. Be realistic
about what you
need
Saturday, April 20, 13

68. Involve a
Developer
Saturday, April 20, 13

69. Planning
Saturday, April 20, 13

70. Negotiate
acceptance
criteria
Saturday, April 20, 13

71. Use the
whiteboard
Saturday, April 20, 13

72. Keep tasks
small
Saturday, April 20, 13

73. Optimize for
swarming
Saturday, April 20, 13

74. Commit
Saturday, April 20, 13

75. Use a physical
card wall
Saturday, April 20, 13

76. Pairs bring 1
card to their
desk
Saturday, April 20, 13

77. Burndown
Charts
Saturday, April 20, 13

78. Standups
Saturday, April 20, 13

79. Actually stand
up
Saturday, April 20, 13

80. Drifting off?
Switch it up
Saturday, April 20, 13

81. Try using
check-ins
Saturday, April 20, 13

82. Use a token
Saturday, April 20, 13

83. Going in
random order
Saturday, April 20, 13

84. Pick an ending
phrase
Saturday, April 20, 13

85. Timebox to 15
minutes
Saturday, April 20, 13

86. Retrospectives
Saturday, April 20, 13

87. Agile
Retrospectives
Esther Derby
Diana Larson
Saturday, April 20, 13

88. Kanban
Saturday, April 20, 13

89. Backlog Working Done
Saturday, April 20, 13

90. Product Owner
sorts value
stream
Saturday, April 20, 13

91. Deliver
Continuously
Saturday, April 20, 13

92. Pick a release
cycle
Saturday, April 20, 13

93. Retrospect
Saturday, April 20, 13

94. Highlights
problems,
doesn’t solve
them
Saturday, April 20, 13

95. Use WIP limits
Saturday, April 20, 13

96. Avoid work
arounds
Saturday, April 20, 13

97. Agile Tools
Roy van de Water
http://bit.ly/dcc-agile-tools
Saturday, April 20, 13