Agile, Project, SAFe: It Doesn't Matter

The three layers

Direction. Someone decides what matters. Call it strategy, product vision, OKRs, a program. Doesn't matter. At this level, the questions are: why are we doing this, what do we want to achieve, and what are we willing to postpone so something else comes first?

Planning. Someone translates that direction into a plan. Initiatives get broken into features or deliverables. Teams are assigned. Dependencies are mapped. And here's where most organizations go wrong: this isn't a one-time exercise. Every time something changes (a priority shifts, a team gets stuck, an estimate turns out to be wrong) the plan needs to be recalculated. Not next quarter. Immediately. The plan is a living thing, not a document.

Execution. Teams do the work. From features they create tasks, work in sprints or iterations or whatever cadence fits, and report progress. That progress feeds back into the plan, and the plan feeds back into strategic direction. A roadmap that doesn't move with reality isn't a roadmap. It's a wish list.

Every methodology is just a different configuration

And here's where it gets interesting: every methodology is simply a different configuration of these three levels.

The point: these are not fundamentally different ways of working. They are the same three layers with different amounts of structure per layer.

Terminology is a translation exercise

And when you see it this way, terminology stops being a barrier and becomes a translation exercise. Projects have regular status updates. Call them iterations… that sounds suspiciously like sprints. A project plan connects to strategic program goals and has phases. Call them initiatives and you're suddenly speaking the same language as an agile organization. Different words. Same structure underneath.

This also explains why projects, agile, and everything in between coexist in most organizations, and why they misunderstand each other so badly. They're not doing something fundamentally different. The labels make it feel that way.

Complicated vs complex

There's a useful perspective from the Cynefin framework. Most work falls into one of two categories: complicated or complex.

Complicated work can be hard, but you know exactly where you want to end up. You can plan the path. Complex work can also be hard, but you don't know exactly where you'll end up. You have to discover the path as you go. Most people intuitively sense which way of working fits best. And the match is logical: complicated work leans toward project-based planning, complex work toward agile discovery. Both exist in every organization at the same time.

The three-layer model doesn't care which type of work you do. It connects them. Direction sets the priorities, regardless of whether the underlying work is complicated or complex. Planning translates those priorities into executable plans, whether teams run sprints or execute project phases. Execution feeds reality back up. The layers stay the same. Only the ceremony per layer adapts.

Most organizations break at the seams between these levels. Strategy says one thing, the plan says another, and teams do something else entirely.

Fix the connections, and the label you put on your process becomes almost irrelevant.