Distributed Agile: An oxymoron?
elizabeth.keogh@thoughtworks.com
patrick.kua@thoughtworks.com
© ThoughtWorks 2008
Agile = Co-locatedAgile = Co-located
© ThoughtWorks 2008
Agile Manifesto Principles
Business people and developers must work
together daily throughout the project.
The most effici...
Agile = Co-located
© ThoughtWorks 2008
Distributed = Different locations
Distributed Agile = An Oxymoron?
Enterprise Software
Large
Sometimes
Distributed
Business critical
Enterprise Software
© ThoughtWorks 2008
Complex
Heavily ...
Our experience…
Large
Business critical
Sometimes
Distributed
Our experience…
© ThoughtWorks 2008
Complex
Heavily dependent
Distributed development looks easy
© ThoughtWorks 2008
Distributed development looks easy
(a slightly fictional story)
Once upon a time…Once upon a time…
© ThoughtWorks 2008
there was a team…there was a team…
© ThoughtWorks 2008
© ThoughtWorks 2008
working together on the same project…working together on the same project…
© ThoughtWorks 2008
……
……
Same project at the
same location
© ThoughtWorks 2008
…… ……
……
everyone understood each other…everyone understood each other…
© ThoughtWorks 2008
© ThoughtWorks 2008
some people wanted the project distributed…some people wanted the project distributed…
© ThoughtWorks 2008
= ££££££
+
= ££ + $$$$
© ThoughtWorks 2008
= ½ £££
(of course, it might be more than just £££s)(of course, it might be more than just £££s)
© ThoughtWorks 2008
they started work with new
people in another place...
© ThoughtWorks 2008
© ThoughtWorks 2008
New
New New
New
life was great!life was great!
© ThoughtWorks 2008
they would talk over the phone...they would talk over the phone...
© ThoughtWorks 2008
……
…… ……
© ThoughtWorks 2008
……
and send email...and send email...
© ThoughtWorks 2008
© ThoughtWorks 2008
type type type…
sometimes things would take some time...sometimes things would take some time...
© ThoughtWorks 2008
I wonder what
Jane meant by
I wonder what
Jane meant by
© ThoughtWorks 2008
Jane meant by
that. I better send
an email...
...
That’s an
easy one.
Here you go.
That’s an
easy one.
Here you go.
… Gobbleflux? On
the left …
© ThoughtWorks 2008
the left...
© ThoughtWorks 2008
On the
left?
On the
left?
… on the left
of what? …
something that should have been ten minutessomething that should have been ten minutes
© ThoughtWorks 2008
stretches to several days...stretches to several days...
© ThoughtWorks 2008
!!!!!!
… To the left of
the widget …
© ThoughtWorks 2008
the widget …
There’s a
widget?
There’s a
widget?
She’s
not even
She’s
not even
© ThoughtWorks 2008
widget?widget?
… What widget are
you...
Why doesn’t he
understand?
Why doesn’t he
understand?
… The breadcrumbs
widget …
© ThoughtWorks 2008
widget …
things continue like that for three months...things continue like that for three months...
© ThoughtWorks 2008
until...until...
© ThoughtWorks 2008
I can’t wait to see...I can’t wait to see...
They’re going to be
impressed by this...
They’re going to be
impressed by thi...
A KEY LESSON
every physical boundary increases noise
© ThoughtWorks 2008
every physical boundary increases noise
© ThoughtWorks 2008
http://www.agilemodeling.com/essays/communication.htm
© ThoughtWorks 2008
cost of distributed development
© ThoughtWorks 2008
cost of distributed development
(is more than just people)
A more realistic formula
= ££££££
+
= ££ + $$$$
½On-shore Distributed
© ThoughtWorks 2008
= ££££££ = ££ + $$$$
+ Cost of (...
Challenges of Distributed Development
Timely decisions
Trust and rapport
Visibility into progress
© ThoughtWorks 2008
Chal...
Must haves for successful distributed development
Division by role
Functional teams
© ThoughtWorks 2008
Analysts Developer...
Must haves for successful distributed development
© ThoughtWorks 2008
Cross functional teams
Division by feature, not by r...
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
Shared Culture
© ThoughtWorks 2008
Example: Sharing culture
© ThoughtWorks 2008
Must haves for successful distributed development
© ThoughtWorks 2008
Shared Environments
Must haves for successful distributed development
Shared sense of 3 P’s (Purpose, Priority, Plan)
© ThoughtWorks 2008
Must haves for successful distributed development
© ThoughtWorks 2008
Frequent software demos
Must haves for successful distributed development
Continuous Reflection
and Improvement
© ThoughtWorks 2008
Must haves for successful distributed development
© ThoughtWorks 2008
Frequent visits
Must haves for successful distributed development
Cross functional teams
Excellent relationship with the business
Speedy E...
Good practices still hold
Tools that support distributed teams
Agile development
practices
JIRA
Good practices still hold
...
Conclusion
Distributed Agile: An oxymoron?
© ThoughtWorks 2008
Questions and Comments?
© ThoughtWorks 2008
Questions and Comments?
elizabeth.keogh@thoughtworks.com
patrick.kua@thoughtwo...
Flickr Creative Commons
• Alarm: http://flickr.com/photos/chidorian/7666930/
• Masonic handshake: http://flickr.com/photos...
Upcoming SlideShare
Loading in...5
×

Distributed Agile: An oxymoron?

202

Published on

Isn't Agile = Co-located? How do we work around that and get the most out of Agile?

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
202
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Distributed Agile: An oxymoron?"

  1. 1. Distributed Agile: An oxymoron? elizabeth.keogh@thoughtworks.com patrick.kua@thoughtworks.com © ThoughtWorks 2008
  2. 2. Agile = Co-locatedAgile = Co-located © ThoughtWorks 2008
  3. 3. Agile Manifesto Principles 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. © ThoughtWorks 2008 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
  4. 4. Agile = Co-located © ThoughtWorks 2008 Distributed = Different locations Distributed Agile = An Oxymoron?
  5. 5. Enterprise Software Large Sometimes Distributed Business critical Enterprise Software © ThoughtWorks 2008 Complex Heavily dependent
  6. 6. Our experience… Large Business critical Sometimes Distributed Our experience… © ThoughtWorks 2008 Complex Heavily dependent
  7. 7. Distributed development looks easy © ThoughtWorks 2008 Distributed development looks easy (a slightly fictional story)
  8. 8. Once upon a time…Once upon a time… © ThoughtWorks 2008
  9. 9. there was a team…there was a team… © ThoughtWorks 2008
  10. 10. © ThoughtWorks 2008
  11. 11. working together on the same project…working together on the same project… © ThoughtWorks 2008
  12. 12. …… …… Same project at the same location © ThoughtWorks 2008 …… …… ……
  13. 13. everyone understood each other…everyone understood each other… © ThoughtWorks 2008
  14. 14. © ThoughtWorks 2008
  15. 15. some people wanted the project distributed…some people wanted the project distributed… © ThoughtWorks 2008
  16. 16. = ££££££ + = ££ + $$$$ © ThoughtWorks 2008 = ½ £££
  17. 17. (of course, it might be more than just £££s)(of course, it might be more than just £££s) © ThoughtWorks 2008
  18. 18. they started work with new people in another place... © ThoughtWorks 2008
  19. 19. © ThoughtWorks 2008 New New New New
  20. 20. life was great!life was great! © ThoughtWorks 2008
  21. 21. they would talk over the phone...they would talk over the phone... © ThoughtWorks 2008
  22. 22. …… …… …… © ThoughtWorks 2008 ……
  23. 23. and send email...and send email... © ThoughtWorks 2008
  24. 24. © ThoughtWorks 2008 type type type…
  25. 25. sometimes things would take some time...sometimes things would take some time... © ThoughtWorks 2008
  26. 26. I wonder what Jane meant by I wonder what Jane meant by © ThoughtWorks 2008 Jane meant by that. I better send an email... Jane meant by that. I better send an email... … what’s the gobbleflux about …
  27. 27. That’s an easy one. Here you go. That’s an easy one. Here you go. … Gobbleflux? On the left … © ThoughtWorks 2008 the left …
  28. 28. © ThoughtWorks 2008 On the left? On the left? … on the left of what? …
  29. 29. something that should have been ten minutessomething that should have been ten minutes © ThoughtWorks 2008
  30. 30. stretches to several days...stretches to several days... © ThoughtWorks 2008
  31. 31. !!!!!! … To the left of the widget … © ThoughtWorks 2008 the widget …
  32. 32. There’s a widget? There’s a widget? She’s not even She’s not even © ThoughtWorks 2008 widget?widget? … What widget are you talking about? … not even trying... not even trying...
  33. 33. Why doesn’t he understand? Why doesn’t he understand? … The breadcrumbs widget … © ThoughtWorks 2008 widget …
  34. 34. things continue like that for three months...things continue like that for three months... © ThoughtWorks 2008
  35. 35. until...until... © ThoughtWorks 2008
  36. 36. I can’t wait to see...I can’t wait to see... They’re going to be impressed by this... They’re going to be impressed by this... © ThoughtWorks 2008
  37. 37. A KEY LESSON every physical boundary increases noise © ThoughtWorks 2008 every physical boundary increases noise
  38. 38. © ThoughtWorks 2008 http://www.agilemodeling.com/essays/communication.htm
  39. 39. © ThoughtWorks 2008
  40. 40. cost of distributed development © ThoughtWorks 2008 cost of distributed development (is more than just people)
  41. 41. A more realistic formula = ££££££ + = ££ + $$$$ ½On-shore Distributed © ThoughtWorks 2008 = ££££££ = ££ + $$$$ + Cost of (timely response and shared understanding)
  42. 42. Challenges of Distributed Development Timely decisions Trust and rapport Visibility into progress © ThoughtWorks 2008 Challenges of Distributed Development Look familiar? Shared understanding Working in the same way It’s (almost) the same as co-located development... just much harder.
  43. 43. Must haves for successful distributed development Division by role Functional teams © ThoughtWorks 2008 Analysts Developers Testers Infrastructure
  44. 44. Must haves for successful distributed development © ThoughtWorks 2008 Cross functional teams Division by feature, not by role
  45. 45. Must haves for successful distributed development © ThoughtWorks 2008 Excellent relationship with the business
  46. 46. Must haves for successful distributed development © ThoughtWorks 2008 Speedy Escalation Paths
  47. 47. Must haves for successful distributed development Shared Culture © ThoughtWorks 2008
  48. 48. Example: Sharing culture © ThoughtWorks 2008
  49. 49. Must haves for successful distributed development © ThoughtWorks 2008 Shared Environments
  50. 50. Must haves for successful distributed development Shared sense of 3 P’s (Purpose, Priority, Plan) © ThoughtWorks 2008
  51. 51. Must haves for successful distributed development © ThoughtWorks 2008 Frequent software demos
  52. 52. Must haves for successful distributed development Continuous Reflection and Improvement © ThoughtWorks 2008
  53. 53. Must haves for successful distributed development © ThoughtWorks 2008 Frequent visits
  54. 54. Must haves for successful distributed development Cross functional teams Excellent relationship with the business Speedy Escalation Paths Shared culture Shared environments Shared purpose, priority, plan © ThoughtWorks 2008 Shared purpose, priority, plan Frequent showcases Continue Reflection and improvement Frequent visits
  55. 55. Good practices still hold Tools that support distributed teams Agile development practices JIRA Good practices still hold © ThoughtWorks 2008 Visibility and transparency of informationFace to face time Frequent rotationPrinciples of good teams
  56. 56. Conclusion Distributed Agile: An oxymoron? © ThoughtWorks 2008
  57. 57. Questions and Comments? © ThoughtWorks 2008 Questions and Comments? elizabeth.keogh@thoughtworks.com patrick.kua@thoughtworks.com
  58. 58. Flickr Creative Commons • Alarm: http://flickr.com/photos/chidorian/7666930/ • Masonic handshake: http://flickr.com/photos/gaetanlee/159591865/ • Plane: http://flickr.com/photos/volodimer/400350015/ • East meets west: http://flickr.com/photos/evanosherow/2280507811/ Photo Credits Free wallpaper • Matrix wallpaper: http://www.wallpaperbase.com/wallpapers/movie/matrix/matrix_5.jpg © ThoughtWorks 2008
  1. A particular slide catching your eye?

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

×