Scaling agility across the Enterprise.Focus on visibility, consistency and keeping track of the bigger picture

David Weir – Head of Development

Presentation Summary

• Quick overview• Why we needed to become Agile• Scrum Boards – Common Pitfalls• Scrum Boards – Quick Wins• Practical walkthrough• Increase visibility across the Enterprise/

Multiple Programmes• Q & A

Experts in enabling smarter decisions, by converting clients own DATA into INFORMATION

Introducing Callcredit

• More than 1000 employees in ten locations, headquarters in Leeds

• Vertically split into 3 sectors:- Credit, Marketing and Consumer.

• Serving leading companies in Financial Services, Telecoms, Retail, Utilities and Insurance

Our Agile Adoption

• Since 2000 (inception) Callcredit has grown both organically and through acquisition ( over 8 sub companies acquired in 12 years)

• Adopted a complete new restructure in 2010 to provide total operational capability (HR, IT, Legal, Facilities) as one to the wider group.

• In parallel to the TOM, we adopted a standard Agile delivery approach:- DSDM

• DSDM• More business friendly terms• Prioritised set of requirements (M60%, S20%, C20%, W0%)• Delivers to a fixed time, dropping scope (S&C) if necessary

Scrum Boards / White Boards

• Provides a focal point for the project team• Assists the velocity• Are we working on the right things• What’s blocked• What is committed / time left

• Ensures important steps are not missed

• Provides visibility……provided that we stick to a few simple rules.

No Scrum board is the same

Examples of some of our white boards

Quick Win 1: Project Info

• Name of the Project or Product• Timebox Start Date• Timebox End Date• Optional • RAG• Current Stage• Due Date

Backlog

Derived from Timebox Planning

Q13

Where a priority is decided then this shows

the next story to move to development

In Progress

A story currently in development

Q13

Where a number of stories are completed and awaiting QA they can be

prioritised here

In QA

A story currently in QA

Done

Completed stories ready for timebox

releaseStory Section

Task Section

Quick Win 2: Consistent Sectors

Quick Win 3: Colour Coding

STORY

A

As a business ambassador I want to be able to ............ So that

TASK

A.1

Write query to allow ............. To be retrieved

A

A.1 BLOCKER

QA Resource Unavailable

Blocker

Issue

Issue

Test Database Corrupted

Project Whiteboard

Backlog Q13

In Progress Q13

In QA Done

A

D

B

G

C

E

F

A.1 A.3 A.2 A.4A.5

D.2D.1 D.3

B.1 B.2 B.3

E.4E.1 E.2 E.3

E.6

F.1 F.2

G.5G.4G.1 G.2 G.3

I B

Quick Win 4: Consistent Progression

Practical Walkthrough - Scenario

• There is a development conference in Southampton (UK) scheduled for 4th May 2013. We have won the exclusive catering contract for this event.• We must transport 2 Tonnes of bananas from

Rio (Brazil) to the Event• We must arrive via France in order to pay the

minimal European import tax

Practical Walkthrough – NFR’s

• The transport must arrive before May 2013• Bananas will only last 6 weeks unrefrigerated• Southampton port is not used to international

trade therefore we must upgrade its navigational aids.

• 2 Projects. Build a Boat, and Build a Lighthouse

The Boat Design

The lighthouse Design 1

The lighthouse Design 2

The lighthouse Design 3

The Plan

The Boat: Halfway checkpoint

The Lighthouse: Halfway Checkpoint

The Boat: Complete (Ahead of Schedule)

The lighthouse: Complete J.I.T

Conclusion

Post Implementation Review

• Boat twice as fast as expected• The light house was delayed• The boat was finished and released early• The daylight savings hours (march) wasn't considered• ......Lots of other reasons etc.

Generally • Each project acted exactly as it should have done to satisfy it’s own

requirements.• Each project approached the delivery using many of the tried and tested agile

techniques (incl. Running their whiteboards/scrum boards as demonstrated – this doesn't guarantee success)

• Doing right by their own project but by the programme/Enterprise • No overarching ownership

FUNDAMENTALLY – Each project was not concerned or visible to one another despite their joint goals– NO ONE WAS LOOKING

Scrum of Scrums

• 9:45am daily ‘huddle’ which contains all PM’s and other stakeholders to discuss issues/status of the day.• Reports on the major issues, concerns,

changes and state of every project in a programme• Contains key individuals who can un-block

major issues (Dev/QA/DBA/Infrastructure)

Our Scrum of Scrums Board

Project Cards

• Project Name• Release Name • PM Initials• Release Date• RAG Status• Any associated Issues

or Blockers