making scrum distributed great!': pete deemer @ colombo agile conference 2014

15
Making Distributed Scrum Great! Pete Deemer [email protected]

Upload: colombocampscommunity

Post on 10-May-2015

268 views

Category:

Software


2 download

DESCRIPTION

Is agility really possible when people are thousands of miles apart from each other? Yes! In this talk, Pete Deemer shared tips and techniques gleaned from nearly a decade of working with distributed Scrum teams in Asia.

TRANSCRIPT

Page 1: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

Making DistributedScrum Great!

Pete [email protected]

Page 2: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

Is “Distributed” and “Agile”

a contradiction?

Page 3: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014
Page 4: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

Distributed projects actuallybenefit the most from Agile

Page 5: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

…because they have the most room for improvement

Page 6: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

2007 Study of software projectsof similar size and complexity

Average time required to complete:

Colocated teamsDistributed teams

48.3 days97.3 days

Espinosa, Slaughter, Kraut, and HerbslebOrganization Science, Jul-Aug 2007

Why?!

Page 7: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

So how does Scrum help us?

Working software early and often

Inspection and Retrospection

Visibility about the “leaks”

Adaptation: Action to improve

+

Page 8: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

The Big 4 “Leaks”:

CommunicationCollaborationRelationshipTechniques

Page 9: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

• ScrumMaster should be located with Dev Team• Short Sprints – 2 weeks or less• Dev Team does Daily Scrum during local business

hours• Real-time meetings between Dev Team and Product

Owner must be visual, not just audio

Product Owner in Location ADev Team in Location B

Page 10: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014
Page 11: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

• ScrumMaster should be located with Dev Team• Short Sprints – 2 weeks or less• Dev Team does Daily Scrum during local business

hours• Real-time meetings between Dev Team and Product

Owner must be visual, not just audio• Standing weekly call for Product Owner and Dev

Team (in addition to lots of other interactions)• Product Owner to Dev Team location for project

kickoff• Product Owner visits Dev Team location regularly

Product Owner in Location ADev Team in Location B

Page 12: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

• To be effective, Dev Team bonding must occur• Dev Team members colocated for first Sprint• Ongoing “ambassadorship”• Multiple forms of continuous live communication• Daily Scrum live via webcam

Dev Team split between two (or more) separate locations

Page 13: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014
Page 14: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

• To be effective, Dev Team bonding must occur• Dev Team members colocated for first Sprint• Ongoing “ambassadorship”• Multiple forms of continuous live communication• Daily Scrum live via webcam• Scrum Artifacts maintained using electronic tool• Test-driven Development• Continuous Integration

Dev Team split between two (or more) separate locations

Page 15: Making Scrum Distributed Great!': Pete Deemer @ Colombo Agile Conference 2014

free download from distributedscrumprimer.com