Tweet
Tweet

Slide 1

Slide 1 text

Agile service delivery
 In the UK’s public sector Roo Reynolds @rooreynolds
 digi2al.co.uk

Slide 2

Slide 2 text

Hello

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

flickr.com/photos/rooreynolds/27131941631

Slide 5

Slide 5 text

flickr.com/photos/rooreynolds/17043911398

Slide 6

Slide 6 text

A brief history of the Government Digital Service (GDS)

Slide 7

Slide 7 text

gds.blog.gov.uk/tag/revolution-not-evolution

Slide 8

Slide 8 text

GDS was formed in November 2011

Slide 9

Slide 9 text

Leading the digital transformation of government Making services so good people prefer to use them

Slide 10

Slide 10 text

www.gov.uk

Slide 11

Slide 11 text

www.gov.uk

Slide 12

Slide 12 text

25 of the most important government services

Slide 13

Slide 13 text

flickr.com/photos/gdsteam/26736615492

Slide 14

Slide 14 text

A multi-disciplinary team - working with colleagues across government flickr.com/photos/paul_clarke/6477056845

Slide 15

Slide 15 text

Agile

Slide 16

Slide 16 text

7 steps to construct
 a building (I imagine) flickr.com/photos/lhanaphotography/6107639393

Slide 17

Slide 17 text

1. Gather the requirements 2. Agree a plan 3. Dig up some ground 4. Pour some concrete 5. Build the ground floor 6. Build some more floors 7. Put the roof on flickr.com/photos/lhanaphotography/6107639393

Slide 18

Slide 18 text

1. Gather the requirements 2. Agree a plan 3. Dig up some ground 4. Pour some concrete 5. Build the ground floor 6. Build some more floors 7. Put the roof on flickr.com/photos/lhanaphotography/6107639393 Disclaimer
 I am not a civil engineer

Slide 19

Slide 19 text

7 steps to build a digital service 
 (you’d think)

Slide 20

Slide 20 text

1. Gather the requirements 2. Agree a plan 3. Pick a supplier and set goals 4. Plan the project 5. Start implementation 6. Finish implementation 7. Handover and evaluation

Slide 21

Slide 21 text

7 steps to build a digital service
 (based on user needs)

Slide 22

Slide 22 text

1. Meet the users 2. Understand the users’ needs 3. Build a prototype 4. Get feedback from real users 5. Iterate, with constant feedback 6. Make it live 7. Continue to improve

Slide 23

Slide 23 text

www.gov.uk/service-manual

Slide 24

Slide 24 text

What if what you make doesn’t meet the needs of your users?

Slide 25

Slide 25 text

What if you missed some requirements?

Slide 26

Slide 26 text

What if things change during the process?

Slide 27

Slide 27 text

www.gov.uk/service-manual

Slide 28

Slide 28 text

flickr.com/photos/mtaphotos/8310696617

Slide 29

Slide 29 text

flickr.com/photos/compacflt/15725076691

Slide 30

Slide 30 text

Agile

Slide 31

Slide 31 text

twitter.com/psd/status/568324759521501184

Slide 32

Slide 32 text

www.gov.uk/service-manual

Slide 33

Slide 33 text

www.gov.uk/service-manual/governance

Slide 34

Slide 34 text

www.gov.uk/service-manual/digital-by-default

Slide 35

Slide 35 text

www.gov.uk/performance Service
 performance

Slide 36

Slide 36 text

github.com/alphagov A photo with some text next to it

Slide 37

Slide 37 text

Some tips

Slide 38

Slide 38 text

Start with
 user needs

Slide 39

Slide 39 text

flickr.com/photos/ndomer73/2582778532/

Slide 40

Slide 40 text

“When making bacon and eggs for breakfast, 
 the chicken is involved but the pig is committed” flickr.com/photos/ndomer73/2582778532/

Slide 41

Slide 41 text

Show the thing

Slide 42

Slide 42 text

Five is enough

Slide 43

Slide 43 text

nngroup.com/articles/why-you-only-need-to-test-with-5-users/

Slide 44

Slide 44 text

“Testing with one user is one hundred percent better than testing with none” Steve Krug @skrug

Slide 45

Slide 45 text

Walls are important

Slide 46

Slide 46 text

flickr.com/photos/rooreynolds/14203258760

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

gds.blog.gov.uk/2014/09/03/vertical-campfires-our-user-research-walls

Slide 51

Slide 51 text

gds.blog.gov.uk/2014/09/03/vertical-campfires-our-user-research-walls “A well-tended wall keeps research insights and user needs constant in the collective ‘mind’ of the project team.” Kate Towsey

Slide 52

Slide 52 text

Milk matters

Slide 53

Slide 53 text

abscond.org/2014/09/25/culture-stories-milk.html

Slide 54

Slide 54 text

abscond.org/2014/09/25/culture-stories-milk.html “Left unchecked in a semi-isolated environment, cultures can get very odd” James Darling

Slide 55

Slide 55 text

instagram.com/p/BCfNLIAlYu_

Slide 56

Slide 56 text

abscond.org/2014/09/25/culture-stories-milk.html “Free to anyone. Contributions welcome.”

Slide 57

Slide 57 text

alicebartlett.co.uk/blog/tampon-club

Slide 58

Slide 58 text

alicebartlett.co.uk/blog/tampon-club-v2

Slide 59

Slide 59 text

www.tampon.club

Slide 60

Slide 60 text

Thank you Roo Reynolds @rooreynolds
 digi2al.co.uk rooreynolds.com/2016/05/25/agile-in-the-public-sector