Building and Managing a Successful Offshore Team Using Scrum

Transcription

1 Building and Managing a Succeful Offhore Team Uing Scrum Chicago Quality Aurance Aociation Reviion: Building Technologie

2 Building and Managing a Succeful Offhore Team Uing Scrum Welcome & Introduction 2 Building Technologie

3 Agenda Who are we? What i crum? What did we do? What made it work? What difference doe culture make? What challenge do we face? How doe thi compare to other in the indutry? How do our offhore team feel about Scrum? Reource Quetion 3 Building Technologie

4 Who are we? 4 Building Technologie

5 Project Context The InfoCenter Suite Utility Cot Manager InfoCenter Interactive InfoCenter Web Client Animal Facility Report Bundled Report Add-in InfoCenter Server Adminitrator Client Report Manager Client 5 Building Technologie

6 Project Context InfoCenter Characteritic Firt releae in 1998 Viual Baic 6, SQL Server, C++, ASP Approximately 25% of cutomer are Pharmaceutical Firt FDA 21CFR Part11 compliant product of it kind Firt product in SBT to be CMM3 compliant Succeful at Waterfall 6 Building Technologie

7 Project Context The InfoCenter Team Multi-Cultural, cro-dicipline, co-located team Average time on InfoCenter product = 5 year Average level of oftware product development experience = 15 year We put the FUN in dyfunctional Key Project Mgr SW Eng Tet Eng Tech Com 7 Building Technologie

8 InfoCenter 1.6 Pilot for Offhoring Why chooe InfoCenter a the Pilot Program? Experienced table team Succeful at waterfall Piloted other program uccefully (CMM level 3) Lower rik product Lower volume Feature v. date driven Not integrated with hardware Not tied to any other product releae 8 Building Technologie

9 InfoCenter Offhore Pilot Goal Company Goal Flexibility with Reource Improve Time to Market Save Money Team Goal Build a Team in India Succefully utilize offhore reource Ship on time with high quality Long Term: Turn over the maintenance of the product to the offhore team 9 Building Technologie

10 Offhore Pilot Time Line Dec 2005: Got the word Mar 2006: Team (both member) come to the US Apr 2006: Firt Development Iteration May 2006: We viit India Jan 2007: Stable team in India Dicipline Lead in place Working together for couple of iteration Sep 2007: Project Complete 10 Building Technologie

11 InfoCenter Offhore Pilot Project Product Reult 11 Building Technologie

12 What i Scrum? 12 Building Technologie

13 What i Scrum? A et of practice and principle An Agile project management framework Tranparency / Viibility 13 Building Technologie

14 Scrum Principle Working oftware every iteration Delivering the right product Rooted in The Toyota Way principle A holitic (v. equential) approach to product development Simple but Hard 14 Building Technologie

15 Scrum Practice Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 15 Building Technologie

16 What Did We Do? 16 Building Technologie

17 Offhore & Scrum Pilot Why Combine Scrum with the Offhore Pilot? Short iteration Small chunk of work Viibility - Ability to cloely track the progre Frequent retropective and feedback Clear role and reponibilitie Aha! moment Some didn t think thi wa a good idea! 17 Building Technologie

18 Offhore & Scrum Pilot Initial Step Iterative Step Intropective Step 18 Building Technologie

19 Offhore & Scrum Pilot Initial Step Rik Identification and Mitigation Reearch Offhoring (ome poitive, ome negative) Cultural Awarene Training 19 Building Technologie

20 Offhore & Scrum Pilot Initial Step (cont d) Product Backlog Refinement Offhore team lead did firt print with u in the U.S. Detailed Product Training Built a cro-functional team in India Sprint planning calendar 20 Building Technologie

21 Offhore & Scrum Pilot Initial Step (cont d) Went to India! Trained India team in Scrum Face to Face Sprint planning firt two print More Product Training 21 Building Technologie

22 Offhore & Scrum Pilot Initial Step (cont d) Decided to hold Onhore and Offhore team to ame tandard Decided to treat Offhore team a a partner v. conultant Team Bio on SharePoint 22 Building Technologie

23 Offhore & Scrum Pilot Initial Step (cont d) SharePoint 23 Building Technologie

25 Offhore & Scrum Pilot Iterative Step Backlog Refinement Prepare for Sprint Planning #1 Sprint Planning #1 Sprint Planning #2 Sprint Plan Review Sprint Execution Review (Deign, Code, Tet, Documentation) Sprint Demo Sprint Retropective 25 Building Technologie

26 Iterative Step - Backlog Refinement Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 26 Building Technologie

27 Iterative Step Backlog Refinement When? Done during Onhore Sprint, but outide of Sprint (overhead) How Long? 1 hour: 1 requirement -> 2-3 uer torie. About 8 hour per print Deign Note (Uer Storie XYZ.01, XYZ.02, etc.) At thi point original wording of requirement i not important. 27 Building Technologie

28 Iterative Step - Prepare Sprint Planning Meeting #1 Product Owner re-prioritize the Product Backlog Determine bet high priority work to end offhore Allow offhore team time to review the uer torie before 28 Building Technologie

29 Iterative Step - Sprint Planning Meeting #1 Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 29 Building Technologie

30 Iterative Step - Sprint Planning Meeting #1 2-3 hour meeting Review uer torie and UI deign Planning Poker online Great time to oberve offhore team dynamic 30 Building Technologie

31 Iterative Step Sprint Planning #2 & Sprint Plan Review Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 31 Building Technologie

32 Iterative Step Sprint Planning #2 & Sprint Plan Review Face to face once They do it on their own, make their own print Burndown chart Meet to review Sprint Plan Offhore team very good at thi! 32 Building Technologie

33 Iterative Step Sprint Execution Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 33 Building Technologie

34 Iterative Step Sprint Execution Take a look at the Burndown chart Scrum of Scrum Anwer functional and technical quetion Remove impediment 34 Building Technologie

35 Iterative Step Peer Review Review (Deign, Code, Tet, Documentation) Do it during the print Meeting tyle i more efficient and effective A Peer Review i not an Inquiition! 35 Building Technologie

36 Scrum Practice Sprint Planning Meeting #2 (4 Hour) Sprint Planning Meeting #1 (Planning Poker) (4 Hour) Daily Standup Meeting (15 Min) Sprint Demo Meeting (4 Hour) Sprint Retropective Meeting (4 Hour) Backlog Refinement (Ongoing) 36 Building Technologie

37 Iterative Step Sprint Demo & Retropective Product owner need to be there, o plan ahead Can be difficult due to number of people involved Offhore team (7) Onhore liaion (3) Project Manager (1) Product Owner (1) Offhore team really good at thi! Well planned, well delivered demo Format for Retropective Review artifact (Sprint Burndown, Defect, What i done checklit) Open ended quetion worked bet 37 Building Technologie

39 Intropective Step Brought 3 lead from India and one key developer to the US for a couple of week Conducted multi-day braintorming eion (Open Space) for improvement uggetion for next project Created a backlog of improvement effort and tarted working on them. 39 Building Technologie

40 Key Succe Factor 40 Building Technologie

41 Key Succe Factor Attitude Trut Cultural Awarene Relationhip Meet the family Social event Talk about peronal thing before work thing Viit their country Be a good guet Be a good hot (We fell very hort here on their initial trip) 41 Building Technologie

42 Offhore & Scrum Pilot Project Attitude Cultural Awarene Tool Training 42 Building Technologie

43 Key Succe Factor (cont d) Uer Storie Well defined Uer Storie Selection of uer torie Role and Line of Communication Scrum of Scrum meeting (ingle point of contact per dicipline, one for whole project) Offhore Scrum Mater Product Owner Proxy (ex.. Sprint Planning #1 Scrum rule ay that P.O. hould be there) Authority clearly identified, epecially when it i delegated 43 Building Technologie

44 Key Succe Factor (cont d) Long runway for takeoff Partner v. Conultant relationhip Flexibility and patience (work chedule, meeting time, bad connection during meeting, etc.) Giving and receiving honet feedback in a timely fahion 44 Building Technologie

45 Scrum and Culture Different apect of Scrum will be more challenging for different culture Pair Programming Taking Own Work Hierarchy of role Authority Obervation from our experience Scrum a a culture? 45 Building Technologie

46 Ongoing Challenge Face to Face meeting Time zone Scheduling many print review and retropective meeting with the ame et of people involved in each one. Attitude of onhore team Experience level offhore v. onhore (Quality of deliverable) 46 Building Technologie

47 Ongoing Challenge Domain knowledge Configuration Management Availability of Product Owner (Product Owner proxy i a good olution) Giving honet, direct feedback in a timely fahion Meauring the right thing (quality v. quantity, donene ) Growing leader (attitude, kill, product knowledge, willingne to travel) Support time required of onhore team Infratructure 47 Building Technologie

48 Indutry Comparion Agile Offhoring : It' hard work but it work! poted by: Vika Hazrati on May 11, 2007 A an advice for the offhoring indutry, follow Scrum with the Toyota principle in pirit without diluting their eence. Apply them to your way of working and ee the magic unfold. Uing an Agile Software Proce with Offhore Development by Martin Fowler We may never really undertand the pro and con offhore development. Software development i an activity who' output i impoible to meaure. A uch we'll never have hard number to prove one approach better than another. What we will ee i growing qualitative feedback on the benefit of agility and offhore development - thee qualitative aement will determine if either, or both, will urvive Building Technologie

49 Indutry Comparion (cont d) Ambaador Model for Effectively Ditributed Agile Team (by BigViible rep Giora Morein and George Schlitz at the 2008 Scrum Gathering) 49 Building Technologie

50 Thought From India Scrum Benefit Scrum i epecially beneficial in monitoring and controlling activitie in all ite Communication i key regular Scrum of Scrum meeting provide the mean. Regular retropective are effective to get immediate and actual feedback Detailed Uer Storie were a great benefit to offhore team. Thi noto-bookih approach i really amazing!! Team like the reult driven approach Since each print need to be a complete delivery, we urely end up having a product more detailed and of higher quality. Scrum i mut when anyone i thinking of Off Shoring!!! 50 Building Technologie

51 Thought From India Scrum Challenge Keeping everybody alway on toe to perform, deliver and demontrate People were ued getting their work choen for them. Now in Scrum they are free to chooe from Sprint Backlog. The challenge i to pick up the right tak and coordinate effectively. Handling impediment in a timely fahion Effective daily meeting reporting to the team v. manager Stringent deadline Ability to deliver within tipulated time frame depite obtacle 51 Building Technologie

52 Future Contant integration Automated regreion teting Ambaador Program Automated and objective meaure of code quality 52 Building Technologie

53 InfoCenter Offhore Pilot Goal Company Goal Flexibility with Reource Improve Time to Market Save Money Team Goal Build a Team in India Succefully utilize offhore reource Ship on time with high quality Long Term: Turn over the maintenance of the product to the offhore team 53 Building Technologie

54 Reource Agile Alliance Control Chao Mountain Goat Software Planning Poker Scrum Alliance 54 Building Technologie

55 Contact Information 55 Building Technologie