45

A "Walking Skeleton" is a form of "proof of concept" of your basic architectural concept. Where a proof of concept typically focuses more on a single functionality, a "Walking Skeleton" is a minimalistic end-to-end implementation. A "Walking Skeleton" is not an outline of your concept (only a "skeleton") but is really executable and shippable (it can "walk" :...


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 ...


4

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 ...


3

I must admit that I don't quite get the examples your giving. Sure, random numbers will be different between the two environments. Blue-green means simply to have two nearly identical production environments with some kind of router/load balancer in front. Clients talk to the load balancer, and the LB routes requests to one of the two environments. To ...


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" ...


Only top voted, non community-wiki answers of a minimum length are eligible