Delivery Management
How we manage delivery in the age of agents. From human PR review to autonomous delivery pipeline.
Maturity →
You don't have to figure this out alone.
Every level in this matrix has a path. Read the playbooks the teams that have climbed it wrote. Run the assessment with our consultants. Start where you are.
Book an AI Maturity Assessment session with your team.
We walk you through all four perspectives, score where you actually are, and leave you with a 90-day plan to climb in the dimensions that matter most.
If the factory has an operating manual, delivery is where you find out whether anyone is reading it.
Two numbers from August frame the whole perspective. The first is Zalando's: 33% of pull requests auto-approved by a risk classifier trained on their own incident history, with a 20-40% reduction in lead time - a genuine result from a genuine platform. The second is LinearB's, across 8.1M PRs: agentic PRs merge at 79% in elite organisations and 37% in the rest, and the variable that separates them is not tooling. It is ownership. An agent-opened PR with no named human owner does not get rejected; it just quietly never merges. Throughput is a queueing problem long before it is a model problem.
The bill arrived too, and it is itemised in three places. A study of 3.52M changes in one enterprise C++ codebase found AI-generated code carries higher coupling and copy overhead that shows up as a 5-8% increase in production compute consumption - the first credible number putting AI code on the cloud bill rather than the maintainability ledger. Meta's internal telemetry, reported by Reuters, shows changes to internal platforms up 220% and features up 36%, against major incidents up 40% and time firefighting them up 70%. And McKinsey's survey of 1,719 leaders has EBIT impact statistically flat year over year at 37% any, 6% significant. The productivity is real; so is the counterweight, and any metrics program that reports only the first half is not measuring, it is marketing. Track incidents-per-merged-change next to throughput or do not bother.
Governance is where August moved fastest, and mostly in one direction: away from scanning and toward provenance. Rust adopted an explicit LLM policy - analyse, review, refine, but do not create - Oracle barred AI-generated code from OpenJDK, Debian voted, SourceHut changed its terms. The Linux kernel's 7.2 cycle carried 1,111 `Assisted-by` commits, and at least one maintainer strips the tags on the way in, which tells you everything about disclosure that is not enforced in CI. One factual correction worth carrying: the EU AI Act milestone that actually bit on 2 August 2026 was Article 50 transparency, not the high-risk regime. The Digital Omnibus deferred that to December 2027 and August 2028. Plan the conformance work, but do not let anyone sell you a panic about a deadline that moved.