Communication Between Tribes: A Story of Silos, DevOps and Government
summary
Early GDS work builds GOV.UK and runs the site with automated provisioning and more than a thousand releases, proving continuous delivery works at government scale. A huge spreadsheet-based configuration management project fails; automated CM and live state tracking replace it. Policy and assurance get thinned into executable checks: high-level smoke tests tagged to map to SLAs so only tagged failures page people, turning arguing over words into tests-as-code. Examples cite GPG13 interpretations, GCHQ authorship, Puppet and BDD-security for implementation.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:16GDS Government Digital Service
- 4:28Agile, lean, scrum, containers, iteration, stack, hypervisor, nosal, serverless, cloud, velocity...
- 5:01Incident, event, problem, COBIT, configuration management, capacity management, CAB...
- 7:00Language differences reinforce organisational silos
- 10:38Words often carry the weight of past experiences and other organisations
- 13:48But practices like automation, developers on-call, configuration management, continuous deployment, and automated testing were second nature
- 16:53Overlapping words from different tribes are often a great place to start collaborating
- 21:21Subverting stereotypes as a way to build relationships
- 26:58Don't let scarcity of expertise lead to unapproachable stereotypes
- 27:45Code as a Communication Medium Bridging policy and practice
- 28:07The dreaded incident severity conversation
- 28:50Everyone thinks everything is critical
- 33:23What I Don't Know How to Do Devops Enterprise Ask
related talks
52mShepherding Government Towards Effective Delivery
32mContinuous Delivery Sounds Great But It Won’t Work Here
11mWorking with sharp tools - A case study of Continuous deployment
21mScaled Agile DevOps
30mOur Continuous Delivery Journey
38mSIG Release Deep Dive
29mOne DevOps does not git all
11mTDD - Trust Driven Development