Why I’ve Stopped Obsessing Over Agile
Over the years, I’ve watched Agile go from a transformative idea to something that often feels hollow.
Not because the core principles are flawed — but because the way Agile is often implemented misses the point entirely.
I’ve sat through the overhyped workshops.
I’ve seen the templated playbooks.
I’ve witnessed rigid rituals dressed up as innovation.
And each time, I find myself asking:
Are we actually working better — or just adding more process for the sake of process?
Let’s be clear: Agile didn’t fail because the concept is broken.
It failed in many places because it became more about checking boxes than driving outcomes.
When someone says “we need to be more agile,” what that often translates to is:
- Adding another ceremony
- Spinning up another dashboard
- Running another retro
- Tracking velocity as if it’s an indicator of real progress
All in the name of “continuous improvement” — but with little real change to show for it.
In many organizations, Agile has become more about form than function.
It’s turned into a belief system, where questioning the process is seen as missing the point.
But real builders know better.
They don’t worship the process — they focus on outcomes.
What I Actually Care About
What matters to me is delivering real value — quickly.
Not how many story points we move in a sprint.
I care about teams who:
- Think critically
- Challenge assumptions
- Solve problems
Not teams who follow processes blindly because it’s what the guidebook says.
I care about staying close to the customer — deeply understanding their needs and being ready to adjust when those needs evolve.
Not obsessing over stale backlogs and tickets that no longer reflect reality.
I care about clarity — knowing the purpose behind the work.
Not hiding behind rituals to mask a lack of direction.
And most of all, I care about trust — giving people the responsibility and space to do great work, and the accountability to do it well.
Not managing through rigid status meetings or process checklists.
If you use Scrum, Kanban, SAFe, or something homegrown — great.
Use what works.
But don’t mistake the framework for the result.
When teams are moving fast, solving meaningful problems, and creating real impact — it’s rarely because they followed a perfect Agile ritual.
It’s because they’re sharp, focused, and empowered to get the job done.
Forget Agile (Sort Of)
Be adaptive
- Change shouldn’t require a sprint planning meeting.
- Good teams adjust in real time, listen to feedback, and move with purpose.
Be intentional
- Do work that matters.
- Know why it’s being done.
- Trade process for purpose and busywork for meaningful progress.
Be useful
- Deliver something that improves someone’s day.
- Solve actual problems.
- Build products and services your customers care about — and your team is proud of.
Because at the end of the day, nobody is asking how Agile you are.
They’re asking:
- Did you solve the problem?
- Did you make it better?
- Did you move the needle?
That’s what actually works.