<p>Dan is close.  I think the easy way to describe the difference is that the two have different customers.  The customer of the walking skeleton is the dev (and ops) team, in that it implements the simplest thing from each of the elements of the architecture and strings them together in a working way.  For example, it has a front end, it has a backend, it has a database, and it can move null betwween the three layers of the arhitecture.  It can be deployed in production; but from a user perspective it doesn't really <em>do</em> anything.</p>

<p>In contrast, the customer of the MVP is, well, the end user of the product.  It's the simplest slice of functionality that can satisfy the core payoff/value for the user.  The MVP is then the smallest amount of value that can be delivered that demonstrates that the application is worthwhile.   Often this is completely the opposite of a walking skeleton.  A common approach is a 'concierge' MVP, where the steps are manually performed behind say a simple landing page or google form, with the results sent to the user over email.</p>

CC BY-SA 3.0
2018-02-12T06:10:15.560Z
2018-02-12T06:10:15.560Z
toddwseattle
<p>Based on the following two comments to the referenced answer in the question:</p>

<p>@Adrian:</p>

<blockquote>
  <p>I guess it's the delivery pipeline equivalent of a minimum viable product.</p>
</blockquote>

<p>@DaveSwersky</p>

<blockquote>
  <p>This does sound similar to minimum viable product, but at a more
  granular level- "minimum viable component" perhaps. Returning 200 from
  a service just to get it "running" sounds like a stub to me.</p>
</blockquote>

<p>it looks like that a <code>Walking skeleton</code> is not identical, but a smaller <code>MVP</code>.</p>

CC BY-SA 3.0
2017-08-10T16:22:31.307Z
2017-08-10T16:22:31.307Z
030
<p>The walking skeleton reflects the rough structure/shape of the product, but it may be entirely stubbed out (initially), meaning it may not be actually functional. The skeleton cannot move without the muscles.</p>

<p>The MVP however must meet a certain minimum functionality level to be considered viable.</p>

<p>As development progresses the walking skeleton typically morphs into an MVP and eventually into a final product.</p>

CC BY-SA 3.0
2017-08-10T22:11:43.850Z
2017-08-10T22:11:43.850Z
Dan Cornilescu
<p>I've recently stumbled upon the <a href="https://devops.stackexchange.com/questions/712/what-is-a-walking-skeleton">"Walking skeleton" term</a> and got a bit confused about the terminology.</p>

<p>Is it the same or a variation of a <a href="https://en.wikipedia.org/wiki/Minimum_viable_product" rel="noreferrer">Minimum Viable Product</a>, or how does it relate to MVP in general?</p>

<terminology><practices><patterns>
What is a difference between a Walking Skeleton and an MVP?
alecxe
# What is a difference between a Walking Skeleton and an MVP?

(Asked by: username_0 on 2017-08-10)

I've recently stumbled upon the ["Walking skeleton" term](https://devops.stackexchange.com/questions/712/what-is-a-walking-skeleton) and got a bit confused about the terminology.

Is it the same or a variation of a [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), or how does it relate to MVP in general?

**Tags:** terminology, practices, patterns


---

## 3 answers

### Answer by username_3 on 2017-08-10. Score: 4 | Accepted answer

The walking skeleton reflects the rough structure/shape of the product, but it may be entirely stubbed out (initially), meaning it may not be actually functional. The skeleton cannot move without the muscles.

The MVP however must meet a certain minimum functionality level to be considered viable.

As development progresses the walking skeleton typically morphs into an MVP and eventually into a final product.


---

### Answer by username_1 on 2018-02-12. Score: 4

Dan is close. I think the easy way to describe the difference is that the two have different customers. The customer of the walking skeleton is the dev (and ops) team, in that it implements the simplest thing from each of the elements of the architecture and strings them together in a working way. For example, it has a front end, it has a backend, it has a database, and it can move null betwween the three layers of the arhitecture. It can be deployed in production; but from a user perspective it doesn't really *do* anything.

In contrast, the customer of the MVP is, well, the end user of the product. It's the simplest slice of functionality that can satisfy the core payoff/value for the user. The MVP is then the smallest amount of value that can be delivered that demonstrates that the application is worthwhile. Often this is completely the opposite of a walking skeleton. A common approach is a 'concierge' MVP, where the steps are manually performed behind say a simple landing page or google form, with the results sent to the user over email.


---

### Answer by username_2 on 2017-08-10. Score: 2

Based on the following two comments to the referenced answer in the question:

@Adrian:

> I guess it's the delivery pipeline equivalent of a minimum viable product.

@DaveSwersky

> This does sound similar to minimum viable product, but at a more
> granular level- "minimum viable component" perhaps. Returning 200 from
> a service just to get it "running" sounds like a stub to me.

it looks like that a `Walking skeleton` is not identical, but a smaller `MVP`.


---

