Harisenin Bootcamp

HS UI/UX & PM#3

Deliver a
#3
Minimum Viable
Product (MVP)
Owen Nixon Jimawan
May 25th, 2022 | 19.00-21.00
EXPERT INTRODUCTION
 PART 1

Introduction to MVP

PART 2

Class
Examples MVP's different business models

PART 3

Agenda
Building MVP

PART 4

Learn the Fundamentals of Agile Estimation

PART 5

Write Agile Documentation: User Stories &

Acceptance Tests
 PART 1

MVP Introduction to MVP

Subject Name |
99 % STARTUPS FAIL

More starups fail from a lack of customer

than from failure of product development

FOCUS ON CUSTOMER AND MARKET ! KEY

FOCUS ON
CUSTOMERS
AND MARKET

Subject Name |
basic design thinking

KEY
FOCUS ON
CUSTOMERS
FOCUS ON CUSTOMER AND MARKET ! AND MARKET

Subject Name |
THATS WHY WE NEED…

MVP
Minimum Viable Product
WHAT IS MVP ?
WHY WE NEED… ?

MVP
Minimum Viable Product
 BASIC CONCEPT

MVP
Minimum Viable Product
 PART 2

Examples MVP's different

business models

Subject Name |
 PART 3

MVP BUILDING MVP

Subject Name |
THREE KEY CHARACTERISTICS OF MVP

FUTURE BENEFIT VALUE FEEDBACK

DEMONSTRATES ENOUGH IT HAS ENOUGH VALUE IT PROVIDES FEEDBACK

FUTURE BENEFIT TO THAT PEOPLE ARE WILLING LOOP TO GUIDE FUTURE
RETAIN EARLY ADOPTERS TO USE IT OR BUY IT DEVELOPMENT
INITIALLY

Subject Name |
FUNDAMENTALS OF MVP

FUTURE BENEFIT VALUE FEEDBACK

IT HAS ENOUGH VALUE IT PROVIDES FEEDBACK

THAT PEOPLE ARE WILLING LOOP TO GUIDE FUTURE
TO USE IT OR BUY IT DEVELOMENT
INITIALLY

Subject Name |
 HOW TO BUILD MVP? 6 STEPS

1 DEFINE THE MVP IDEA
Define the purpose of the product
and the issue it will resolve
PRODUCT
2 3 PRIORITY PRODUCT
REQUIREMENTS REQUIREMENTS
List down the features of the
List down the requirements that
product. This will help you
needs to be implemented in the
understand the product to a
product.
better extent.

FEEDBACK
PPR DEPENDENCY BUILD PRODUCT 6
4 5 Develop and launch the product
The most important element is the
It may happen that one product feedback which enables you to
feature is dependent on another. It with defined product
know if you are on the correct
is important to identify them in requirements
path or not
advance

Subject Name |
TESTING MVP

1 2 3 4 5

Subject Name |
MEASURING SUCCESS

1 2 3 4

Subject Name |
BUT SOMETIMES…. WHY FAIL?

PRODUCT FAILURE MARKET FAILURE CUSTOMER FAILURE

POOR CUSTOMER NOT CONSIDERING BUILDING FOR TOO

COMMUNICATION ALTERNATIVE SOLUTIONS BROAD AN AUDIENCE

NOT TRANSLATING NOT ADAPTING BUSINESS OPTING FOR ONLY PUSH

CUSTOMER PROBLEMS MODEL TO BE PROFITABLE STRATEGY INSTEAD OF
INTO PRODUCT PULL STRATEGY
REQUIREMENTS

Subject Name |
 PART 4

MVP Learn the Fundamentals

of Agile Estimation

Subject Name |
Learn the
Fundamentals of
Agile Estimation

Subject Name |
Agile is an iterative approach to project management and software development that helps teams deliver value to their
customers faster and with fewer headaches.

Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments.

Subject Name |
Subject Name |
Subject Name |
Subject Name |
 PART 5

MVP Write Agile Documentation:

User Stories & Acceptance
Tests

Subject Name |
Write Agile
Documentation:
User Stories &
Acceptance Tests

Subject Name |
A user story is an informal, general explanation of a software feature written from
the perspective of the end user.

Its purpose is to articulate how a software feature will provide value to the
customer.

Why create user stories?

● Stories keep the focus on the user.
○ A to-do list keeps the team focused on tasks that need to be checked off, but a
collection of stories keeps the team focused on solving problems for real users.
● Stories enable collaboration.
○ With the end goal defined, the team can work together to decide how best to serve the
user and meet that goal.
● Stories drive creative solutions.
○ Stories encourage the team to think critically and creatively about how to best solve for User Story
an end goal.
● Definition
● Stories create momentum. ● Why we have to
○ With each passing story, the development team enjoys a small challenge and a small create an user story
win, driving momentum.

Subject Name |
In Agile, acceptance criteria refer to a set of predefined requirements that must be
met to mark a user story complete.

Acceptance criteria are also sometimes called the “definition of done” because
they determine the scope and requirements that must be executed by developers
to consider the user story finished.

Acceptance Criteria
● Definition
● Why we have to create an
acceptance criteria

Subject Name |
 Template & Example
The standard user story follows the template:
“As a (intended user), I want to (intended
action), so that (goal/outcome of action).”
User story:
As a product manager.
I want to score potential ideas.
So that I can decide what to include on my
product roadmap.
User acceptance criteria follows the template:
“Scenario: (explain scenario). Given (how things begin), when
(action taken), then (outcome of taking action).”
Acceptance criteria for that user story could be:
Scenario: The product manager adds potential ideas and ranks
the best ideas based on benefit versus cost.
Given that I have added two or more ideas and scored them
using the Benefit vs Cost scoring model
Subject Name |
When I click the Rank button
Then ideas are sorted with the top-scoring ideas at the top.
Do you have any
questions?
Dont miss the chance!
Fell free to ask on zoom chat box or
ask directly to the speakers
 Thank you for listening

How do you feel about today's

subject?

Love It Okay