Experience Of Fully Distributed Scrum With No Time Overlap
39
Experiences of Fully Distributed Scrum Narinder Kumar www.xebiaindia.com
-
Upload
xebia-it-architects -
Category
Technology
-
view
2.080 -
download
2
description
This is one of the second presentation that was given by Narinder Kumar @IndicThreads Conference in Pune.
Transcript of Experience Of Fully Distributed Scrum With No Time Overlap
Experiences of Fully Distributed Scrum
Narinder Kumar
www.xebiaindia.com
Linear Scalability of Production between San Francisco and India
Agenda
➢ Overview of Scrum➢ Types of Scrum in Distributed Development➢ Project Context➢ Challenges & Solutions➢ Agile Toolkit for Java Developer➢ Discussion
Scrum process
Scrum Terms
RolesScrum Master
Product owner
Team
ArtifactsProduct backlog
Sprint backlog
Impediment list
Burn-down chartMeetingsSprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Plan – Act - Study
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
Agile and Distributed : Oil and Water ?
➢ Good Hyperproductive Agile Teams are ➢ Co-located
with➢ Shared Ownership➢ Shared Responsibility➢ High Interaction
Typical Problems in Distribution ➢ Time-Zones➢ Culture➢ Language➢ Different Standards➢ No Shared Ownership➢ Us - Them
Distributed Scrum Styles
Isolated Scrums
Distributed Scrum of Scrums
Fully Distributed ScrumsFully Distributed Scrums
© Jeff Sutherland 1993-2007
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
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 !
Fully Distributed Scrum
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
Getting to Know Each Other
software development done right
Technology Stack
YUI
Spring Web MVC
JSP 2.0
Critical Success Factors
➢ Shared Resources
➢ Regular Communication
➢ Initial Co-location and Regular Travel
➢ Easy Access to Product Owner
Acknowledgement of Challenges
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
Norming & Chartering Session
➢ Common Code Base
➢ Common Backlog
➢ Shared Definition of Done
➢ Communication Modes
Success Criterias
➢ Productivity
➢ Knowledge Build-Up of India Team
➢ Quality
➢ General Team Dynamics
6 week pilot was initiated
Modified Scrum Sprint in Action
➢ Daily Scrum
➢ End of Day Status Updates
➢ Weekly Team Meetings
Modified Scrum Sprint in Action contd...
➢ Pre-Planning and Planning Meeting
➢ Sprint Review and Updates
➢ Retrospectives
Tools at Our help
➢ Skype Video/Audio Conference
➢ Adobe Acrobat Connect
➢ Pivotal Tracker
➢ Confluence, Jira, SVN, Staging Environment..
Results
One Team
Business Value
-
10,000
20,000
30,000
40,000
50,000
60,000
70,000
80,000
Member Growth
JanuaryFebruaryMarchAprilMayJuneJulyAugust
Time
Tota
l Mem
bers
0
50,000
1,00,000
1,50,000
2,00,000
2,50,000
3,00,000
3,50,000
Monthly Visits
JanuaryFebruaryMarchAprilMayJuneJulyAugust
TimeN
umbe
r of V
isits
0
50,000
100,000
150,000
200,000
250,000
300,000
350,000
Monthly Visits
January
February
March
April
May
June
July
August
TimeN
umbe
r of V
isits
0
10,00,000
20,00,000
30,00,000
40,00,000
50,00,000
60,00,000
Monthly Page Views
JanuaryFebruaryMarchAprilMayJuneJulyAugust
Time
Num
ber o
f pag
e vi
ews
0.002.00
4.006.008.00
10.00
12.0014.00
16.0018.0020.00
Monthly Page View per visit
JanuaryFebruaryMarchAprilMayJuneJulyAugust
Time
Num
ber o
f pag
e vi
ews
per v
isit
Productivity & Quality Improvements
0
2
4
6
8
10
12
Average Per Person Velocity
Iterations
Sto
ry P
oint
s
Project Review in India by Mary & Tom Poppendieck
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
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
Difficulties Faced
➢ Limited Travel possible
➢ Distributed Demos
➢ Distributed Design
➢ Some work still remains local
Guiding Principles
➢ One Team
➢ Shared Goal and Ownership
➢ Shared Agile Value System
Agile Toolkit for Java Developer
Build Tools
➢ Easy Build➢ Maven / Ant (max 10 minutes)
➢ Continuos Integration➢ Bamboo / Cruise Control / Hudson
➢ Automated Quality Statistics➢ Code Coverage (Clover / Cobertura)➢ Code Quality (JDepend, PMD, CheckStyle)
Test Tools
➢ Unit Testing Frameworks➢ JUnit➢ DBUnit➢ Mocking Frameworks➢ HttpUnit
➢ Integration Testing Frameworks➢ Fitnesse➢ Selenium
ReferencesArticles and Presentations on Distributed Scrum with No time overlap
➢ http://www.agile2009.org//node/1528
➢ http://blog.xebia.com/2009/08/26/fully-distributed-scrum-agile2009/
➢ http://www.infoq.com/presentations/fully-distributed-scrum
➢ http://www.computer.org/portal/web/csdl/doi/10.1109/AGILE.2009.27
Articles and Presentations on Distributed Scrum with Time-Overlap
➢ http://submissions.agile2008.org/node/1442
➢ http://blog.xebia.com/2008/08/21/agile2008-fully-distributed-scrum/
➢ http://www.infoq.com/articles/dutch-railway-scrum
General Articles about Java EE Technology and Agile Methodologies
➢ http://xebee.xebia.in
➢ http://blog.xebia.com
➢
