Blog

Large-Scale Scrum (LeSS) is often filed under "scaling frameworks," but that label undersells it — LeSS is really a de-scaling framework built around simplification, queueing theory, and a genuine whole-product focus. It keeps the essentials of Scrum but modifies events like sprint planning and backlog refinement for multi-team reality, adds an overall retrospective to unlock organizational improvement, and has officially aligned itself with the 2017 Scrum Guide rather than 2020. Whether or not you adopt it, the underlying ideas are worth knowing.

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.

Spoiled for choice when it comes to scaling beyond two Scrum teams? This piece is a long-form opinion walk through the major patterns — SAFe, Scrum@Scale, LeSS, Pulse, Nexus, Spotify copy-paste, Kanban, Flow, Disciplined Agile, Prince II Agile, WaterScrumFall, Scrum of Scrums, and even the option of no pattern at all — with honest pros and cons drawn from real experience. The first rule of scaling is not to scale. Get the best people and let them crack on. If you must grow, grow rather than scale. As one mentor put it, "something inferior done well in the right spirit is usually better than something superior done badly." Plus a reflection on which patterns truly hold a single product backlog (only Nexus and LeSS), why most frameworks are Shu patterns to get you started, and a teaser for "Broad and Deep agility" — combining Nexus+ for breadth with LeSS or Scrum Studio for depth, instead of choosing between broad-and-shallow or deep-and-narrow.