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

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 - archite

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir