A minimal product is the smallest valuable capability that can reach users, test initial assumptions, and provide evidence for the next increment. Treat its feature set as a hypothesis rather than a fixed specification. section 2.1.4
Apply the pattern by:
- Starting with one basic configuration or capability instead of a long list of agreed features. section 2.1.4
- Delivering incremental value at every stage, then observing early-adopter behavior and feedback. section 2.1.4
- Replacing speculative completeness with short iterations that can change priorities when evidence contradicts assumptions. section 2.1.4 section 10.2.3
Platform deployment automation
A platform team can begin with an MVP that automates basic deployment tasks rather than spending months building a complete automation tool. Later increments can add automated testing and rollback mechanisms, guided by user feedback. section 10.2.3
Figure 2.5 The progression of an MVP delivery process. A fully functional product does not need to be delivered at the start, but all phases should deliver some incremental value to the customer.
Use the progression from skateboard to bicycle to motorcycle to car—or other staged delivery models—to assess whether each increment creates customer value. section 2.1.4
