Olha Moroz9/15/2010Distributed Scrum – Keys to Successby Olha Moroz Project Manager, SoftServe
Statistics
What’s the deal?DistanceCultureTimeLanguage
The TeamUSUADev TeamQA TeamDev TeamQA TeamSupportDev ManagersSupportProject ManagerQA ManagerProduct Managers
The Team4 Hours of OverlapDev TeamQA TeamDev TeamQA TeamSupportDev ManagersSupportProject ManagerQA ManagerProduct Managers
Fully Distributed ScrumDifferent LocationsSingle Sprint BacklogSingle Sprint GoalShared Code OwnershipCross - Functional
Fully Distributed ScrumSMDevQADevQADevQADevQADevQADevQADevQADevQAUAUSSMSMSMPOPOPOPO
Key 1 – Common VisionDomain KnowledgeReal UsersRelease DatesMarket NeedsCompetitors
Key 2 – Right PeopleFlexible to the ChangeReady to LearnNot Afraid of ChallengesTeam PlayersAgile!
Key 3 – EducationBasic KnowledgeInitial TrainingCoaching ProgramOn Site Kick-offAssessment
Key 4 – LanguageTalkListen and HearUnderstand
Key 5 – CommunicationOn Site VisitsVideo on Each MeetingWhole Team on Each MeetingToolsDaily Updates
Key 6 – Socializing and CulturePersonal RelationshipsEquality
Key 7 – Visibility and TransparencyShared ToolsShared Definition of DoneExpertiseShared Sprint BacklogScrum of Scrums
Key 8 – InfrastructureShared CodebaseContinuous IntegrationDaily BuildsTest AutomationHardware and Software
Key 9 – Product Owner
Key 10 – AdjustmentTeam Culture and StandardsAdjust Work HoursTeam Conventions and Agreements
Master Key – Common SenseThe Art of Possible
AchievementsIncreased CommunicationImproved EstimationBetter at Planning, Tracking and Changing PrioritiesMore ContextResponsibility and Ownership
Thank you!“If everyone is moving forward together, then success takes care of itself” Henry Ford

Distributed scrum keys to success