The MVP Bridge Builder
Iterative vs. Incremental. Build a bridge layer-by-layer to deliver value early, or section-by-section and risk delivering nothing.
Theoretical Background & Agile Dynamics
This game illustrates the critical difference between <1>Iterative</1> and <1>Incremental</1> development.
- <1>Incremental (Waterfall) Strategy:</1> Building the bridge section-by-section (e.g., building one perfect, sturdy pillar) is like building a single, perfect wheel for a car. It's a high-quality component, but it delivers zero value on its own. You can't cross a chasm on one pillar, just as you can't get to your destination with just a wheel. If you run out of time before the rest of the bridge is built, the entire effort is wasted.
- <1>Iterative (Agile) Strategy:</1> Building a simple, complete bridge first (for pedestrians) delivers value immediately. It solves the customer's core problem ('get from A to B'). You can then <1>iterate</1> on it, upgrading it to support bicycles, then cars, and finally trucks, gathering feedback and delivering more value at every stage. This is a common analogy, similar to the famous 'skateboard to car' example by Henrik Kniberg.