Skip to content

Blog

Agentic adoption is harder than agile, because you can't fake it

Agile rollouts could rename roles and keep the waterfall. Agentic engineering returns nothing on half-measures, because every gate sits upstream in architecture, context and the team.

Written by

Adoption

Published: 18 June 2026 Updated: 2 min read

Talking with Bjoern Rochel last week. He used to lead engineering at a large network company. Now he’s deep in agentic adoption at a German enterprise.

He said something that hasn’t left me: “This is the agile transformation squared. At least a league harder.”

I get why people push back on that framing. Most agile rollouts didn’t go great. So saying agentic is harder than agile lands as either bragging or doom posting. But I think he’s right, and the reason isn’t what people expect.

You could fake agile

With agile, you could fake it. Rename the Project Manager to Product Owner, hire an Agile Coach, ship the same waterfall in two-week wrappers. Half the rollouts I saw in 2010 were exactly that. The numbers stayed flat. Everyone moved on.

Agentic doesn’t let you do that. Half-measures return zero.

Every gate is upstream

That’s the structural difference. Agile had downstream shortcuts. You could optimize the ceremony, leave the architecture, leave the team boundaries, leave the org chart, and still call it done.

Agentic doesn’t have downstream. Every gate is upstream:

  • architecture principles
  • ADR practice
  • context engineering
  • the harness around the tool
  • the hiring filter
  • the team that knows what to build before the agent writes it

The capability bar moves up

Bjoern put it sharper: “You have to turn average developers into director-of-technology people.” Not literally. But that’s the capability gap. The minimum bar for an effective agentic developer is closer to today’s senior architect than today’s mid-level engineer.

And the existing process layer doesn’t help, it actively gets in the way. Sprint cycles, approval gates, coordination overhead. The frameworks that made delivery legible at scale in 2015 are friction in 2026.

There’s another piece. Technology changes faster than the org can standardise it. By the time you have a company-wide standard, the standard is already obsolete.

The work is foundation work

So the move isn’t another framework. It’s foundation work. Slow, expensive, hard to fake.

The companies pulling ahead are doing that work. The ones still negotiating which AI license to roll out are buying the Product-Owner-rename version of this shift.

What does the foundation work look like in your org right now?

Further reading

  1. Agentic coaching is the new agile coaching Adopting agentic engineering has the same shape as adopting agile twenty years ago: an organizational change, resistance among senior people, and the same three levers that worked the first time. 2 min readShort post
  2. Most AI rollouts change the codebase and leave the team untouched In a Multitudes survey, codebase changes made up 85% of what teams changed for AI, and only 13% named a process change. In our experience, that gap is why most rollouts hit the same wall. 1 min readShort post
  3. Agency, not the tool, decides whether AI works for a team Skill on one axis, agency on the other: four quadrants with four very different outcomes. Give senior developers agency and the tool starts working. Strip it away and even the best reject it. 2 min readShort post

All 13 posts on Adoption

ClientsCase study: Tegtmeier Internet Solutions

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check