1 of 34

An Insider’s View Of Agile

In The Public Sector

@ntcoding

2 of 34

@ntcoding

3 of 34

x 1.3 Million

Photo credit: Ralphy Daly, https://www.flickr.com/photos/92269745@N00/4612732045

(annual tuition fees)

@ntcoding

4 of 34

x 50 000

Photo credit: By Graham Richardson from Plymouth, England - South Western Ambulance VX09FYP, CC BY 2.0, https://commons.wikimedia.org/w/index.php?curid=13250417

@ntcoding

5 of 34

x 250 000

Photo credit: https://www.flickr.com/photos/usdagov/16762770039

(annual salaries)

@ntcoding

6 of 34

x 250

© Copyright R Greenhalgh and licensed for reuse under the Creative Commons Licence 2.0

@ntcoding

7 of 34

x 200 000

Photo credit: peter russell [CC BY-SA 2.0 (http://creativecommons.org/licenses/by-sa/2.0)], via Wikimedia Commons

@ntcoding

8 of 34

x 650

Photo credit: Martin J Galloway, CC BY-SA 2.5 (http://creativecommons.org/licenses/by-sa/2.5)] via Wikipedia

@ntcoding

9 of 34

@ntcoding

10 of 34

“I'm so glad we extended the sprints to 3 weeks long. We get 1 week of solid development work now”

@ntcoding

11 of 34

“Programmers are a liability. The industry is moving towards generic rules engines & BPM tools [so we don’t need programmers]”

@ntcoding

12 of 34

“The Oracle web server we will use for this project is probably older than you”

@ntcoding

13 of 34

“Stand up is at 11[am]. And actually we sit down. It only lasts for about an hour, though.”

@ntcoding

14 of 34

“As a Message Bus�I want an API that I can call�So that…..”

@ntcoding

15 of 34

We

Users

@ntcoding

16 of 34

@ntcoding

17 of 34

https://www.gov.uk/service-manual/phases

@ntcoding

18 of 34

Digital Service Standard - User Needs

  1. Understand user needs
  2. Do ongoing user research
  3. Make sure users succeed first time
  4. Make the experience consistent with GOV.UK
  5. Encourage everyone to use the digital service

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

@ntcoding

19 of 34

Digital Service Standard - Agile

  • Have a multidisciplinary team
  • Use agile methods
  • Iterate and improve frequently

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

@ntcoding

20 of 34

Digital Service Standard - Tech

  • Evaluate tools and systems
  • Test the end-to-end service

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

@ntcoding

21 of 34

Digital Service Standard - Open

  • Make all new source code open
  • Use open standards and common platforms

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

@ntcoding

22 of 34

https://www.github.com/hmrc

@ntcoding

23 of 34

@ntcoding

24 of 34

Pass alpha assessment

You can spend money on a beta

Pass beta assessment

Live on gov.uk (with beta banner)

Pass live assessment

Live on gov.uk (no beta banner)

https://www.gov.uk/service-manual/service-assessments/how-service-assessments-work

@ntcoding

25 of 34

“You can’t be half agile”

- Mike Bracken, Ex Head of GDS

https://gds.blog.gov.uk/author/mike-bracken/

@ntcoding

26 of 34

Digital

IT

Agile

Citizens

Not Agile

@ntcoding

27 of 34

“You can’t be half agile”

- Mike Bracken, Ex Head of GDS

https://gds.blog.gov.uk/author/mike-bracken/

@ntcoding

28 of 34

Agile

Citizens

@ntcoding

29 of 34

Problems I’ve Seen in Gov IT

  • Separate digital and IT silos
  • GDS not assessing full system
  • Lack of long-term culture building
  • Not embracing assessments

@ntcoding

30 of 34

Fixing the Problems

  • All agencies must be more open
  • Agile leaders in gov agencies
  • Assess end-to-end system
  • GDS should be embedded

@ntcoding

31 of 34

HMRC Digital deploys to production multiple times per day, and has a platform running over 300 microservices.”

https://www.infoq.com/news/2016/08/devops-gov-hmrc

@ntcoding

32 of 34

Government IT Needs More People Like You

@ntcoding

33 of 34

So, have GDS made any difference?

@ntcoding

34 of 34

Let’s keep in touch

@ntcoding

blog.ntcoding.com

ntcoding

@ntcoding