Agile, Lean and IT

www.agilemindstorm.com@ruckiand

From 35 to 600+www.adform.com

# of IT people: 2 -> 23

+6 business offerings

# of developers: 25 -> 280

20+ deployments per day

1 mln. reqs per second <100 ms

1 PB of data

2000+ servers

Agile and Scrum

Build process that works

Deliver early and adjust

Find your pace

Lean and KanbanManage value delivery flow

Manage queues and bottlenecks

Eliminate waste in your flow

How we organised ourselves?

Creative Chaos

#1

#2

Scrum in da House

ITPM DEV

Scrum team

…

Scrum team

CS

Sales

Push

Challenges popped upas # of people increased

Micro changes vs Batches

IT scope enormous, but 5 people

Increased # of dependencies

Automation vs Manual

#1Deployment

ITDEV

Scrum team

…

Scrum team

1 release manager Release dayRollbacks Exceptions

Measure Hot fixes

Rollbacks fail

Lack of knowledge

Complex

Manual work

ITDEV

Scrum team

…

Scrum team

Deployment platform: custom

No rollbacks

Measure product quality, not exceptions

Delegate

#224/7 monitoring

ITDEV

Scrum team

…

Scrum team

OnDuty Setting up KPIs

Reaction Exceptions

Need to involve devs

but feature not workingServer up

Micro changes are too fast

ITDEV

…

Metrics platform:

zabbix graphite grafana bosun

Scrum team

Scrum team

Teams are responsible for their SLAs

3d party 24/7

#3Access to prod

ITDEV

Scrum team

…

Scrum team

ConfigurationTroubleshooting

Queues of developers

Distraction

long resolution time

Manual work

ITDEV

Scrum team

…

Scrum team

Access platform:

sit.adform.com

Access to prod givenPersonalised accounts

Configuration automation

Config platform:

puppet

#4Procurement

ITDEV

Scrum team

Scrum team

Batching: office and prodCosts optimisation

CTO

HW

#1

#2

#3

#4

deliver

#5

#4.1

Negotiation during purchase

#1.1

Custom HW

IT

DeV

CTO

#1

deliver

ALL

#1.1 stock contracts

configs: S, M, L, XL, XXL

#2

Officestock

contracts deliver

On demand

EvolutionLean

Adapt to business needs

Permanent changeAgile

Growth

Competition

Pull

PMDevCSOps

PMDevCS Ops

Product development

ServicesFront teams

Team A

Team Z

Srv1

Srv2

Srv3… …

Srv4

…

What has changed for IT?

StructureCulture

and not only

Services

DevOps

DC

Virt

Security

2. Service catalogue

Structure1. Split into areas with

dedicated people

PMDevCSOps

3. Ops in teams

Services

CultureClients

Ext. provider

do it yourself

#1

#2

#3

potential service

#4

ImportantI think following is very

for any service unit

Imagine you have to earn money

shifts your thinking away from “cost center”

Avoid broad terms

Devops

IT

SecurityVirtualisation

Core

Say “No“

Control scopeBe explicit about

what you can do

Monitoring and Transparency

Best way to control

De-centralizeBuild for scale

Grow you processevolution vs adoption

Know value flowLocal efficiency is not what you need

www.agilemindstorm.com

@ruckiand

Credits to my team for bringing these ideas to life

Questions ?www.adform.com