+ All Categories
Home > Technology > Adp scrum multiple product logs

Adp scrum multiple product logs

Date post: 11-Nov-2014
Category:
Upload: akkirajub
View: 3,042 times
Download: 0 times
Share this document with a friend
Description:
 
Popular Tags:
17
Scrum - Maintenance Projects - Multiple Product Backlogs Akkiraju Bhattiprolu (Akki) [email protected] http://www.after3beers.com / Facebook : akkirajub Twitter : akkirajub Linkedin : akkiraju +91 98665 51263 Akkiraju Bhattiprolu (Akki) Senior Manager ADP Private Ltd. Hyderabad akkiraju_bhattiprolu@adp .com http://www.adp.com/ +91 (40) 66378073
Transcript
Page 1: Adp scrum multiple product logs

Scrum - Maintenance Projects - Multiple Product Backlogs

Akkiraju Bhattiprolu (Akki)[email protected] http://www.after3beers.com/Facebook : akkirajub Twitter : akkirajubLinkedin : akkiraju+91 98665 51263

Akkiraju Bhattiprolu (Akki)Senior Manager ADP Private Ltd. [email protected]://www.adp.com/ +91 (40) 66378073

Page 2: Adp scrum multiple product logs

2

Agenda

About ADP Maintenance Traditional Working Model Extended Team In India Agile In ADP India Multiple Product Back Logs Results

Page 3: Adp scrum multiple product logs

3

About ADP

World’s leading provider of Outsourced HR and Auto Dealership Services

Brief Profile Established in 1949 and Headquartered in NJ Revenues of about $9 billion Operates in more than 50 Countries with 46,000 Associates 90% of revenue is recurring with an average client tenure of

over 9 years Electronically moved over $1 trillion in client tax, direct deposit,

and related client funds in fiscal 2008 Pay 30% of the employees of medium-sized businesses in the U.S.

ADP India Fully Owned Subsidiary of ADP Inc. Established in July 1999 with 102 Associates Currently 3900+ and growing Involved in R&D, BPO and RIM Offices in Hyderabad and Pune Works on an Extended Team Model

Page 4: Adp scrum multiple product logs

4

ADP India R&D

India R&D Head

Prod1 Dev TeamRoseland NJ

15Yrs in MarketMainframe

Team Size 100

Prod2 Test TeamPleasanton CA5Yrs In Market

.NetTeam Size 50

Prod3 Dev TeamAlpharetta GATo Be Release

J2EETeam Size 25

Prod4 Dev & Test Team

Canada1 Yr

Web 2.0Team Size 10

…….???

Prod ‘n’ Team<Function ??><Location??><Maturity??>

<Technology?><Team Size ??>

Page 5: Adp scrum multiple product logs

5

Maintenance

New Feature

New RegulationIntegrations

A Hosted A

DP App

Non Functional (Scalability etc)

Multiple Sub Projects Projects Vary Significantly In Size, Complexity & Priority Multiple Releases Business Prioritizes And Development Delivers

Production / Support Incidents

Defects

Page 6: Adp scrum multiple product logs

6

Traditional Working Model

Collocated Specialists By Modules Captive Ownerships Releases Plans Module By Module

Module 1 Expert

Module 2 Expert

Module 3 Expert

Module ‘n’ Expert

Page 7: Adp scrum multiple product logs

7

Extended Team In India

India TeamModule 1 Expert

Module 2 Expert

Module 3 Expert

Module ‘n’ Expert

Page 8: Adp scrum multiple product logs

8

Extended Team In India

New “Specialists” Created In India Many Sub Groups Capacity Planning Still Module By Module Varying Utilization Predominantly Waterfall At Both Ends More Challenges On India Side To “Click” As One Team

India TeamModule 1 Expert

Module 2 Expert

Module 3 Expert

Module ‘n’ Expert

Page 9: Adp scrum multiple product logs

9

Agile In ADP India

Agile Objectives Increase Capacity – More Utilization Reduce Individual Dependencies Reduce Onsite Dependencies Bring In The “Team” Spirit Bring Common Commitment

US Team India Team

Scrum Master

Product Owner

789101112

123456

13

Product Backlog

Page 10: Adp scrum multiple product logs

10

Agile In ADP India

India Team Gets Deliverables* R100 : New Requirement In Batch Process 8/25/10 R200 : Add New Feature In UI Screen 9/15/10 R300 : Develop New Report 9/23/10

Product Owner Breaks Deliverable Into Stories R100–8 Stories R200–5 Stories R300–13 Stories

2 Week Sprints Stories In Sprint From Any Deliverable PO Decides The Sequence Of The Stories Everyone Is Responsible For Every Deliverable Pair Programming

Normal Sprint Practices

India Team

Scrum Master

Product Owner

789101112

123456

13

Product Backlog

* Production/Support Incidents are a different beast

Page 11: Adp scrum multiple product logs

11

Agile In ADP India

7/26/2010 8/25/2010

8/1/2010 8/8/2010 8/15/2010 8/22/2010

7/26/2010 9/15/2010

8/1/2010 8/8/2010 8/15/2010 8/22/2010 8/29/2010 9/5/2010 9/12/2010

7/26/2010 9/23/2010

8/1/2010 8/8/2010 8/15/2010 8/22/2010 8/29/2010 9/5/2010 9/12/2010 9/19/2010

R100 Available Sprints 2

R200 Available Sprints 3

R300 Available Sprints 4

9/6/2010Sprint

9/6/2010Sprint

8/9/2010Sprint

9/20/2010Sprint

8/23/2010Sprint

8/9/2010Sprint

7/26/2010Sprint

7/26/2010Sprint

7/26/2010Sprint

8/23/2010Sprint

8/9/2010Sprint

Page 12: Adp scrum multiple product logs

12

Multiple Product Backlogs

Scrum Master

Product Owner

789101112

1234

56

13

PB R1008/25/10

789101112

1234

56

13

789101112

1234

56

13

PB R2009/15/10

PB R3009/23/10

Textbook SCRUM One Product Backlog One Release Plan One Priority Adaptive Plan Is Easy To Manage

Our Context Multiple Backlogs Each Deliverable Is Different

Size – Number Of Stories Release Date Priority

Have To Make Parallel Progress Customized SCRUM – Agility!

How Can We Plan?

Page 13: Adp scrum multiple product logs

13

Deliverable R100

Story Story Points

Story 101 2

Story 102 4

Story 103 4

Story 104 8

Story 105 4

Story 106 8

Story 107 1

Story 108 4

Total Size 35

Date 8/25/2010

Available Sprints 2

Team Velocity 28

Doable ? YES

Multiple Product Backlogs

India Team

Scrum Master

Product Owner

789101112

123456

13

Product Backlog

R100 “Deliverable Velocity” : 18 SP

Page 14: Adp scrum multiple product logs

14

Deliverable R100

StoryStory Points

Story 101 2

Story 102 4

Story 103 4

Story 104 8

Story 105 4

Story 106 8

Story 107 1

Story 108 4

Total Size 35

Date 8/25/2010

Available Sprints 2

Team Velocity 28

Deliverable R200

StoryStory Points

Story 201 2

Story 202 4

Story 203 8

Story 204 2

Story 205 4

Total Size 20

Date 9/15/10

Available Sprints 3

Team Velocity 28

Deliverable R300

StoryStory Points

Story 301 1

Story 302 2

Story 303 8

Story 304 4

.. ..

…. …

Story 313 2

Total Size 53

Date 9/23/10

Available Sprints 4

Team Velocity 28

Can We Deliver All?

Multiple Product Backlogs

R100 Deliverable Velocity : 18 SP R200 Deliverable Velocity : 7 SP R300 Deliverable Velocity : 14 SP

Page 15: Adp scrum multiple product logs

15

DeliverableSize SP

Release Date

Available Sprints

Deliverable Velocity

R100 35 8/25/2010 3 18

R200 20 9/15/2010 2 7

R300 53 11/05/2010 4 14

Total 108     39

Team Velocity (SP) 28

What Are Average SP To Be Developed For Each Deliverable? What Are The Total Average SP To Be Developed Per Sprint ? (39) What Is Team Velocity? (28) In Control If Velocity Is Less Than Average Deliverable Velocity

Deliverable Velocity : The average SPs that need to be delivered in each available sprint before its release date

Multiple Product Backlogs

Page 16: Adp scrum multiple product logs

16

Results

On Average Team Utilization Has Moved Up From 60% To 90% Every Module Has More Than One Specialist Team Level Ownership. Everyone Responsible For Success Of

Every Deliverable or Otherwise. Team Confidence On Rise To Stake Claim For Bigger Projects

US Team India Team

Scrum Master

Product Owner

789101112

123456

13

Product Backlog

Page 17: Adp scrum multiple product logs

17

Bouquets

And

Brickbats


Recommended