ATMEN Framework · Agentic Delivery
Intent, verification and integration now decide how fast — and how safely — you ship. The IVI method fixes those three, one measured step at a time.
Agentic delivery is how software gets delivered when AI agents write much of the code. Writing code got cheap, so work now stalls at intent, verification and integration. The IVI method (Intent → Verification → Integration) gives each of those an owner and a metric.
For two decades, agile has helped teams make the most of one scarce resource: the hours it takes people to write code. Sprints, story points and velocity charts are all ways of planning around that constraint.
AI agents changed the equation. Writing code got cheap — but the constraint didn't disappear. It moved. Today, work stalls in three new places:
Before the agent starts: The intent is too vague to build from, so the output misses the point and comes back as rework.
After it finishes: Nobody can say with confidence that the output is correct, so it piles up in review.
On the way to production: Integration is too fragile to ship often, so finished work waits for a release window.
ATMEN keeps what made agile work — small slices, fast feedback, working software — and rebuilds the operating model around the new bottleneck.
IVI is its agentic delivery module: principles and metrics, not ceremonies.
The IVI method · Intent → Verification → Integration
01 · Intent
02 · Verification
03 · Integration
The roadmap
More often than not, the constraint turns out to be review — not coding.
Baseline with PulseCheck →Run as a measured experiment, with go/no-go criteria agreed before it starts.
The step most organisations underestimate: writing agent-ready intent is a new skill, and it has to be trained.
In regulated DACH organisations, this is what auditors — and budget holders — ask about first.
The honest part
Agentic delivery is young, and long-term evidence is still thin — for everyone. So I don't sell a guaranteed transformation. The pilot runs as an experiment: before it starts, we agree the go/no-go criteria together — rework rate, escaped defects, review lead time and your DORA metrics. You scale only what the numbers support.
IVI isn't a new framework to adopt. It's the discipline behind these results — dual-track discovery, test-first development, CI/CD and measurable compliance — re-aimed at a world where agents write the code.
5×
Release cycle reduction
ZEISS AG
−95%
Critical defects
Manufacturing enterprise
80%+
Process compliance within 3 months, up from under 30%
Healthcare enterprise
IVI stands for Intent → Verification → Integration. It's the agentic delivery module of the ATMEN framework: three stages, each with an owner and a metric.
The pilot runs in months 2–3, after a four-week Diagnose: one team, one value stream, with go/no-go criteria agreed before it starts. The roadmap from diagnosis to governance takes about six months.
Rework rate for intent; escaped defects and review lead time for verification; DORA metrics (deployment frequency, change failure rate, time to recover) for integration.
In 30 minutes we'll locate your bottleneck — intent, verification or integration — and decide together whether a Diagnose is worth it. No pitch, no pressure.
Last updated: November 2026