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

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

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

4 T's - Technology, Time, Teamwork, Transparency

1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished. 3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...

High-Tech Yuga

Search This Blog