DevOps in a Windows (Enterprise) World
summary
The United Kingdom Hydrographic Office adopts CI/CD, moves from centralized to GitHub/DVCS, and cuts VM provisioning from two–three weeks to minutes by automating Hyper‑V/SCVMM with shared PowerShell modules and consolidating pipelines on Azure DevOps. Change management shifts to a “guide, trust and verify” model that removes approval gates while remaining auditable. Organization has ~850 staff with ~200 in digital/change; outcomes include faster time‑to‑market, more experiments, and measurable data‑driven decisions.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:02United Kingdom Hydrographic Office
- 7:29Cultural Challenges
- 10:43How Did We Address This?
- 13:45Outcomes
- 15:55Process Challenges
- 20:19Tooling Challenges
related talks
44mDevOps at Microsoft: Our Internal Transformation Story
05mDevOps over time
39mPutting the Ops in DevOps
07mWhat we learned moving 65,000 Microsofties to DevOps...
34mDevOps: Next
01h 01m"Doing Devops" as a politically powerless developer
36mDevOps: Improving applications with DevOps
15mDevOps - Future of IT
