MVP development
Build the first version around a real question.
Scope
A first release with a specific job to do
Choose the assumption
Name the customer, the task and the behavior that would make further investment worthwhile.
Build a complete first workflow
Focus the scope without omitting the reliability, access or support needed for real use.
Plan what to learn
Agree how usage and feedback will inform the next release, a change of direction or a decision to stop.
Before we start
How small should the first release be?
Small enough to test the important assumption, complete enough for the chosen users to finish their task. We include the access, error handling and support that task requires.
Can a prototype answer the question first?
Sometimes. A prototype can expose a confusing interaction; a technical experiment can test an integration. If those answer the immediate question, building a production release may be premature.
What do you need to learn from the first users?
Bring the proposed product and the assumption behind it. We can choose the first scope that gives you useful evidence.