Member-only story
How to Lead Engineering Teams Without Letting Chaos Win
Why a bit of process policing can be a very good thing.
Agile is supposed to make us nimble, responsive, and relentlessly focused on delivering value. But somewhere along the line, we decided that “agile” meant “no rules”, or worse “all the rules”.
We threw away documentation, stopped planning, and declared meetings a relic of the waterfall era. The result? Teams move fast, but mostly in circles.
AI coding tools have supercharged this problem. Teams can now generate code, tests, and documentation at ten times the old pace which means the circles get bigger faster. Agility without discipline was always expensive. With AI in the loop, it’s ruinous.
Here’s the uncomfortable truth: agility without discipline isn’t agility. It’s chaos with a sprint board.
As engineering leaders, our challenge isn’t to eliminate process, it’s to make process useful. To police it just enough that it keeps people aligned, without turning into the Agile Inquisition.
Agile needs structure — just the right amount
A good agile process is like a well-drawn football pitch. The lines keep the game fair, focused, and fun but they don’t dictate how you play.
