Are Agile Coaches living in a time warp?

Debbie Levitt makes solid arguments about how the Lean Startup is irrelevant or maybe never relevant was in several contexts in this excellent article. The Lean Startup is Outdated, Drop Everything That Comes from It). I found the perspective interesting and something to ponder on.

Scaled Agile Framework, or SAFe as its popularly referred to, is the leading scaling framework for agile enterprise adoption. It takes many concepts from the Lean Startup, several of which are core to its structure. Not just SAFe, many frameworks and flavours of agile also leverage these ideas in some shape and form.

I tend to agree, at least partially with Debbie. Many of these ideas that SAFe adopts and, in general, agile coaches promote from the Lean Startup have merit but often are not appropriate or fit the context in a real-world enterprise. The struggle is real.

Build Measure Learn

By Antonsk — Own work, CC BY-SA 4.0,

The fundamental assumption in the build-measure-learn is that we iterate with our build cycles trying to learn. That has merit. However, what if our core idea is flawed and we are not building the right initial features? Focusing on releasing features to the market and discovering what customers think might be good from a startup perspective, but from a large enterprise that often addresses an existing customer base, is it worth the risk? Are we leveraging on the experience and knowledge we already have of the customer or just rushing wildly into “building” like a feature factory?

Having said that build-measure-learn conceptually remains a decent idea for enterprises especially in the enterprises who spend months and sometimes years launching a new product only to discover that it was way off the mark. The challenge lies in the adoption of this practice and bringing it in context.

Minimum Viable Product

“The lesson of the MVP is that any additional work beyond what was required to start learning is waste, no matter how important it might have seemed at the time.” ― Eric Ries

As Ries advocates, the core principle about MVP is to ship the barest minimum functionality to the customer to get fast feedback. Building anything else is a waste. In large enterprises where SAFe is often practised, the scale and complexity of the product often make this MVP too big. A smaller version is often unusable or can rarely be shipped beyond a minimal audience. For enterprises, the customers are often already paying and not in the “acquiring customers” phase of a startup where things are free, and you can experiment far more easily. So while still useful, it is a concept that has found limited support. Also, the anti-pattern often observed with MVP is that teams use the same term to mean “First release”. This is where you start to see MVP-1, MVP-2 and so on. That defeats the whole purpose of using the concept of MVP.

There are few thought processes already that go beyond the MVP and make this concept more real to the enterprise world. MBI is one.

As defined on the PMI website,

Once we dig deeper and understand the nuances, I find the concept of MBI as advocated by Disciplined Agile far more relevant and useful in large enterprises. For a good comparison between MVP and MBI, and to understand them better, refer below — Minimum Business Increments (MBIs)


Pivot is advice, as Debbie says, “could be good but rarely taken”. How often have we seen pivoting in real life and especially in enterprises? It would take a lot of leadership mettle and supportive organisational culture to “safely” pivot for large initiatives. That does happen too, but often the way is to stop talking less about the failed project and launch a brand new one with revised branding. People eventually forget about the failed one, and that’s not precisely pivoting.

This misfit of ideas is true not just for the few ideas from the Lean Startup but for many others. Story points is one such actively promoted concept, often with lot of passion by several agile coaches. It is a great concept, but its inventor has already refuted that (Story Points Revisited ( It is useful but not in all contexts and its implementation is horrible in most enterprises.

Actually, we can challenge a lot in the agile manifesto too, but that would need a blog of its own. Some folks have already done some work in that area — Agile 2. I would not say I subscribe to each and everything they claim, but it’s a good start.

The Emperor has no clothes.

A lot of failed attempts to use these concepts or struggles are getting brushed under the “agile hype” around, where everyone wants to say they are successful at agile. The most common excuse being — Oh ! They don’t have an agile mindset ! or They are not yet ready to be agile ! Often the “emperor has no clothes” but no one dares call that ugly reality.

While agile and agility are still relevant and timely, the practices and ideas that have driven it so far need upheaval. In 2022, we cannot run with the same tools we used in 2000 or 2010. Agile itself needs to evolve with the times, and so does its practices, especially when it is becoming the new normal in large enterprises.

The Wrap

*** Did you like this? Feel free to bang that clap button. Do you want more? Follow me on Medium | LinkedIn | Twitter , or read more here. ***



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store