Introducing iterative development into an org that has never done it; it is important to align on some definitions:

Prototype - demonstrates the ‘art of the possible’, a visual representation of the concept.

Proof-of-Concept - Demonstrates ‘the feasibility’. A working example of the concept. Built to test and learn. not launch at scale.

Pilot - Creating ‘a measurable test’ a trial to work out details before rolling out to a larger population.

Production - the concept hardened at scale.

Each of these have different risk profiles, and there are determined decision gates before a concept gets promoted from one to another.

A prototype can be scrappy, even simple simple paper.

A proof-of-concept is not only a good place to test a working example, but a great time to experiment with different tools, code frameworks, infrastructure etc.

A Pilot is where things start to become hardened, if you don’t have a security and performance ops person in your dev team this is where you absolutely want them.

These are on a continuum with different objectives, decisioning, risk profiles, and tooling/infrastructure.

In Agile you will hear MVP (Minimal Viable Product), MMR (Minimal Marketable Release), MMF (Minimal Marketable Feature) and MMP (Minimal Marketable Product).

Original Linked in Post: http://bit.ly/2jZGzvc