Uploaded on

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

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

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
358
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Agile ToolsRoy van de WaterSaturday, April 20, 13
  • 2. PairingSaturday, April 20, 13
  • 3. 2 Humans1 ComputerSaturday, April 20, 13
  • 4. DetectivesSaturday, April 20, 13
  • 5. PilotsSaturday, April 20, 13
  • 6. Pair LOUDSaturday, April 20, 13
  • 7. Argument isGoodSaturday, April 20, 13
  • 8. Don’t be afraidto be dumbSaturday, April 20, 13
  • 9. If you don’tknow anything,DriveSaturday, April 20, 13
  • 10. Explain like I’m5Saturday, April 20, 13
  • 11. It will be slowerSaturday, April 20, 13
  • 12. It’s worth itSaturday, April 20, 13
  • 13. Increase CodeQualitySaturday, April 20, 13
  • 14. PreventInformationSilosSaturday, April 20, 13
  • 15. The hit-by-a-bustestSaturday, April 20, 13
  • 16. Techniques:Saturday, April 20, 13
  • 17. Ping PongPairingSaturday, April 20, 13
  • 18. A**hole DrivenDevelopmentSaturday, April 20, 13
  • 19. PromiscuousPairingSaturday, April 20, 13
  • 20. Driver switch ontimerSaturday, April 20, 13
  • 21. DeciderSaturday, April 20, 13
  • 22. I proposeSaturday, April 20, 13
  • 23. 1..2..3..Saturday, April 20, 13
  • 24. Saturday, April 20, 13
  • 25. Nobody speaksSaturday, April 20, 13
  • 26. Absolute no?Saturday, April 20, 13
  • 27. What will it taketo get you in?Saturday, April 20, 13
  • 28. Re-propose orwithdrawSaturday, April 20, 13
  • 29. Every Decisionis UnanimousSaturday, April 20, 13
  • 30. No saboteursSaturday, April 20, 13
  • 31. No unnecessarydiscussionSaturday, April 20, 13
  • 32. Core ProtocolsSaturday, April 20, 13
  • 33. Meal DeciderSaturday, April 20, 13
  • 34. TimeboxSaturday, April 20, 13
  • 35. Prevent theRabbit HoleSaturday, April 20, 13
  • 36. Say what youwill doSaturday, April 20, 13
  • 37. Set a smalltimeboxSaturday, April 20, 13
  • 38. Use a centraltimerSaturday, April 20, 13
  • 39. Black BoxBuild login pageSaturday, April 20, 13
  • 40. Red BoxBuild login pageSaturday, April 20, 13
  • 41. You have to askfor helpSaturday, April 20, 13
  • 42. PlanningPokerSaturday, April 20, 13
  • 43. Steps:Saturday, April 20, 13
  • 44. Read the UserStory out loudSaturday, April 20, 13
  • 45. 1..2..3Saturday, April 20, 13
  • 46. Everyone votesat onceSaturday, April 20, 13
  • 47. Outliers speakSaturday, April 20, 13
  • 48. Dissentindicates a lackof sharedSaturday, April 20, 13
  • 49. Discuss, don’tnegotiateSaturday, April 20, 13
  • 50. RevoteSaturday, April 20, 13
  • 51. Take the higherestimateSaturday, April 20, 13
  • 52. Estimate storiesin isolationSaturday, April 20, 13
  • 53. Vote relative tothe other storiesin the backlogSaturday, April 20, 13
  • 54. Avoid too muchdetailSaturday, April 20, 13
  • 55. Don’t worry ifthey’re wrongSaturday, April 20, 13
  • 56. Stay low techSaturday, April 20, 13
  • 57. Force quietteam membersto contributeSaturday, April 20, 13
  • 58. Variation: Nodiscussion till2nd timethroughSaturday, April 20, 13
  • 59. Tasking PokerSaturday, April 20, 13
  • 60. Use blocks oftime instead ofpointsSaturday, April 20, 13
  • 61. ScrumSaturday, April 20, 13
  • 62. One ProductOwnerSaturday, April 20, 13
  • 63. Scum Master isnot a developerSaturday, April 20, 13
  • 64. Cross-functionalTeamSaturday, April 20, 13
  • 65. BackloggroomingSaturday, April 20, 13
  • 66. Larger storiesfarther outSaturday, April 20, 13
  • 67. Be realisticabout what youneedSaturday, April 20, 13
  • 68. Involve aDeveloperSaturday, April 20, 13
  • 69. PlanningSaturday, April 20, 13
  • 70. NegotiateacceptancecriteriaSaturday, April 20, 13
  • 71. Use thewhiteboardSaturday, April 20, 13
  • 72. Keep taskssmallSaturday, April 20, 13
  • 73. Optimize forswarmingSaturday, April 20, 13
  • 74. CommitSaturday, April 20, 13
  • 75. Use a physicalcard wallSaturday, April 20, 13
  • 76. Pairs bring 1card to theirdeskSaturday, April 20, 13
  • 77. BurndownChartsSaturday, April 20, 13
  • 78. StandupsSaturday, April 20, 13
  • 79. Actually standupSaturday, April 20, 13
  • 80. Drifting off?Switch it upSaturday, April 20, 13
  • 81. Try usingcheck-insSaturday, April 20, 13
  • 82. Use a tokenSaturday, April 20, 13
  • 83. Going inrandom orderSaturday, April 20, 13
  • 84. Pick an endingphraseSaturday, April 20, 13
  • 85. Timebox to 15minutesSaturday, April 20, 13
  • 86. RetrospectivesSaturday, April 20, 13
  • 87. AgileRetrospectivesEsther DerbyDiana LarsonSaturday, April 20, 13
  • 88. KanbanSaturday, April 20, 13
  • 89. Backlog Working DoneSaturday, April 20, 13
  • 90. Product Ownersorts valuestreamSaturday, April 20, 13
  • 91. DeliverContinuouslySaturday, April 20, 13
  • 92. Pick a releasecycleSaturday, April 20, 13
  • 93. RetrospectSaturday, April 20, 13
  • 94. Highlightsproblems,doesn’t solvethemSaturday, April 20, 13
  • 95. Use WIP limitsSaturday, April 20, 13
  • 96. Avoid workaroundsSaturday, April 20, 13
  • 97. Agile ToolsRoy van de Waterhttp://bit.ly/dcc-agile-toolsSaturday, April 20, 13