30
Scrum at BT Geoff Watts Roger Leaton

Scrum at BT - · PDF fileEnd to End Product Delivery Management Team Product Line 2 No end to end owner! Operation al process Product Line 1 Product Line 3 OSS Developers

  • Upload
    vuthuy

  • View
    214

  • Download
    0

Embed Size (px)

Citation preview

Scrum at BT

Geoff Watts Roger Leaton

About •  Global provider of network-centric solutions, services & products

•  (2006/07) 40% of revenues from “new-wave revenues”

•  6m Broadband users

•  Company Stats:

–  100,000 staff globally (25,000 outside UK)

–  20 million ( Residential & Business Customers)

–  Annual Turnover ~ £20 Billion (2007)

–  £2.3 Billion NHS contract (2004)

•  IT Organisation – BT Design

–  8000 People

–  4000 on customer facing IT

–  6000 subcontract staff in India

How it was before?

Efficiency & Adaptability

Business does not want “technical success”

Why Agile?

“It is not the strongest of the species that survives, nor the most intelligent,

it is the one most adaptable to change”

- Charles Darwin

Challenges at BT

“Of all the places to try agile, why would anyone

choose [BT]”

-  JP Rangaswami BT Global Services CIO

Crossing the Chasm

Crossing the Chasm, Geoffrey A. Moore, 2002.

Conservatives

Sceptics

Pragmatists

Early Adopters

Visionaries

Need Coaches

The Coaching Team

Education

Community

BT Agile Awards

Prove it

As a customer I want to know when my Service is ready to use asap So I can maximise my ROI

Agile Planning

Release planning •  Backlog

•  Prioritise •  Estimate (points) •  Acceptance criteria

•  Validation •  Iteration plan(s)

Planning is continuous

Iteration planning •  Iteration plan

•  Learn •  Prioritise •  Estimate (points)

•  Tasks and Tests •  Re-plan

Vision

Product Backlog

Vision Product Backlog

Scrum Team Scrum Team Scrum Team

Sprint Backlog Sprint Backlog Sprint Backlog

Product Line 2

No end to end owner!

Operational process

Product Line 1

Product Line 3

OSS Developers

Network rollout

Product delivery

managers

External Network Vendors

15000+ Sub-

contract developers

primarily offshore

OSS Design Network rollout

SOA Architects

BT Design

21C - The Starting Point

Classic sub-optimised Waterfall organisational structure

BT Operate

BT Wholesale

BT Retail

BT Openreach

Kick-Off

•  Initial event for management team –  Essential to get buy-in for top-down

support

–  Lean Analysis workshop

–  External consultants

•  Major Team Event –  Large scale Agile simulation

–  Focus on end to end delivery

•  Product and team selection for initial target

End to End Product Delivery Management Team

Product Line 2

No end to end owner!

Operational process

Product Line 1

Product Line 3

OSS Developers

Network rollout

Product delivery

managers

External Network Vendors

15000+ Sub-

contract developers

primarily offshore

OSS Design Network rollout

SOA Architects

BT Design

Classic sub-optimised Waterfall organisational structure

BT Operate

BT Wholesale

BT Retail

BT Openreach

The New “Team”

Planning

•  Dumped 8 month Milestone plan •  Prioritised backlog of stories, 2 week

iterations and 8 week release cycles •  Focus on 1 real customer working •  Delivered in 4 customers in 8 weeks •  Speed exposed the targets for follow-up

transformation activities

Aug

Sept

Nov

Oct

Mar

Jan

May

Apr

Dec

Feb

Follow-up

•  Heavy coaching activity –  Extending approach to other teams – Based on business priority products –  Extending learning

•  Operating continuous improvement initiative –  Fixing core issues raised bottom up

Component User Stories Code/Unit test System Test Integration Test

Component User Stories Code/Unit test System Test Integration Test

Component User Stories Code/Unit test System Test Integration Test

Typical BT Value Stream

Effectiveness = 48.35/467 = 10.3%

2 days

Design Review

1 day

5 days

342 days

Component User Stories

5 days

15 days

359 days

2 days

Code/Unit Test

15 days

15 days

376 days

2 days

System Test

2 days

10 days

387 days

1 days

Integration Test

2 days

15 days

402 days

0 days

UAT

5 days

10 days

457 days

Wait for release every 90 days

0 days

45 days

447 days

45 days

Deploy

48.35 days

467 days

10 days

Initial concept

Value

Time

Cumulative Time

Release review (90 days) Hothouse

1 day

3 days

285 days

Initial Sift

0.1 days

1 day

62 days

30 days

Business Case

10 days

30 days

102 days

10 days

High Level Solution Design

5 days

30 days

325 days

6 days

Detailed User Stories

2 days

2 days

289 days

2 days

HL Stories

0.25 days

1 day

1 day

1 day

Queue for go

0 days

180 days

282 days

180 days

Component User Stories Code/Unit test System Test Integration Test

Component User Stories Code/Unit test System Test Integration Test

Component User Stories Code/Unit test System Test Integration Test

Effectiveness = 48.35/467 = 10.3%

2 days

Design Review

1 day

5 days

342 days

Component User Stories

5 days

15 days

359 days

2 days

Code/Unit Test

15 days

15 days

376 days

2 days

System Test

2 days

10 days

387 days

1 days

Integration Test

2 days

15 days

402 days

0 days

UAT

5 days

10 days

457 days

Wait for release every 90 days

0 days

45 days

447 days

45 days

Deploy

48.35 days

467 days

10 days

Initial concept

Value

Time

Cumulative Time

Release review (90 days) Hothouse

1 day

3 days

285 days

Initial Sift

0.1 days

1 day

62 days

30 days

Business Case

10 days

30 days

102 days

10 days

High Level Solution Design

5 days

30 days

325 days

6 days

Detailed User Stories

2 days

2 days

289 days

2 days

HL Stories

0.25 days

1 day

1 day

1 day

Queue for go

0 days

180 days

282 days

180 days

Agile Value Stream

Initial concept HL Stories Product Level

Planning

Release Level

Planning

Iteration Level

Planning Build & Test Deploy

Value

Time

Cumulative Time

0.5 days

1 days

25 days

0.25 days

1 day

1 days

1 days

2 day

12 days

0.5 days

2 days

24 days

25 days

25 days

50 days

Wait for team

0 days

10 days

22 days

27.25 days

50 days

1 days 10 days 180 days

Effectiveness = 27.25/50 = 54.5%

Automated Testing

•  Not for legacy? •  It’s too big and complex to think

about

•  But we have distributed teams •  Slow across the network? •  Dev is separate from SYS/INT

What next?

     “Success is not final, failure is not fatal: it is the courage to continue that counts.”

- Winston Churchill

Customers & Suppliers

Brendan Kennedy 10th May 2007

Round Tables

Agile Heartbeat

•  establish a vision

•  change always happens

•  so prioritise your activity

•  do something small

•  get feedback

•  decide next steps

We are committed to contributing positively to society and to a sustainable future. This is part of the heart of BT.

Contact

•  Questions •  Further Information •  Training

•  Consultancy •  Coaching

Please contact [email protected] +44 7717 111199