SLIDE 1
Overcoming Challenges in Distributed Agile
M a r k R a j p a l , M . S c . C S M , C S P O , C S P , P M I
- A
C P , P M P m a r k @ m a r k r a j p a l . c
- m
Overcoming Challenges in Distributed Agile . c S . M , l a - - PowerPoint PPT Presentation
Overcoming Challenges in Distributed Agile . c S . M , l a - - PowerPoint PPT Presentation
Overcoming Challenges in Distributed Agile . c S . M , l a p j a R P k M r a P M , P C A - I M m P o , P c S . C l a , p O j a P r S k C r a , m M @ S C k r a m } About Me } What
SLIDE 2
SLIDE 3
I t ’ s A l l A b
- u
t M e
} Facilitate different roles
( P M , D e v e l
- p
e r , A r c h i t e c t )
} First Agile experience
d a t e s b a c k t
- 2
8
} Masters thesis was on
D i s t r i b u t e d A g i l e
} Continued research…
SLIDE 4
W h a t i s D i s t r i b u t e d A g i l e ?
} Teams or team members
a r e n
- t
c
- l
l
- c
a t e d
} not necessary
} to be geographically
dispersed
} spread across time zones
SLIDE 5
D i s t r i b u t e d S c r u m
3 Models
Totally Integrated Scrums Distributed Scrum of Scrums Isolated Scrums
SLIDE 6
D i s t r i b u t e d S c r u m
} Isolated Scrums
} teams are not cross-
functional and may not be using the Scrum process
} teams typically abandon
Scrum and fall back to Waterfall
} common in many
- utsourced development
efforts
SLIDE 7
D i s t r i b u t e d S c r u m
} Distributed Scrum of
S c r u m s
} isolation across
geographies
} integrated by a Scrum of
Scrums that meets regularly
} Promotes sub-team unity
as opposed to team unity.
SLIDE 8
D i s t r i b u t e d S c r u m
} Totally Integrated
S c r u m s
} cross-functional across
geographies.
} The project is integrated
into a single whole.
} Single code base. } Retain core knowledge. } Recommended for
experienced Agile teams
SLIDE 9
P r e p a r a t i
- n
} What can be done to
p r e p a r e ?
SLIDE 10
O v e r c
- m
i n g P r e p a r a t i
- n
} Experience
} Don’t jump to Distributed
Agile, try Agile first.
SLIDE 11
O v e r c
- m
i n g P r e p a r a t i
- n
} Training & Certification
} Bring in a coach } High-level training on
integration systems
SLIDE 12
O v e r c
- m
i n g P r e p a r a t i
- n
} Travel
} Visas, passports } Immunizations
SLIDE 13
C
- m
m u n i c a t i
- n
} Misinterpretation } Delayed responses } Different languages/
cultures
SLIDE 14
O v e r c
- m
i n g C
- m
m u n i c a t i
- n
} Team Unity
} Bring everyone together
at the beginning (if possible)
}
- W
h a t i s t h e p r
- d
u c t v i s i
- n
?
} Avoid the Blame Game
SLIDE 15
O v e r c
- m
i n g C
- m
m u n i c a t i
- n
} In Practice
} Use simple language, slow
down, read body language
} Agree on Agile terms and
practices
} Take advantage of
collaboration tools
}
I M , V i d e
- C
- n
f e r e n c i n g , W e b c a m s , e t c .
} Don’t rely on email alone
SLIDE 16
O v e r c
- m
i n g C
- m
m u n i c a t i
- n
} Camaraderie
} Celebrate holidays,
customs
} Send e-cards, gift boxes } Incorporate pictures, fun
facts into presentations
SLIDE 17
C
- r
d i n a t i
- n
} Duplication of effort, re-
work
} Opposite time zones } Difficulty acquiring
domain knowledge
} Difficulty synchronizing
work between sites
SLIDE 18
O v e r c
- m
i n g C
- r
d i n a t i
- n
}
D e d i c a t e d r
- m
s a n d e q u i p m e n t
}
I t e r a t i
- n
s
} Start with 2-week long sprints
a n d a d j u s t a c c
- r
d i n g l y
}
S t r
- n
g S c r u m
- f
S c r u m s
} Possibly a weekly meeting which
m u s t b e a t t e n d e d i n p e r s
- n
}
O v e r l a p w
- r
k i n g h
- u
r s
} Adjust the daily Scrum
}
I n c
- r
p
- r
a t e a t e a m c a l e n d a r
}
P r
- j
e c t s h u t d
- w
n ( e v e r y
- n
e t a k e s v a c a t i
- n
)
SLIDE 19
O v e r c
- m
i n g C
- r
d i n a t i
- n
Chicago Dallas New York Phoenix Seattle
Travelling Product Owner
SLIDE 20
O v e r c
- m
i n g C
- r
d i n a t i
- n
Split Teams Geographically
Team A
Phoenix Atlanta Boston
Team B
Phoenix Atlanta Boston
Team C
Phoenix Atlanta Boston
Product Owner
Phoenix
SLIDE 21
O v e r c
- m
i n g C
- r
d i n a t i
- n
www.solutionsiq.com Chief Product Owner/Scrum Master
SLIDE 22
T e c h n i c a l
} Toolset } Integration issues } Incompatible data
f
- r
m a t s , s t a n d a r d s , e t c .
SLIDE 23
O v e r c
- m
i n g T e c h n i c a l
} May require additional
t
- l
s .
} DVCS } CI is a must
} Consider 3rd party
s e r v i c e s t
- h
- s
t i n f r a s t r u c t u r e t
- a
l l e v i a t e l a t e n c y
SLIDE 24
O v e r c
- m
i n g T e c h n i c a l
} Integration
} Incorporate integration
tests early
} Introduce a integration
team
SLIDE 25
F i n a l T h
- u
g h t s
} Maximize face time
} Travel when necessary
} Distributed Agile is not a
g
- d
f i t f
- r
a l l
- r
g a n i z a t i
- n
s
} Re-evaluate and take
c
- r
r e c t i v e a c t i
- n
a t t h e e n d
- f
e a c h s p r i n t
} SAFe, LeSS, DASD,
p r
- g
r e s s i
- n
- f
D A
SLIDE 26
R e f e r e n c e s
}
- J. Sutherland, A. Viktorov, J. Blount, and N.
Puntikov, "Distributed scrum: Agile project management with outsourced development teams," in Hawaii International System Sciences (HICSS) 2007 Hawaii, 2007, p. 274.
}
- M. Rajpal, “Challenges in Distributed Agile
Software Development”
}
My sister
SLIDE 27