Building the Right Thing
0 likes784 views
The document outlines the importance of collaboration and continuous discovery in agile development processes, highlighting techniques for reducing cycle time and improving productivity. It emphasizes the need for teams to define 'done' and to share responsibility for completing stories efficiently. Additionally, it references various resources and principles from agile methodologies to support effective team dynamics and project outcomes.
Building the Right Thing
- 1. Building the Right Thing through collaboration and continual discovery
- 12. The Team
- 13. The Team Joanne
- 14. The Team Joanne Terry
- 15. The Team Joanne Terry Sally
- 23. #293 - Add a new friend by email address (M)
- 24. #293 - Add a new friend by email address (M) 2/5/12 - Terry, Joanne, Sally
- 25. #293 - Add a new friend by email address (M) 2/5/12 - Terry, Joanne, Sally IN OUT
- 26. #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
- 27. 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
- 29. To Do Dev Test Done
- 30. Day 1 To Do Dev Test Done
- 31. Day 2 To Do Dev Test Done
- 32. Day 3 To Do Dev Test Done
- 33. Day 4 To Do Dev Test Done
- 34. Last Day To Do Dev Test Done
- 35. Last Day To Do Dev Test Done Average time in play: 4+ days
- 37. To Do Dev Test Done
- 38. Day 1 To Do Dev Test Done
- 39. Day 2 To Do Dev Test Done
- 40. Day 3 - Dev is Blocked! To Do Dev Test Done
- 41. Helping to Free Up Test... To Do Dev Test Done
- 42. Dev is Unblocked To Do Dev Test Done
- 43. Day 4 To Do Dev Test Done
- 44. Day 4 To Do Dev Test Done
- 45. Last Day... To Do Dev Test Done
- 46. By the End of the Day To Do Dev Test Done
- 47. By the End of the Day To Do Dev Test Done Average time in play (cycle time): 2.6 days
- 48. cycle time cost
- 49. cycle time cost 4 days X 5 stories = 20 days
- 50. cycle time cost 4 days X 5 stories = 20 days 2.6 days X 5 stories = 13 days
- 53. To Do Doing Done
- 59. 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”
- 66. Keeping Stories On Track • Spot the problem using statistics • Split stories by fidelity or functionality • Swarm to complete things faster
- 67. Individuals and Interactions over Processes and Tools The Agile Manifesto brent@zooatrope.com @brentsnook http://www.slideshare.net/fuglylogic/building-the-right-thing
- 68. 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> • Little's Law, Wikipedia, 2 May 2012, <http://en.wikipedia.org/wiki/Little's_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/)