What is an MVP and why it is a good idea?
If your project involves building an entirely new application, consider planning and starting with a Minimum Viable Product (MVP).
A minimum viable product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development.
A focus on releasing an MVP means that developers potentially avoid lengthy and (ultimately) unnecessary work. Instead, they iterate on working versions and respond to feedback, challenging and validating assumptions about a product’s requirements.
The Objectives of MVP
- Be able to test a product hypothesis with minimal resources
- Accelerate learning
- Reduce wasted engineering hours
- Get the product to early customers as soon as possible
- Base for other products
- To establish a builder’s abilities in crafting the product required
- Brand building very quickly
Remember that Testing is the essence of minimum viable products. MVP seeks to test out whether an idea works in market environments while using the least possible expenditure.
How long will MVP take to build
This is entirely dependant on the project and complexity, but it is reasonable to expect an MVP to take a minimum of 6 weeks, and with the right velocity and limited feature set, the team should be able to deliver an MVP within 3 months.
Launch phase focuses on launching the platform live and initial monitoring in order to spot potential problems. The work undertaken includes:
- Preparing Production server environment
- Monitoring services for a defined period of time
- Fixing potential problems
- Producing final documentation