Distributed Agile Development - PO Perspective

1,672 views

Published on

This lecture was given in the Annual Agile conference in Brno, Czeck Republic - Agilia 2012
Th lecture discuss the distributed Agile model from the Product Owner perspective - how to overcome the challenge of efficient knowledge transfer as in distributed model the product owner is almost always far from the team. It discusses various team models, onsite visits, communication means, roles in the team, documentation and more

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,672
On SlideShare
0
From Embeds
0
Number of Embeds
88
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Distributed Agile Development - PO Perspective

  1. 1. Distributed Agile Development– PO Perspective Aviram Eisenberg, CEO, Ignite
  2. 2. Agile 1.0 & Globalization 3.0The Agile Manifesto was written in 2001before global development teams where sopopularIn 2003 there was only a single decentarticle publicly available describing anAgile-based global delivery model
  3. 3. Common Distributed Models 1 2 3 4Product Owner Product Owner Product Marketing Project ManagerScrum Master PO Proxy Product Owner Product OwnerScrum Team Scrum Master Scrum Master Scrum Master Scrum Team Scrum Team Scrum Team
  4. 4. Common Distributed Models 5 6 7 Product Owner Product Owner Product OwnerScrum Master Scrum Master Scrum Master Scrum MasterScrum Team Scrum Team Scrum Team Scrum Team In almost all models PO is not located near the Scrum team Decision making is almost always not located near the team
  5. 5. Agile and Distributed DevelopmentAgile makes knowledge transfer moreefficientAgile identify offshore mistakes fasterAgile makes offshore visibleAgile keep offshore teams on trackYet, Agile practices and offshore practicescontradict!
  6. 6. Agile and Distributed DevelopmentFace to face communicationMultiple interfaces, single interfaceCross-functional teams vs. ComponentownershipJust enough documentation vs formaldocumentation
  7. 7. It’s ALL about communicationAgile promotes face-to-face communicationLogistically problematicNot cost-effectiveAmbassador exchange program People that know each other well communicate better when they are apart Bring the team to onsite training on project launch Send the product owner to the offshore location once a quarter Bring the scrum master on major deliveries to the customerLocate the team in similar time zone
  8. 8. It’s ALL about communicationEmail – asynchronous messagingIM – the presence advantage and themisuse riskVOIP phones/SkypeWeb-Conference – a mustVideo Conference systemWiki – a must
  9. 9. Team Structure - co-located waterfall Product Marketing Product Management ArchitectGraphic Design Copyright/ Usability Marketing writing R&D Manager R&D Teams Test Teams R&D Teams Test Teams R&D Teams Test Teams R&D Teams
  10. 10. Team Structure – co-located Scrum Product Marketing Product OwnerGraphic Design Copyright/ Usability Marketing writing R&D Teams R&D Teams R&D Teams Scrum Teams
  11. 11. Team Structure – Distributed ScrumKeep interfaces simple as possible Product Marketing Product Owner HL ArchitectGraphic Design Usability Copyright/ Marketing writing Scrum Master Scrum Master Scrum Master Scrum Team Scrum Team Scrum Team
  12. 12. The Scrum challengeScrum promotes Scrum…Offshore best practice – have as simpleonsite-offshore interfaces as possibleDistributed Agile best practices: Product owner “hides” the rest of the stake holders or SMEs in the day-to-day Scrum Master does assume some of the traditional team leader roles Team dailys + PO-SM dailys
  13. 13. Work DistributionAgile promotes user stories as opposed tocomponent featuresOffshore best practice – give the team ownershipof component(s)Alternative 1 : Invest in a distributed configuration management Invest in a distributed integration system Invest in knowledge transfer and trainingAlternative 2: Give offshore teams component responsibility Do Agile in the micro level
  14. 14. DocumentationAgile promotes just enough documentationOffshore best practice – formalized anddetailed documentationDid I mention Wiki??? User stories Planning games Standup meetingsLoad user stories to Wiki prior to planninggame
  15. 15. Knowledge TransferTwo-folds challenge Train offshore teams on existing code base Train onsite staff on deliverablesOffshore training Do the first sprints co-located Next sprints should be for bug fixingOnsite training Product demonstrations during deliveries Onsite training by Scrum master before releaseTwo-way Wiki User stories are loaded by the onsite product owner Tests, design decisions, planning is loaded by offshore team
  16. 16. Q&A Aviram Eisenberg Ignite www.igniteso.comaviram@Igniteso.com

×