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 is Distributed Agile? a } Distributed Scrum d } n Preparation e } Communication g } Coordination A } Technical } Final Thoughts } References } Q & A/Insights

} Facilitate different roles ( P M , D e v e A l o e r p c h e i r t , e c M } First Agile experience t ) t d a t e u s b a c } Masters thesis was on k o t o 2 0 0 8 b D i s A t r i b u t } Continued research… e d A g i l l e l A s ’ t I

} Teams or team members s a d r e i n ? o t e c t } not necessary o e l l o a c a t t e l d u h i g b } W to be geographically A i r dispersed t s } spread across time zones i D

d m e u t u r b c Isolated Scrums Distributed i S r Scrum of Scrums t s i D Totally Integrated Scrums 3 Models

} Isolated Scrums d m } teams are not cross- e u t functional and may not be u r using the Scrum process b c } i S teams typically abandon r t Scrum and fall back to s i Waterfall D } common in many outsourced development efforts

} Distributed Scrum of d S m c r u e m s } u t isolation across u r b geographies c i S } integrated by a Scrum of r t s Scrums that meets i regularly D } Promotes sub-team unity as opposed to team unity.

} Totally Integrated S c r u d m s m } e cross-functional across u t u geographies. r b } c The project is integrated i S r into a single whole. t } s Single code base. i D } Retain core knowledge. } Recommended for experienced Agile teams

n } What can be done to o i p r e t p a r a e ? r a p e r P

g n n o i } Experience i m t a o } r Don’t jump to Distributed c a r Agile, try Agile first. p e e v r O P

g n n } Training & Certification o i i m t } a Bring in a coach o r c } a High-level training on r p e integration systems e v r O P

g n n o } Travel i i m t a } o Visas, passports r c a } r Immunizations p e e v r O P

} n Misinterpretation o } Delayed responses i t } a Different languages/ c cultures i n u m m o C

g n n } Team Unity o i i m t } a Bring everyone together o c c at the beginning (if i n r possible) e u } v m - W h a O } t i s Avoid the Blame Game t h e p m r o d u c t v i s i o n ? o C

} In Practice } g Use simple language, slow n n down, read body language o i } i m Agree on Agile terms and t a o practices c c } i Take advantage of n r e u collaboration tools v m } O I M , V i m d e o W C e o b n f c } e a r m e n Don’t rely on email alone s , c e i o n t c g . , C

g } Camaraderie n n o i } i m Celebrate holidays, t a customs o c } c i Send e-cards, gift boxes n r e } u Incorporate pictures, fun v m facts into presentations O m o C

} Duplication of effort, re- work } n Opposite time zones o } Difficulty acquiring i t a domain knowledge n } Difficulty synchronizing i d work between sites r o o C

} D e d i c a t e e q d u r i p o o m } m e g s n t a n I d t n e r a t i o n n s } Start with 2-week long sprints o i i m a n d } t a d j u s S a t t r a o c c n o g o r d S i n c g n r } Possibly a weekly meeting which u l y m o c f S c i r u m m r s u d s } t b e a e O t t e v n e r d r e l a d p i n v w p } Adjust the daily Scrum o o e r r k s i o n n g } h O o o u r s I n c o r p C } o r a t e P a r o t e j e a c m t s t c a h a k u l e e t d n s o d v w a a n r c a ( t e i o v n e ) r y o n e

g n Travelling Product Owner n o i i m t a o Chicago n c i r d e r v o Seattle Dallas O o C New Phoenix York

Product Owner g n Phoenix n o i i m t a Split Teams Geographically o n c i r d Team A Team B Team C e r v o O o Phoenix Phoenix Phoenix C Atlanta Atlanta Atlanta Boston Boston Boston

g n Chief Product Owner/Scrum Master n o i i m t a o n c i r d e r v o O o C www.solutionsiq.com

} Toolset } Integration issues l a c } Incompatible data i n f h o r m a t s , c s t a n d a e r d s , e t c T .

} May require additional g l t o o n a l s . c i } m DVCS i n } o CI is a must h c } Consider 3 rd party c r e e s T e r v v i c e s t o i O n h f r o a s s t t r u c t l a u t r e e n t c o y a l l e v i a t e

g l n a } Integration c i m i } n Incorporate integration o h c tests early c r } e Introduce a integration e T v team O

} Maximize face time } Travel when necessary } Distributed Agile is not a s g t o o d h f i t f o o r r g a g l a l n i z a } Re-evaluate and take t i u o n s o c h o r r e c t i v T e e n a c d t i o o f n e a a l } SAFe, LeSS, DASD, t c t h h e s a p r i n t n p r o i g r e s F s i o n o f D A

} J. Sutherland, A. Viktorov, J. Blount, and N. s Puntikov, "Distributed scrum: Agile project e management with outsourced development teams," in Hawaii International System c Sciences (HICSS) 2007 Hawaii, 2007, p. 274. n } M. Rajpal, “Challenges in Distributed Agile e Software Development” r } e My sister f e R

Q & A / I n s i g h t s