Discussion about this post

User's avatar
EleoNora Nelson-Per-Claeson's avatar

Thought-provoking article. I agree with the challenge to equate Scrum, Lean, flow and agility as though they are automatically the same thing. Many organisations have become more focused on Sprint commitments, velocity, planning cycles and ceremony compliance than on improving flow, reducing delays and delivering meaningful outcomes. In that respect, the critique of how Scrum is commonly practised is fair. Flow matters. Smaller batches matter. Reducing WIP matters. Too many implementations have become bureaucratic and framework-centric rather than value-centric.🧭

That said, I remain curious whether the issue is the Sprint itself or how it is applied. The argument appears to move from "many Sprint implementations are problematic" to "Sprints are bad", which feels like a significant leap. A Sprint is, at its core, a cadence. In practice, cadence and flow are not necessarily opposites. Portfolio reviews, quarterly planning, strategy reviews and Big Room Planning are all forms of cadence. Healthy systems often benefit from both flow and cadence. The question is one of balance, not polarity. 🔍

I was also intrigued by the statement that "No piece of software has ever been produced by a team." In most modern product organisations, value delivery depends on far more than code creation. Architecture, customer insight, product management, UX, security, DevOps, testing, compliance and countless collaborative interactions all contribute to the outcome. A developer may write the code, but value is created through a socio-technical system of people working together towards a shared purpose. Reducing software development to coding alone risks overlooking the human and collaborative dimensions that make successful products possible.🌱

Regarding TOSD, much of what is described feels familiar from Lean Flow, Kanban, pull systems, continuous delivery, single-piece flow, throughput optimisation and WIP reduction. The genuinely interesting elements appear to be the OK Point, the focus on item-level timeboxing and the removal of Sprint constructs and traditional role structures. Whether this represents a genuinely new paradigm or a thoughtful evolution and repackaging of existing Lean principles remains to be seen, but it is certainly an interesting challenge to established thinking. Interested to see how TOSD evolves and where it demonstrates advantages beyond existing Lean and flow-based approaches.🤔

As a framework-agnostic practitioner, the question that always comes to mind is: what problem are we trying to solve? In some contexts, Scrum works. In others Kanban works. In others, flow-based systems are more appropriate. Sometimes a hybrid approach is the most effective answer. The real danger, in my experience, is dogma. I've seen organisations hide behind Scrum, Kanban, SAFe and Lean alike. The framework is rarely the problem. More often, it is the underlying system, behaviours and assumptions that deserve closer examination.🦋💃🏿

@Rnest's avatar

Pensándolo de una manera amplia, tener "equipos de desarrolladores" es equivalente a crear equipos de "vendedores" o de "torneros".

Lo que no es lo mismo que crear "equipos de desarrollo", que tienden a ser multidisciplinarios. Eso abre un poco más la idea del ciclo de vida completo o el "End 2 End" como se le suele llamar, contenido en el equipo completo.

TOSD va un poco más allá: donde no necesites equipos, no los crees. Hacerlo puede burocratizar de manera muy penosa la creación de valor y la entrega en tiempo.

19 more comments...

Ready for more?