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 2 years ago
Distributed Agile: An oxymoron? © 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 ... © ThoughtWorks 2008
type type type…
sometimes things would take some time... © ThoughtWorks 2008
I wonder what Jane meant by that. I better send an ... … 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
© 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?
Flickr Creative Commons Alarm: Masonic handshake: Plane: East meets west: Free wallpaper Matrix wallpaper: Photo Credits © ThoughtWorks 2008
The Agile Primer July 2008 © ThoughtWorks 2008.
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Agile Introduction Emerson Murphy-Hill. Agile Manifesto/Alliance XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD February 2001 (Snowbird,
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
1 11/21/2015 ã 2007, Spencer Rugaber Agile Manifesto February, 2001 XP, SCRUM, DSDM, Adaptive Software Development,
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Agile Methods 1. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have.
1 Chapter 4 Agile Development Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
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.
How Agile Are You? Larry Apke Agile Expert
- Discussion of Chapter 1 in Martin and Martin. We are uncovering better ways of developing software by doing it and helping others do it. Through this.
From The Academe to Industry: Context-Driven Software Engineering Matthew Heusser Excelon Development – xndev.com - Presented to CS 611.
Agile Project Management with Scrum. Resource links
Continuous Delivery Ajey Gore Head of Technology ThoughtWorks India.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
CS1: Classic Software Life Cycle “Waterfall” method: 1.Requirements/Analysis Determine the problem to be solved – client-centered 2.Specification.
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
Why (or When) Agile Fails Creating high performance software delivery teams.
Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Transition to Scrum Midway through a AAA Development Cycle: Lessons Learned Asbjoern Malte Soendergaard Development Manager Crytek GmbH.
Agile Testing and/or Agility in Testing? Juha Itkonen SoberIT Teknillinen Korkeakoulu Test Summit, , Savonlinna.
Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Larry Apke Agile Expert
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Does it work with Data Warehouses?. “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we.
By: Isuru Abeysekera AGILE DEVELOPMENT. WHAT IS AGILE DEVELOPMENT? Broad term used to describe several methods for a development process Introduced in.
IS3320 Developing and Using Management Information Systems Lecture 20: Project Management Rob Gleasure
Coaching Essentials: Module #1 IMS Consulting Group.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
AGILE DELIVERY FACILITATION Agile Project Manager should see his stakeholders as kids and aim to help them be successful in their respective goals, each.
Agile Web Development C. Daniel Chase University of Colorado at Boulder.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.1.
Designed for your needs ANI Voice Communications Designed for your needs Audio Conferencing Message Delivery TeamConnect.
Employee Engagement Survey Question Definitions. Gallup Q12 Questions What are they? The Gallup Questions are questions that Gallup has consistently found.
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Developed by Reneta Barneva, SUNY Fredonia Agile Development.
TIK 302 Rekayasa Perangkat Lunak Agile Proses. Agile View of Process Represents a reasonable compromise between conventional software engineering for.
UX meets XP. Overview of core approaches to creating interactive software Waterfall, iterative design, Agile Hybrid methods of evaluation H&P Chapter.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
© 2017 SlidePlayer.com Inc. All rights reserved.