Agile distributed teams

Agile distributed teams

• 1.
  Agile Distributed TeamsArielSchapiro – ariel.schapiro@southworks.net
• 2.
  Stats
• 3.
  Stats32% + 13%=45%
• 4.
  Why distributed?Global marketsCostsSpecializationTalent“Followthe sun”
• 5.
  “High-bandwidth communication isone of the core practices of Scrum… The best communication is face to face, with communications occurring through facial expression, body language, intonation, and words. When a white board is thrown in and the teams work out design as a group, the communication bandwidth absolutely sizzles.”Ken Schwaber,The Enterprise and ScrumCo-located
• 6.
  War-rooms vs. cubiclesCo-located
• 7.
  Co-locatedProductivityActivitiesDistraction and recognition
• 8.
  Distribution levelsDevsCustomerQASponsor
• 9.
  Challenges
• 10.
  GoalMinimize impact
• 11.
  CommunicationHOWWHATStatus, plan, progress,Problems,discussions, expositions, training, complaints, congratulations, help…Frequent but efficientChannels for every needBalanced coordination and points of reference“Share the pain”
• 12.
  Follow-up meetingsPresentations: inspiring,easy to follow, to the pointLive meeting minutes / collaborativeCheckpoints (open questions, summaries)“sorry I was on mute”
• 13.
  Slide 47 witha very long title (the “anti slide”)Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Maecenas porttitorconguemassa. Fusceposuere, magna sed pulvinarultricies, puruslectusmalesuada libero, sitametcommodo magna eros quis urna. Nunc viverraimperdietenim. Fusceest.Vivamus a tellus. Pellentesquehabitantmorbitristiquesenectus et netus et malesuadafamesacturpisegestas. Proinpharetranonummypede. Mauris et orci. Aeneanneclorem.In porttitor. Doneclaoreetnonummyaugue. Suspendisse dui purus, scelerisque at, vulputate vitae, pretiummattis, nunc. Maurisegetneque at semvenenatiseleifend. Utnonummy.Fuscealiquetpede non pede. Suspendissedapibuslorempellentesque magna. Integernulla. Donecblanditfeugiat ligula. Donechendrerit, felis et imperdieteuismod, purus ipsum pretiummetus, in lacinianullanislegetsapien.
• 14.
  Email1:1-N Formal Discussions
• 15.
  IM1:1Ideas/thoughtsTool to getcloserStatus (available, busy, etc.)Availability + progressTo the pointFormal (?)FocusExitSensitive issues
• 16.
  Phone1:1Urgency/sensitive issueToneOfficialAvailabilityAgenda
• 17.
  Repository“Maps and dictionaries”VideosToolsBacklogIssuesSharedKnowledge
• 18.
  Change of channelsMinimumdoc necessarySketches  “specltes”  docOrganization based on distribution (Conway’s Law)Flexible process
• 19.
  TrustFrequent visits (sponsors,team members)Feedback:1:1RetrospectivesPrevious team cohesion
• 20.
  Sample
• 21.
  Thanks!
• 22.
  References and recommendedreadingsScrum and XP from the Trenches - Henrik KnibergThe Enterprise and Scrum - Ken SchwaberA Practical Guide to Distributed Scrum – Elizabeth WoodwardAdapting Agile Methods for Complex Environments - IBMGlobal Development and Delivery in Practice (GDD) – IBMDistributed Agile Development at Microsoft patterns & practices – Ade MillerState of Agile Survey 2010 – VersionOneHow Does Radical Collocation Help a Team Succeed? - Stephanie TeasleyExploring the Duality between Product and Organizational Architectures: A Test of the “Mirroring” - Alan MacCormackHypothesis 2008 IT Project Success Rates Survey Results - Ambysoft