0
Building the Right            Thingthrough collaboration and continual            discovery
Brent Snook@brentsnookbrent@zooatrope.com
The Team
The TeamJoanne
The TeamJoanne      Terry
The TeamJoanne      Terry   Sally
#293 - Add a new friend by email address (M)
#293 - Add a new friend by email address (M)                  2/5/12 - Terry, Joanne, Sally
#293 - Add a new friend by email address (M)                  2/5/12 - Terry, Joanne, Sally       IN                      ...
#293 - Add a new friend by email address (M)                              2/5/12 - Terry, Joanne, Sally           IN      ...
Good Stories are Told,    Not Written •   Defer detail until the last responsible     moment •   Understand and solve the ...
To Do   Dev   Test   Done
Day 1To Do   Dev   Test   Done
Day 2To Do   Dev   Test   Done
Day 3To Do   Dev   Test   Done
Day 4To Do   Dev   Test   Done
Last DayTo Do   Dev   Test   Done
Last Day  To Do         Dev     Test   DoneAverage time in play:  4+ days
To Do   Dev   Test   Done
Day 1To Do   Dev   Test   Done
Day 2To Do   Dev   Test   Done
Day 3 - Dev is Blocked!To Do   Dev   Test   Done
Helping to Free Up Test...  To Do   Dev   Test   Done
Dev is UnblockedTo Do   Dev   Test   Done
Day 4To Do   Dev   Test   Done
Day 4To Do   Dev   Test   Done
Last Day...To Do    Dev   Test   Done
By the End of the DayTo Do   Dev   Test   Done
By the End of the Day  To Do         Dev       Test       DoneAverage time in play (cycle time):        2.6 days
cycle timecost
cycle time               cost4 days X 5 stories = 20 days
cycle time                 cost 4 days X 5 stories = 20 days2.6 days X 5 stories = 13 days
To Do Doing Done
Reducing Cycle Time•   Build things in a way that allows people to play    earlier•   Don’t retreat to your bay in the ass...
Keeping Stories On Track• Spot    the problem using statistics• Split   stories by fidelity or functionality• Swarm     to...
Individuals and Interactions  over Processes and ToolsThe Agile Manifesto brent@zooatrope.com @brentsnook http://www.slide...
Bibilography• Kent Beck, Cynthia Andres, Extreme Programming Explained: Embrace Change (2nd Edition), Addison-Wesley Profe...
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Building the Right Thing
Upcoming SlideShare
Loading in...5
×

Building the Right Thing

1,119

Published on

My presentation on building the right thing through collaboration and continual discovery. Presented at Agile Australia 2012.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,119
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
24
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Building the Right Thing"

  1. 1. Building the Right Thingthrough collaboration and continual discovery
  2. 2. Brent Snook@brentsnookbrent@zooatrope.com
  3. 3. The Team
  4. 4. The TeamJoanne
  5. 5. The TeamJoanne Terry
  6. 6. The TeamJoanne Terry Sally
  7. 7. #293 - Add a new friend by email address (M)
  8. 8. #293 - Add a new friend by email address (M) 2/5/12 - Terry, Joanne, Sally
  9. 9. #293 - Add a new friend by email address (M) 2/5/12 - Terry, Joanne, Sally IN OUT
  10. 10. #293 - Add a new friend by email address (M) 2/5/12 - Terry, Joanne, Sally IN OUT - select friend by searching by - searching for friends by email address name - only show addresses of those - autocomplete when typing that aren’t my friends already name - confirm when I add a friend, - inviting new users to join if only add them if I answer yes they are not members already - back to email search results when I answer no - “You are now friends” confirmation afterwards
  11. 11. Good Stories are Told, Not Written • Defer detail until the last responsible moment • Understand and solve the problem together • Capture the conversation but keep it simple • Define “done” • Stop telling/start building as soon as you have enough detail
  12. 12. To Do Dev Test Done
  13. 13. Day 1To Do Dev Test Done
  14. 14. Day 2To Do Dev Test Done
  15. 15. Day 3To Do Dev Test Done
  16. 16. Day 4To Do Dev Test Done
  17. 17. Last DayTo Do Dev Test Done
  18. 18. Last Day To Do Dev Test DoneAverage time in play: 4+ days
  19. 19. To Do Dev Test Done
  20. 20. Day 1To Do Dev Test Done
  21. 21. Day 2To Do Dev Test Done
  22. 22. Day 3 - Dev is Blocked!To Do Dev Test Done
  23. 23. Helping to Free Up Test... To Do Dev Test Done
  24. 24. Dev is UnblockedTo Do Dev Test Done
  25. 25. Day 4To Do Dev Test Done
  26. 26. Day 4To Do Dev Test Done
  27. 27. Last Day...To Do Dev Test Done
  28. 28. By the End of the DayTo Do Dev Test Done
  29. 29. By the End of the Day To Do Dev Test DoneAverage time in play (cycle time): 2.6 days
  30. 30. cycle timecost
  31. 31. cycle time cost4 days X 5 stories = 20 days
  32. 32. cycle time cost 4 days X 5 stories = 20 days2.6 days X 5 stories = 13 days
  33. 33. To Do Doing Done
  34. 34. Reducing Cycle Time• Build things in a way that allows people to play earlier• Don’t retreat to your bay in the assembly line• Think: concurrent activities, not sequential phases!• Share the responsibility for getting stories to “Done”
  35. 35. Keeping Stories On Track• Spot the problem using statistics• Split stories by fidelity or functionality• Swarm to complete things faster
  36. 36. Individuals and Interactions over Processes and ToolsThe Agile Manifesto brent@zooatrope.com @brentsnook http://www.slideshare.net/fuglylogic/building-the-right-thing
  37. 37. Bibilography• Kent Beck, Cynthia Andres, Extreme Programming Explained: Embrace Change (2nd Edition), Addison-Wesley Professional, 2004• Alistair Cockburn, Agile Software Development: The Cooperative Game (2nd Edition), Addison-Wesley Professional, 2006• Niklaus Wirth, A Brief History of Software Engineering, 25 Feb 2008, 1 May 2012 <http://www.inf.ethz.ch/personal/wirth/ Articles/Miscellaneous/IEEE-Annals.pdf>• The Rise and Fall of Waterfall,Youtube, 2 May 2012, <http://www.youtube.com/watch?v=X1c2--sP3o0>• The Agile Manifesto, 1 May 2012, <http://agilemanifesto.org>• Littles Law, Wikipedia, 2 May 2012, <http://en.wikipedia.org/wiki/Littles_law>• Jeff Patton, Kanban Over Simplified, Agile Product Design, 2 May 20102, <http://www.agileproductdesign.com/blog/2009/ kanban_over_simplified.html>• Timeline of computing 1950–1979, Wikipedia, 21 May 2012, <http://en.wikipedia.org/wiki/ Timeline_of_computing_1950%E2%80%931979>• Gang of Four, Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley Professional, 1994• William J. Brown, Raphael C. Malveau, SkipMcCormick, Thomas J. Mowbray, Anti Patterns: Refactoring Software, Architectures, and Projects in Crisis, Wiley, 1998• Anti-pattern, Wikipedia, 21 May 2012, <http://en.wikipedia.org/wiki/Anti-pattern>• Sasa Stamenkovic, Queuing Theory, 3 April 2009, 21 May 2012, <http://stamenkovic.se/2009/04/03/queuing-theory/>• Images created with Paper (www.fiftythree.com/)
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×