pretty good scrum: secret sauce for distributed teams - Sprettur

Recommendations

Info

Team Characteristics � TDD, pair programming, continuous integration. Same tools and techniques onshore and offshore. � Daily Scrum meeting of team across geographies. � SmartBoards, wikis, and other tools used to enhance communication. � Indians say it feels exactly the same in India as it does in Amsterdam. They do the same thing in the same way. � Xebia CTO has decided to use this model on all projects because it provides (counterintuitively) better customer focus and all other metrics are the same onshore or offshore. © Jeff Sutherland 1993-2008 48
Resolving Cultural Differences � One of the <strong>teams</strong> had local velocity decrease after distributing the team. � Root cause analysis indicated the Indians were waiting <strong>for</strong> the senior Indian developer to tell them what to do. � The same day this was determined, the Dutch ScrumMaster became a team member and the lead Indian developer became the ScrumMaster with the goal of eliminating the impediment. � Distributed velocity immediately went up to previously established local velocity. © Jeff Sutherland 1993-2008 49
Page 1 and 2: PRETTY GOOD SCRUM: SECRET SAUCE FOR
Page 3 and 4: Agile Manifesto Where did Agile Dev
Page 5 and 6: © Jeff Sutherland 1993-2008 5
Page 7 and 8: ScrumButt © Jeff Sutherland 1993-2
Page 9 and 10: Scrum Drivers Human Values Business
Page 11 and 12: Business Value Product Backlog prio
Page 13 and 14: Self-Organization: Complex Adaptive
Page 15 and 16: Books on Scrum drivers ... � Huma
Page 17 and 18: Gustav Bergman. Ken Schwaber: The S
Page 19 and 20: Avoiding ScrumButt - Nokia Test Ori
Page 21 and 22: Nokia Test - Part 2 • You know wh
Page 23 and 24: Can failure help us? How many diffe
Page 25 and 26: How we invented Scrum: Alan Kay’s
Page 27 and 28: Out of the Box � Scrum looked at
Page 29 and 30: Distributed/Outsourcing Styles Isol
Page 31 and 32: SirsiDynix - Anatomy of a failed pr
Page 33 and 34: SirsiDynix Distributed Scrum � Sc
Page 35 and 36: Scrum[1] Waterfall[1] SirsiDynix[2]
Page 37 and 38: Research Issue � SirsiDynix was a
Page 39 and 40: Going Fast is Important � If you
Page 41 and 42: Setting up a prospective study �
Page 43 and 44: Case study: Building a new railway
Page 45 and 46: ProRail PUB Example � ProRail res
Page 47: ProRail Defect Tracking ! 900! 800!
Page 51 and 52: Linear Scalability of Large Scrum P
Page 53 and 54: Conclusion Fully Distributed Scrum
Page 55 and 56: Avoid Thrashing ... Ability to Exec
Page 57 and 58: Cosmic Stopping Problem � Early c
Page 59 and 60: Metastable State � At less than 2
Page 61 and 62: Software Metastable State � If ve
Page 63 and 64: Goal - double output, more than dou

pretty good scrum: secret sauce for distributed teams - Sprettur

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?