We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byBryson Layng
Modified over 4 years ago
Distributed Agile: An oxymoron? firstname.lastname@example.org email@example.com © ThoughtWorks 2008
Agile = Co-located © ThoughtWorks 2008
Agile Manifesto Principles © ThoughtWorks 2008 Business people and developers must work together daily throughout the project. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. On-site customer Collective Code Ownership XP Practices Osmotic Communication Easy access to expert users Crystal Clear (principles) Active user involvement DSDM (principles) Unnecessary Movement Lean Software Development Waiting Unnecessary Transportation
Agile = Co-located © ThoughtWorks 2008 Distributed = Different locations Distributed Agile = An Oxymoron?
Enterprise Software © ThoughtWorks 2008 Large Sometimes Distributed Complex Heavily dependent Business critical
Our experience… © ThoughtWorks 2008 Large Complex Heavily dependent Business critical Sometimes Distributed
© ThoughtWorks 2008 Distributed development looks easy (a slightly fictional story)
Once upon a time… © ThoughtWorks 2008
there was a team… © ThoughtWorks 2008
working together on the same project… © ThoughtWorks 2008
… … … … … … … … Same project at the same location
everyone understood each other… © ThoughtWorks 2008
some people wanted the project distributed… © ThoughtWorks 2008
= ££££££ + = ££ + $$$$ = ½ £££
(of course, it might be more than just £££s) © ThoughtWorks 2008
they started work with new people in another place... © ThoughtWorks 2008
life was great! © ThoughtWorks 2008
they would talk over the phone... © ThoughtWorks 2008
… … … … … … … …
and send email... © ThoughtWorks 2008
type type type…
sometimes things would take some time... © ThoughtWorks 2008
I wonder what Jane meant by that. I better send an email... … whats the gobbleflux about …
© ThoughtWorks 2008 Thats an easy one. Here you go. … Gobbleflux? On the left …
© ThoughtWorks 2008 On the left? … on the left of what? …
something that should have been ten minutes © ThoughtWorks 2008
stretches to several days... © ThoughtWorks 2008
!!! … To the left of the widget …
© ThoughtWorks 2008 Theres a widget? … What widget are you talking about? … Shes not even trying...
© ThoughtWorks 2008 Why doesnt he understand? … The breadcrumbs widget …
things continue like that for three months... © ThoughtWorks 2008
until... © ThoughtWorks 2008
I cant wait to see... Theyre going to be impressed by this...
A KEY LESSON © ThoughtWorks 2008 every physical boundary increases noise
© ThoughtWorks 2008 http://www.agilemodeling.com/essays/communication.htm
© ThoughtWorks 2008
cost of distributed development (is more than just people)
A more realistic formula © ThoughtWorks 2008 = ££££££ + = ££ + $$$$ ½ + Cost of (timely response and shared understanding) On-shoreDistributed
© ThoughtWorks 2008 Challenges of Distributed Development Look familiar? Shared understanding Timely decisions Trust and rapport Visibility into progress Working in the same way Its (almost) the same as co-located development... just much harder. Overcoming the
Division by role Functional teams Must haves for successful distributed development © ThoughtWorks 2008 Analysts Developers Testers Infrastructure
Must haves for successful distributed development © ThoughtWorks 2008 Cross functional teams Division by feature, not by role
Must haves for successful distributed development © ThoughtWorks 2008 Excellent relationship with the business
Must haves for successful distributed development © ThoughtWorks 2008 Speedy Escalation Paths
Must haves for successful distributed development © ThoughtWorks 2008 Shared Culture
© ThoughtWorks 2008 Example: Sharing culture
Must haves for successful distributed development © ThoughtWorks 2008 Shared Environments
Must haves for successful distributed development © ThoughtWorks 2008 Shared sense of 3 Ps (Purpose, Priority, Plan)
Must haves for successful distributed development © ThoughtWorks 2008 Frequent software demos
Must haves for successful distributed development © ThoughtWorks 2008 Continuous Reflection and Improvement
Must haves for successful distributed development © ThoughtWorks 2008 Frequent visits
Must haves for successful distributed development © ThoughtWorks 2008 Cross functional teams Excellent relationship with the business Speedy Escalation Paths Shared culture Shared environments Shared purpose, priority, plan Frequent showcases Continue Reflection and improvement Frequent visits
Good practices still hold © ThoughtWorks 2008 Visibility and transparency of information Face to face time Tools that support distributed teams Agile development practices Frequent rotation Principles of good teams JIRA
Conclusion Distributed Agile: An oxymoron? © ThoughtWorks 2008
Questions and Comments? firstname.lastname@example.org email@example.com
Flickr Creative Commons Alarm: http://flickr.com/photos/chidorian/7666930/http://flickr.com/photos/chidorian/7666930/ Masonic handshake: http://flickr.com/photos/gaetanlee/159591865/http://flickr.com/photos/gaetanlee/159591865/ Plane: http://flickr.com/photos/volodimer/400350015/http://flickr.com/photos/volodimer/400350015/ East meets west: http://flickr.com/photos/evanosherow/2280507811/http://flickr.com/photos/evanosherow/2280507811/ Free wallpaper Matrix wallpaper: http://www.wallpaperbase.com/wallpapers/movie/matrix/matrix_5.jpghttp://www.wallpaperbase.com/wallpapers/movie/matrix/matrix_5.jpg Photo Credits © ThoughtWorks 2008
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Transition to Scrum Midway through a AAA Development Cycle: Lessons Learned Asbjoern Malte Soendergaard Development Manager Crytek GmbH.
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
Chapter: 3 Agile Development
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
Designed for your needs ANI Voice Communications Designed for your needs Audio Conferencing Message Delivery TeamConnect.
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
Agile Testing and/or Agility in Testing? Juha Itkonen SoberIT Teknillinen Korkeakoulu Test Summit, , Savonlinna.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
Agile Project Management with Scrum
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Agile Architecture? Paul Lund 24 th Nov Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile Software Development
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
© 2018 SlidePlayer.com Inc. All rights reserved.