Practice map

The library is organised around the work a delivery team does, not around a checklist. The map below shows what each section answers, how the sections relate, and where to start depending on your role.

The library at a glance

Section	Answers	Core standards
Adoption & assessment	How do we know the organisation is ready, and how do we change it?	Adoption lifecycle · Organisational readiness · Organisational change · Maturity model · Gap assessment
Platform & infrastructure	How is the AWS estate provisioned and governed?	Terraform standard · Terraform state · Landing zone · Control Tower · Identity and SSO · Service control policies
Build & release	How does a change become a deployable artefact?	Source control · Repository and branching · Release workflows · Build and test · GitHub Actions
Deploy & run	How does the artefact reach production safely?	Deployment strategies · Containers and serverless · Elastic Beanstalk · Containerized workloads
Operate	How do we know it is healthy, and what do we do when it is not?	Monitoring · Distributed tracing · Workload health KPIs · Runbooks · Deployment readiness
Security	How is the environment protected and evidenced?	Security model · Security best practices · DevSecOps shift-left · Detection · Config compliance
Reliability	How does it survive failure, and how do we prove it?	Resilience planning · Backup and DR · RTO and RPO
Delivery & governance	How is the engagement scoped, controlled and closed?	Delivery model · Statement of work · Risk management · Change management · Handover
Templates	What do the working documents look like?	Discovery, planning, delivery and closure templates

How the practices connect

Assess        Adoption & assessment
              └── readiness → maturity → gap → change plan

Provision     Platform & infrastructure
              └── accounts → identity → network → guardrails → IaC

Build         Build & release
              └── source control → review → build → test → artefact

Deploy        Deploy & run
              └── strategy → runtime → progressive release → rollback

Operate       Operate
              └── telemetry → KPIs → alert → runbook → review

Secure        Security
              └── design → shift-left gates → detection → response

Assure        Reliability
              └── RTO/RPO → backup → restore drill → failover test

Govern        Delivery & governance
              └── scope → plan → risk → change → acceptance → handover

The arrows are not strictly sequential. Security and reliability are designed alongside platform and deployment work, not after it; the governance practices run across the whole lifecycle.

Where to start

If you are	Start with	Then
A sponsor or executive	How we work	Adoption lifecycle, Delivery model
A platform or cloud engineer	Terraform standard	Landing zone, Configuration management, Service control policies
An application engineer	Source control	Repository and branching, Release workflows, Container pipelines
An SRE or operations lead	Monitoring	Workload health KPIs, Runbooks, Deployment readiness
A security lead	Security model	Security best practices, Detection, Config compliance
A project or delivery manager	Delivery model	Statement of work, Risk management, Change management
New to the library	How we work	Glossary, then the section relevant to your role

Well-Architected alignment

Pillar	Where it is addressed
Operational excellence	Release workflows, Deployment readiness, Runbooks, Change management
Security	Security model, Security best practices, Detection, Config compliance
Reliability	Resilience planning, Backup and DR, RTO and RPO
Performance efficiency	Monitoring metrics, Deployment strategies
Cost optimisation	Cost visibility, Containers and serverless
Sustainability	Right-sizing throughout monitoring metrics and cost visibility

Reading a standard

Every page follows the same shape, so standards can be compared and applied consistently:

Part	What it contains
The standard	The requirement the practice must meet, stated plainly
Approach	How Qbits implements it — tools, patterns and the reasoning behind them
In practice	Configuration, code or procedure a delivery team can follow directly
Evidence	What is produced to show the standard was applied