Service Overview
Landing zones, self service portal, infrastructure as code, CI/CD, API strategy, a shared responsibility model and the change programme that makes engineers use it: the blueprint covers what a governed automation platform needs before the first line of code is written. Automation fails on culture before it fails on code, so the operating model is part of the design, not an afterthought. It applies an operating model designed with Microsoft engineers for a global enterprise, which became part of the Azure Cloud Adoption Framework.
What's Included
- Platform reference architecture: control plane, landing zones, self services
- Target operating model for DevOps, SRE and central platform teams, with shared responsibilities
- Backlog for the first 90 days and a build or buy decision
- API and integration strategy across infrastructure services
- Change strategy, stakeholder map, communication and enablement plan
What you get
- A platform design your engineers can build
- An operating model in force with leads who own automation
- 60 percent less onboarding effort per environment as the design target
- A clear build or buy decision
Format
Design work with the platform and infrastructure leads: reference architecture, operating model, build or buy decision paper. Design only, no engineering delivery.
Who it is for
Head of Cloud, Head of Infrastructure, Head of Platform Engineering, CTO, COO