Top Banner
Beyond the two-week iteration: an experience report Simon Hildrew The Guardian @sihil
54

Beyond the two week iteration - an experience report

Jul 03, 2015

Download

Technology

sihil

Slides from my talk at Agile Turkey 2014 talking about how the journey of the Guardian's development teams over the last few years.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Beyond the two week iteration - an experience report

Beyond the two-week iteration:an experience report

Simon Hildrew

The Guardian @sihil

Page 2: Beyond the two week iteration - an experience report
Page 3: Beyond the two week iteration - an experience report

Founded in 1821

Page 4: Beyond the two week iteration - an experience report

Website growth

1999 1m

March 2014 100m

wwwmonthly uniques

Page 5: Beyond the two week iteration - an experience report
Page 6: Beyond the two week iteration - an experience report
Page 7: Beyond the two week iteration - an experience report
Page 8: Beyond the two week iteration - an experience report
Page 9: Beyond the two week iteration - an experience report
Page 10: Beyond the two week iteration - an experience report
Page 11: Beyond the two week iteration - an experience report
Page 12: Beyond the two week iteration - an experience report
Page 13: Beyond the two week iteration - an experience report

“Its core purpose is to secure the financial and editorial independence of

the Guardian in perpetuity.”

Page 14: Beyond the two week iteration - an experience report

2010 2014

‘Products’ 1 ~15

Services / Deployables 4 ~120

Department size 40 160

Page 15: Beyond the two week iteration - an experience report

99 problems

Page 16: Beyond the two week iteration - an experience report

25 releases a year

Page 17: Beyond the two week iteration - an experience report

Stakeholder anxiety

Page 18: Beyond the two week iteration - an experience report

Release TrifleBrooke Raymond: https://www.flickr.com/photos/brooke/2364980971

Page 19: Beyond the two week iteration - an experience report

Inflexibility

Page 20: Beyond the two week iteration - an experience report

Determining value

Page 21: Beyond the two week iteration - an experience report

Traditional Agile has limits

Joe Lewis: https://www.flickr.com/photos/sanbeiji/220644819

Page 22: Beyond the two week iteration - an experience report

99 problems;Agile ain’t one

Page 23: Beyond the two week iteration - an experience report

Oliv

er W

ihle

r: ht

tps:/

/ww

w.fl

ickr.c

om/p

hoto

s/ol

iver1

/307

0609

090

Page 24: Beyond the two week iteration - an experience report

People and Process

Page 25: Beyond the two week iteration - an experience report

Agile Command & Control

Pam Falcioni: https://www.flickr.com/photos/ducatisti/3445071198

Page 26: Beyond the two week iteration - an experience report

Developer Autonomy

Jeff Mayer: https://www.flickr.com/photos/soundman1024/5813948758

Page 27: Beyond the two week iteration - an experience report

HANDBOOK FOR NEW EMPLOYEES

A fearless adventure in knowing what to do when no one’s there

telling you what to do

FIRST EDITION

2012

========================================================

Page 28: Beyond the two week iteration - an experience report

HANDBOOK FOR NEW EMPLOYEES

A fearless adventure in knowing what to do when no one’s there

telling you what to do

FIRST EDITION

2012

========================================================

Page 29: Beyond the two week iteration - an experience report

step 1. Unplug cords from wallstep 2. Move your deskstep 3. Plug cords back into wallstep 4. Get back to work

Fig. 2-2 Method to move your desk

1.

3.

2.

4.

VA LV E METHOD DIAG. 1

Page 30: Beyond the two week iteration - an experience report

Fred George’s Programmer Anarchy

Copyright © 2011 by Forward Internet Group, Ltd

PROGRAMMER

31

ANARCHY

Page 31: Beyond the two week iteration - an experience report

“Developer Migration”

Page 32: Beyond the two week iteration - an experience report

• Continually updated list of engineer requirements• Anyone can ask to move• Feedback on unsuccessful requests

Page 33: Beyond the two week iteration - an experience report

Technical Enablers

Page 34: Beyond the two week iteration - an experience report

Continuous Delivery

Page 35: Beyond the two week iteration - an experience report

Riff-Raff

Page 36: Beyond the two week iteration - an experience report

Change in attitudesallison: https://www.flickr.com/photos/look_ma_im_flying_pictures/2222370392

Page 37: Beyond the two week iteration - an experience report

Decouple deploymentfrom feature releases

Page 38: Beyond the two week iteration - an experience report
Page 39: Beyond the two week iteration - an experience report
Page 40: Beyond the two week iteration - an experience report
Page 41: Beyond the two week iteration - an experience report
Page 42: Beyond the two week iteration - an experience report
Page 43: Beyond the two week iteration - an experience report

Fix small things; fast

Page 44: Beyond the two week iteration - an experience report
Page 45: Beyond the two week iteration - an experience report

Who knows…?

Page 46: Beyond the two week iteration - an experience report

Guessing & arguing easier than measuring

http://www.flickr.com/photos/nouqraz/200049988

Page 47: Beyond the two week iteration - an experience report

Metrics

Page 48: Beyond the two week iteration - an experience report

change deployedchange deployed

Page 49: Beyond the two week iteration - an experience report
Page 50: Beyond the two week iteration - an experience report

Hypothesis testing

Page 51: Beyond the two week iteration - an experience report

Audience Segmentation

Page 52: Beyond the two week iteration - an experience report

Dev QA Ops

Gatekeeper

Watchman/OverseerConsultant

Manual regression tester

Test automationFeature testing

Product developer

Product developer, operations & support

Page 53: Beyond the two week iteration - an experience report

→ Continuous improvement → Confidence → Feature releases → De facto change → Everyone responsible

Two weeksAnxious stakeholdersTrifle releasesInflexible sprintsSole/unclear ‘value’ owner

Page 54: Beyond the two week iteration - an experience report

Thanks!

Simon Hildrew

@[email protected]

http://github.com/guardian