Experiences of Fully Distributed Scrum. Narinder Kumar

Transcription

1 Experiences of Fully Distributed Scrum Narinder Kumar

2 Linear Scalability of Production between San Francisco and India

3 Agenda Overview of Scrum Types of Scrum in Distributed Development Project Context Challenges & Solutions Agile Toolkit for Java Developer Discussion

4

5 Scrum process

6 Scrum Terms Roles Artifacts Scrum Master Product backlog Product owner Sprint backlog Team Impediment list Meetings Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Burn-down chart

7 Plan Act - Study

8 Why Distributed Scrum? Reduced Costs Availability of Talent Scaling up/down with Knowledge Retention and without local layoffs We count this as successful only if quality and productivity match those locally

9 Agile and Distributed : Oil and Water? Good Hyperproductive Agile Teams are Co-located with Shared Ownership Shared Responsibility High Interaction

10 Typical Problems in Distribution Time-Zones Culture Language Different Standards No Shared Ownership Us - Them

11 Distributed Scrum Styles Isolated Scrums Distributed Scrum of Scrums Fully Distributed Scrums Jeff Sutherland

12 Isolated Scrums Works when you have local PO (Separate Project) May be doing Waterfall with an iterative development team Results in classic Integration problems and code ownership Still large degree of us / them Isolated Scrums

13 Scrum of Scrums Recommended by Scrum Alliance Recognizes the link Does not give us rich communication to close the gap Still accepts the problem of distance as Given!

14 Fully Distributed Scrum

15 Case Study : TBD.com Social Networking WebSite based out of SF, California Started Sep 2006, Live March 2007 April 2008 : Looking for an off-shore partner to increase development capacity Goal : Grow Member base and Create a niche in yet to be tapped market segment

16 Getting to Know Each Other software development done right

17 Technology Stack YUI Spring Web MVC JSP 2.0

18 Critical Success Factors Shared Resources Regular Communication Initial Co-location and Regular Travel Easy Access to Product Owner

19 Acknowledgement of Challenges

20 Kick-Off One week Co-location Product Owner and Scrum Master in India Knowledge Transfer and Set-Up Norming & Chartering Session Success Criterias Initial Distributed Team of 7 People

21 Norming & Chartering Session Common Code Base Common Backlog Shared Definition of Done Communication Modes

22 Success Criterias Productivity Knowledge Build-Up of India Team Quality General Team Dynamics 6 week pilot was initiated

23 Modified Scrum Sprint in Action Daily Scrum End of Day Status Updates Weekly Team Meetings

24 Modified Scrum Sprint in Action contd... Pre-Planning and Planning Meeting Sprint Review and Updates Retrospectives

25 Tools at Our help Skype Video/Audio Conference Adobe Acrobat Connect Pivotal Tracker Confluence, Jira, SVN, Staging Environment..

26 Results

27 One Team

28 Business Value Member Growth Monthly Visits Monthly Visits 80,000 50,000 April 40,000 June May July 30,000 August 20, , , , ,000 June May July June August July 150, , , ,000 50,000 50,000 10,000 August 00 - Time January Number of page views March Number of Visits 60,000 6,000,000 January January February February March March April April May 300, ,000 February 5,000,000 February March 4,000,000 April May 3,000,000 June July 2,000,000 August 1,000,000 0 Time Time Time Monthly Page View per visit Number of page views per visit Total Members 350, ,000 January 70,000 Monthly Page Views January February March April May June 8.00 July 6.00 August Time

29 Productivity & Quality Improvements Average Per Person Velocity 12 Story Points Iterations

30 Project Review in India by Mary & Tom Poppendieck

31 Collaboration Summary 8 Months Distributed project Team Extension in India 24/7 support by development team Because of Fully Distributed Scrum TBD.com got maximum benefits of off-shoring

32 Success Factors Same level of Talent on both sides Rich Experience in Agile Transparency on Business Drivers by TBD.com Evaluation System sets clear expectations

33 Difficulties Faced Limited Travel possible Distributed Demos Distributed Design Some work still remains local

34 Guiding Principles One Team Shared Goal and Ownership Shared Agile Value System

35 Agile Toolkit for Java Developer

36 Build Tools Easy Build Continuos Integration Maven / Ant (max 10 minutes) Bamboo / Cruise Control / Hudson Automated Quality Statistics Code Coverage (Clover / Cobertura) Code Quality (JDepend, PMD, CheckStyle)

37 Test Tools Unit Testing Frameworks JUnit DBUnit Mocking Frameworks HttpUnit Integration Testing Frameworks Fitnesse Selenium

38 ? Narinder Kumar Linear Scalability of Production between San Francisco and India

39 References Articles and Presentations on Distributed Scrum with No time overlap Articles and Presentations on Distributed Scrum with Time-Overlap General Articles about Java EE Technology and Agile Methodologies