Blog

Scrum equals Agile. Agile equals Scrum. It's one of the most common assumptions in the industry, and it's wrong — Scrum predates the Agile Manifesto, and Agile today is a whole family of methods, frameworks, and strategies of which Scrum is just one option among many.

Product owners, product managers, and product leaders aren't the same thing — but the overlap is real enough that teams constantly confuse them. The tension gets sharper when Scrum and product management meet, because Scrum doesn't recognize sub-roles within a team. Here's a practical way to map the responsibilities across all three, and where each one actually adds value.

Most learning programs fail for the same reason: they offer people hours they don't have. Four hours a week of development time sounds generous, but when the week already contains 44 hours of work crammed into 40, that time never arrives. Nine minutes at 9am — every day, protected, no meetings — is smaller, simpler, and far more likely to actually happen.

A mature product living on autopilot and a brand-new product searching for its first customer aren't just at different lifecycle stages — they live in entirely different complexity domains. Mapping Cynefin onto the product lifecycle reveals a pattern worth paying attention to: what works for one stage can be actively dangerous in another. And assuming you're in a simpler space than you actually are is one of the fastest routes into chaos.

You might assume the product owner writes acceptance criteria. They shouldn't — and when they do, a predictable dysfunction creeps in. Here's why the people doing the work should own what "done" looks like, and what the product owner should be doing instead.

A long queue for pizza at a rainy English festival turned into an unexpected lesson in flow. The team at the stall was deliberately slow at taking orders, perfectly coordinated through each step, and careful never to take on more work than their slowest stage could handle. That's a lesson most knowledge work teams haven't quite learned yet — and it's why so many of them feel constantly overloaded.

Developers finish their code early in the sprint, hand it off to testers, and start looking around for the next thing to do. If that sounds familiar, the question isn't really what developers should do with their spare time — it's why work is being handed off at all. Here's what collaboration looks like when a team is actually working toward Done together.

The first rule of scaling agile? Don't scale — get your best people in a room and figure out what actually needs doing. But when scaling is unavoidable, not all frameworks deserve equal respect. This opinionated walk through LeSS, Disciplined Agile, Scrum at Scale, SAFe, Nexus, Spotify/ING, and Flight Levels cuts through the noise to expose a common pathology: organizations growing product owners like flowers, each tending their own backlog while the highest-value work sits untouched. Three patterns earn praise, three get dismissed, and one framework is labeled a "piss in your pants" solution — find out which.

What does organizational agility actually mean — and who's responsible for it? Six months after writing a definition of agility designed to keep no one off the hook (not executives, not specialists, not teams), this piece argues something important is still missing: societal value. Most conversations about value stop at customers, end-users, and knowledge. But agility, the argument goes, also has to be about leaving the planet in a better place. Through the lens of a milk bottling company experimenting with recyclable glass, this article unpacks the different kinds of value teams can deliver, why sincerity from leaders matters more than slogans, and offers an updated September 2019 definition of agility — one that explicitly includes caring about planet earth, shared purpose beyond money, and the courage to make a stand.