I spent a years watching teams fail at Agile before writing APEX

I have watched highly competent people spend most of their week in meetings designed to manage the appearance of progress rather than create it.

That is a precise description. I'm not talking about bad teams. I'm talking about good engineers, smart product people, experienced leaders all working inside a process that consumes the energy it was supposed to organize.

The sprint ends. The retrospective happens. Someone writes action items. The next sprint begins with the same problems and a longer backlog.

I started writing APEX because I needed a name for what I kept watching happen, and I needed a framework that didn't pretend the problem was fixable with better standups.

The specific thing that broke for me

What finally made me write it down was watching a team spend three days preparing for a sprint planning meeting. Three days. The meeting itself was two hours. They were planning two weeks of work.

Nobody in that room thought it was normal. But nobody said anything, because the process demanded it and the process had been in place for years and the process was Agile and Agile is supposed to work.

It does not always work.

Agile was a genuine breakthrough when it replaced waterfall rigidity in the 1990s. But the methodology has calcified into its own form of rigidity: ceremony rigidity. The two-week sprint exists whether the work fits in two weeks or not. The standup happens whether anything useful can be said in 15 minutes or not. Velocity is tracked whether it measures progress or not.

The AI era made this worse, not better

Here is the thing nobody is saying: the AI era should have made this problem smaller. A skilled engineer working with AI can today produce what required a team two or three years ago. The leverage available to small, expert teams is unprecedented.

But most teams are using AI tools inside the same process overhead as before. They're producing more output faster and managing that output in the same Jira-standup-sprint-review cycle. The AI compressed the delivery, not the ceremony.

APEX is an attempt to build a methodology around the leverage that actually exists now, not around the coordination overhead that made sense before it existed.

What APEX is, in one sentence

Small, accountable teams with precise problem understanding, expert judgment, and relentless focus on delivery, with AI amplifying all of it.

That is four principles: Accountable, Precise, Expert-led, eXpedient. It is also a system, guides, templates, a repo structure, a way of tracking progress that does not require a separate tool.

The manifesto is at github.com/evuori/apex-manifesto. It is free. It is in a public repo. I am not selling a course or a certification. There are no fancy colored belts available either.

I am saying: the current approach is broken for a lot of teams, here is a more honest one, use it if it resonates. The full manifesto, guides, and templates are available on GitHub: github.com/evuori/apex-manifesto