Blog

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.

"How do we balance UX with shipping fast in Scrum?" is the wrong question. The real goal isn't to ship faster — it's to discover faster, because a large chunk of the ideas in your backlog probably shouldn't be built at all. Here's how Scrum and UX actually fit together, from striped vs. blended backlogs to the Lean UX Canvas, and why the combination closes the fundamental gap that Lean Startup left open.

Scrum already helps teams deal with complexity — so what does adding Kanban bring to the mix? This piece looks at how Scrum with Kanban tightens the empirical loop, sharpens focus, and helps teams navigate complexity more easily through one definition of workflow, four practices, and four measures. From visualizing aged work, blockers, and unacknowledged dependencies, to using throughput and Monte Carlo probabilistic forecasting in Sprint Planning and Sprint Review, to managing expectations early enough to course correct — this is about more than visual boards. It's about avoiding execution bias, dodging groupthink, and not falling into the "build it and they will come" trap. Because in complex environments, simply talking to the customer beats a fantasy of what we think they want. Plus a reminder that value today isn't just about customers and the organization — it's also about sustainability, risk reduction, and learning.

The 2020 Scrum Guide brought some important shifts — and 18 of them stand out. This piece runs through what's new and what changed: from customers and end-users finally getting explicit mentions, to "Developers" replacing the Development Team (long live one team), to experimentation getting an explicit nod. The Sprint Goal and Definition of Done both found proper homes as commitments. The Scrum Master is no longer called a "servant leader" but is now on the hook for the effectiveness of the Scrum Team. Product Owners get a new Product Goal as their commitment to the Product Backlog. Self-managing teams replace self-organizing ones (in the Hackman sense), Sprint Planning now has three topics instead of two, and Scrum Teams cap at 10 members. Plus a few subtler shifts — the word "consistency" makes an appearance, stakeholders get mentioned twice as often, and feedback gives way to collaboration on what to do next. Overall verdict: a solid update.

The 2020 Scrum Guide elevated "commitment" beyond the artifacts themselves, attaching the Product Goal, Sprint Goal, and Definition of Done to give teams clearer focus and transparency. This post unpacks what each commitment really means, how they differ in "hardness," and why — when navigating complexity — striving toward a direction of travel matters more than guaranteeing an outcome.