Patterns For Successful Distributed Development - Agileee2009

1,051
-1

Published on

8 Patterns for Successful Distributed Development with agile and lean

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,051
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Patterns For Successful Distributed Development - Agileee2009

  1. 1. Patterns for Successful Distributed Development Mads Troels Hansen Agileee 2009, Kyiv, Ukraine © 2009 Mads Troels Hansen
  2. 2. My background • Mads Troels Hansen Agile and Lean Coach at BestBrains, Denmark. Mads has more than 15 years of experience with software development, as developer, project manager, product owner, CIO and CTO in different companies. He is very experienced in working with Scrum, Agile and Lean in a distributed environment and is Certified Scrum Practitioner. mth@bestbrains.dk, +45 6082 2282 . September 09, © 2009 Mads Troels Hansen 2
  3. 3. • Agile team – Co-located, face-to-face collaboration – Task board on the wall September 09, © 2009 Mads Troels Hansen 3
  4. 4. • 8 Patterns for Successful Distributed Development September 09, © 2009 Mads Troels Hansen 4
  5. 5. Structure • Visibility and Transparency TRUST – Use Google Docs or another online tool – Physical task boards whenever possible September 09, © 2009 Mads Troels Hansen 5
  6. 6. Structure • Focus on problem solving – DO regular retrospectives, online and offline – Find root cause, not only symptoms September 09, © 2009 Mads Troels Hansen 6
  7. 7. Structure • Establish flow and remove bottlenecks – Limit Work In Progress, CF Diagrams – Value Stream Mapping September 09, © 2009 Mads Troels Hansen 7
  8. 8. Structure • A normal way of folding hands September 09, © 2009 Mads Troels Hansen
  9. 9. Structure • Change the structure September 09, © 2009 Mads Troels Hansen
  10. 10. Rhythm • Regular rhythm in teams and between teams – Planning, coordination, releases – Establish a cadence September 09, © 2009 Mads Troels Hansen 10
  11. 11. Rhythm • Business and technical feedback rhythms – Sneak preview, demonstrations – Continuous Integration September 09, © 2009 Mads Troels Hansen 11
  12. 12. Technical Infrastructure • Highly automated and fast – Simple tools September 09, © 2009 Mads Troels Hansen 12
  13. 13. Technical Infrastructure • Remove dependencies to other locations – It must be fast to integrate and test September 09, © 2009 Mads Troels Hansen 13
  14. 14. Communication Protocols • Use VIDEO whenever possible – Distributed face-to-face communication – Use different tools for distributed communication September 09, © 2009 Mads Troels Hansen 14
  15. 15. Communication Protocols • Prepare the distributed meetings – Use checklists and remember to ask questions September 09, © 2009 Mads Troels Hansen 15
  16. 16. Communication Protocols • Pomodoro technique – Distributed team – Local team September 09, © 2009 Mads Troels Hansen 16
  17. 17. Shared Product Vision • Understand the vision and key features – User Story Mapping, a picture of the whole system – Innovation Games, learning from customers September 09, © 2009 Mads Troels Hansen 17
  18. 18. Shared Product Vision • Prepare requirements with acceptance criteria – Easier to test and validate – Focus on need not solution September 09, © 2009 Mads Troels Hansen 18
  19. 19. Domain Knowledge • What you don’t know you don’t know • Ask questions • Innovation Games September 09, © 2009 Mads Troels Hansen 19
  20. 20. Domain Knowledge • Physical outputs and business workflow – Learn what the solution will produce – Understand how the user will use it September 09, © 2009 Mads Troels Hansen 20
  21. 21. Development Practices • Slice the system by feature not layer – Integrate and test in small steps – Risk first September 09, © 2009 Mads Troels Hansen 21
  22. 22. Development Practices • From “Ready, Ready” to “Done, Done” – Agree and define your “Done, Done” criteria – Validate requirements with “Ready, Ready” criteria September 09, © 2009 Mads Troels Hansen 22
  23. 23. Cross cultural understanding • Regular face-to-face visits – Distributed teams working together, same office – Solve problems together September 09, © 2009 Mads Troels Hansen 23
  24. 24. People don’t resist change, they resist being changed. - Peter Scholtes Thank you Send me your distributed stories: mth@bestbrains.dk September 09, © 2009 Mads Troels Hansen 24
  25. 25. References • Innovation Games, Luke Hohmann www.innovationgames.com • User Story Mapping, Jeff Patton http://www.agileproductdesign.com/presentations/user_story_mapping/index.html • Distributed Pomodoro: CherryTomato http://www.chrylers.com/cherrytomato/ • Agile 2009 Paper: Agile for Distributed Teams http://tinyurl.com/CmmiAgile September 09, © 2009 Mads Troels Hansen

×