Skip to main content

Minimum Viable Product

Steve Blank said

You’re selling the vision and delivering the minimum feature set to visionaries, not everyone.

The MVP is called minimum, as you should spend as little time and effort to create it as possible. 

But this does not mean that it has to be quick and dirty. 

But try to keep it as small as possible to accelerate learning and avoid the possibility of wasting time and money, as your idea may turn out to be wrong!


You need to validate 2 kinds of hypotheses before you start MVP.

1) Technical

Are you capable from technical point of view? if not there is no product.

2) Market

Is market ready to accept an buy the product?  if not there is no product.

Above 2 hypotheses should be validated in your Product Backlog.

Few inspiring MVP are:

Amazon (launched Amazon B2C, Prime, alexa, echo, etc..) 

Dropbox (Starting out as a demo video MVP, Dropbox explained the benefits of storing data in one place. The feedback from users helped the then-startup receive the funds.)

Facebook (Started to connect friends in social media, and now it's one of the biggest social media getting lot of revenue)

What is expected from customer in MVP?

  • Basic features
  • Performance
  • Excitement
  • Personally likable
  • Reasonable

Client want MVP products to be converted as MMP (Minimum Marketable Product).


Comments

Popular posts from this blog

Voice of the Customer (VoC) vs Voice of the Business (VoB)

  Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Control Chart in Lean Six Sigma

Control Chart in Lean Six Sigma Introduction In Lean Six Sigma , a control chart is a fundamental statistical tool used to monitor process performance over time and ensure that improvements are sustained . It belongs primarily to the Control phase of DMAIC , where the focus is on maintaining process stability and preventing regression after improvements have been implemented. A control chart helps distinguish between normal process variation and abnormal variation that requires investigation and corrective action. What Is a Control Chart? A control chart is a time-ordered graphical display of process data with statistically determined limits. It answers a critical question: Is the process stable and predictable, or is something unusual happening? A typical control chart consists of: Center Line (CL) – the process average or mean Upper Control Limit (UCL) – upper boundary of expected variation Lower Control Limit (LCL) – lower boundary of expected variation Plotted data points o...

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...