More Related Content
Similar to Distributed Agile: An Oxymoron?
Similar to Distributed Agile: An Oxymoron? (20)
More from Thoughtworks (20)
Distributed Agile: An Oxymoron?
- 1. Distributed Agile: An oxymoron?
elizabeth.keogh@thoughtworks.com
patrick.kua@thoughtworks.com
© ThoughtWorks 2008
- 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.
Crystal Clear
(principles)
XP Practices
On-site
customer
Osmotic Communication
Collective Code
Ownership
Easy access to
expert users
Lean Software
Development
DSDM
(principles)
Waiting
Active user involvement
Unnecessary
Transportation
Unnecessary Movement
© ThoughtWorks 2008
- 26. I wonder what
Jane meant by
that. I better send
an email...
… what’s the
gobbleflux about …
© ThoughtWorks 2008
- 36. I can’t wait to see...
They’re going to be
impressed by this...
© ThoughtWorks 2008
- 41. A more realistic formula
On-shore
Distributed
½
+
= ££ + $$$$
= ££££££
+ Cost of (timely response
and shared understanding)
© ThoughtWorks 2008
- 42. Visibility into progress
Trust and rapport
Timely decisions
Challenges of Distributed Development
Look familiar?
It’s (almost) the same as co-located development... just much harder.
Working in the same way
Shared understanding
© ThoughtWorks 2008
- 43. Must haves for successful distributed development
Analysts
Developers
Testers
Functional teams
Division by role
© ThoughtWorks 2008
Infrastructure
- 44. Must haves for successful distributed development
Cross functional teams
Division by feature, not by role
© ThoughtWorks 2008
- 45. Must haves for successful distributed development
Excellent relationship
with the business
© ThoughtWorks 2008
- 46. Must haves for successful distributed development
Speedy Escalation Paths
© ThoughtWorks 2008
- 47. Must haves for successful distributed development
Shared Culture
© ThoughtWorks 2008
- 49. Must haves for successful distributed development
Shared Environments
© ThoughtWorks 2008
- 50. Must haves for successful distributed development
Shared sense of 3 P’s (Purpose, Priority, Plan)
© ThoughtWorks 2008
- 51. Must haves for successful distributed development
Frequent software demos
© ThoughtWorks 2008
- 52. Must haves for successful distributed development
Continuous Reflection
and Improvement
© ThoughtWorks 2008
- 53. Must haves for successful distributed development
Frequent visits
© ThoughtWorks 2008
- 54. Must haves for successful distributed development
Excellent relationship with the business
Speedy Escalation Paths
Cross functional teams
Shared culture
Shared environments
Frequent showcases
Shared purpose, priority, plan
Continue Reflection and
improvement
Frequent visits
© ThoughtWorks 2008
- 55. Agile development
practices
JIRA
Tools that support distributed teams
Good practices still hold
Principles of
good teams
Frequent rotation
Visibility and transparency
of information
Face to face time
© ThoughtWorks 2008
- 58. Photo Credits
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/
Free wallpaper
•
Matrix wallpaper: http://www.wallpaperbase.com/wallpapers/movie/matrix/matrix_5.jpg
© ThoughtWorks 2008
