Those concepts are usually mixed everywhere. It seems both are based on Lean, but that's all. The core of the Lean Startup aproach seems to be to develop the MVP (minimum viable product). Whereas the core of the Lean software development seems to be to eliminate waste.

Could we say that?

  • Lean software development are principles
  • Lean Startup is a methodology which aplies those principles
  • Kanban is a method to apply either those principles or that methodology

2 Answers 2


I would suggest that Lean software development as discussed at length by Mary Poppendieck and Tom Poppendieck is a methodology closely related to the Agile family of software development methodologies such as Extreme Programming and Scrum, each with its own design emphasis, rituals and community. However, at the heart of all Lean/Agile culture is the core belief that rapid feedback cycles - where feedback is meant to be in the form of ‘live’ reactions (such as sales or usage spikes) from the ‘real environment’ (from clients, prospects and users most importantly) – are required to discover the important but false assumptions often hidden in planning or requirements documents. So you can think of the ecosystem of Lean/Agile practices as vehicles for enabling fast feedback cycles - ‘fail fast to succeed sooner’ – in order to expose and manage the risk associated with false assumptions about the development environment.

Lean Startup simply applies the idea of using rapid feedback cycles to expose false assumptions to the customer development and business side of the organization. Steve Blank coined the term and created the processes around ‘Customer Development’ which Eric Reis built upon to develop ‘Learn Startup’.

Kanban is a tool, like you mentioned, that can be used in any project management style, even Waterfall.

  • Thank you. You are right, but I keep researching and I found two articles which explain it easier (I think). So I also have written my own answer. What do you think?
    – chelder
    Apr 30, 2014 at 17:31
  • 1
    I think the articles you referenced do a good job explaining the ideas, but I have noticed sometimes that people focus on the practices and may not understand they 'why' behind them. In fact, understanding the 'why' behind the MVP, for example, can help us design the most effective one possible. We may not need a graphic designer for the landing page. We may not even need a landing page. We do the least possible to accomplish the learning required to make informed decisions.
    – wgajate
    Apr 30, 2014 at 18:17
  • Totally agree. Actually, that is what I want to clarify with those articles. If we read the first results of Google, people (like me) think (wrongly) that MVP is a minimun software implementation. You clarify it even more with this comment. Thanks! :)
    – chelder
    May 1, 2014 at 12:59

I think the following couple of articles are perfect to understand the difference easily.

From oxzigen.com - lean software development:

It’s easy to confuse the Lean IT and Lean Startup methodologies. (...) I sometimes use the analogy of a restaurant to describe these different roles. According to this analogy, the Lean Startup activities are taking place mostly in the “dining room” where there is direct contact with the customers. (...) Lean IT activities, on the other hand, are taking place mostly in the “kitchen.” Their goal is to deliver a high-quality product quickly and efficiently.

From w2lessons.com - minimum viable product dissected:

One of the fundamental and most misunderstood tenants of the lean startup is the minimum viable product (MVP). (...) For starters you must look at the MVP not as a product but as an experiment. (...) The fact is that the actual product does not have to exist at all. (...) Rather than build a whole system, build a simple landing page with some screenshots from your graphic designer (think of about.me).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.