A Minimum Viable Product (MVP) is doing the smallest possible thing in order to learn. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MVP). A MVP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users. Determining what features should be included in or excluded from your MVP is a critical task with major ramifications.

1. SERGEY SUNDUKOVSKIY PH.D.
Product Development Founder
Institute
1

2. Agenda
2

3. Company
3

4. Executive Summary
Pixlwise is an adult education platform designed to
enable learning and skill acquisition through game
play. It aids end-consumer knowledge retention
through repetition, hands on experience and expert
advice
4

5. Problem
Problem: Traditional and online education experience
relies on memorization and understanding of
abstract concepts. In many cases it does not
adequately prepare students for demands of real-
world environment
5

6. Solution
Solution: Pixlwise allows students to absorb
educational material through game play without
placing undue emphasis on the actual process of
learning. Unlike, other competitive products Pixlwise
offers a learning environment closely resembling
real-word conditions
6

7. Startup Alley
7

8. Competitors (Assignment 1)
8

9. Key Features (Assignment 1)
 Udemy – Enables instructors to engage with their users,
providing participants with the ability to “subscribe” to
courses so they are more engaged. They can also ask
questions via the discussion boards and publish links and
comments on course to Twitter and Facebook.
9

10. Product Roadmap (Assignment 2)
Nirvana Features (Everything I Ever Wanted)
Version 1 (GA)
Public Beta
Core Functionality (MVP or MTP)
10

11. Product Lifecycle
11

12. “Nirvana” Features (Assignment 2)
 Forum
 Profile Management
 Subscription Management
 Section Management
 Post Management
 Reply Management
 Reputation Management
 Support Management
 Player Management
12

13. “Nirvana” Drilldown (Assignment 2)
 Post Management – Allows users manage post related
activities in the Forum
 Manage User Posts (author, update, delete)
 Manage Post Reputation (helpful, unhelpful)
 Manage Post Categorization (tagging)
 Manage Post Visibility (vote, unvote)
 Manage Post Appropriateness (flag, unflag)
 Manage Post Notification (follow, unfollow)
13

14. Version 1 (Assignment 2)
Post Management – Allows users manage post related
activities in the Forum
 Manage User Posts (author, update, delete)
 Manage Post Categorization (tagging)
 Manage Post Reputation (helpful, unhelpful)
 Manage Post Visibility (vote, unvote)
 Manage Post Appropriateness (flag, unflag)
14

15. Beta (Assignment 2)
Post Management – Allows users manage post related
activities in the Forum
 Manage User Posts (author, update, delete)
 Manage Post Reputation (helpful, unhelpful)
 Manage Post Visibility (vote, unvote)
 Manage Post Appropriateness (flag, unflag)
15

16. Core Functionality = MVP = Alpha (Assignment 2)
 Post Management – Allows users manage post related
activities in the Forum
 Create Post – Allows Forum user to create posts
 Delete Post – Allows Forum admin or Post creator to delete post
16

17. Mind Map (Assignment 2)
17

18. Product Spec (Assignment 3)
Target Customer
Wireframes
Mockups
Final Creatives
Flow Diagrams
User Stories
Business rules
18

19. Target Customer (Assignment 3)
Target Customer – Pixlwise is a B-C solution targeted to
consumers seeking alternative education
 Age – 18 to 40
 Income – $30K/Y and below
 Education – High School and below
 Internet Experience – Novice
 Demographics – Any
 Industry – Any
19

20. Interface Driven Design
20

21. Wireframe (Assignment 3)
21

22. Wireframe (Assignment 3)
22

23. Clickable Prototype (Assignment 3)
23

24. Mockup (Assignment 3)
24

25. Final Creatives (Assignment 3)
25

26. Flow Diagram (Assignment 3)
26

27. Invision (Assignment 3)
27

28. User Story (Assignment 3)
User Story – As “Who” I want “What” and “Why”
 As a User I Want to Be Able to Author a Post
 As a User I Want to Be Able to Mark a Post as Helpful/Unhelpful
 As a User I Want to Be Able to Add a Tag to the Post
 As a User I Want to Be Able to Follow a Post
 As a User I Want to Be Able to View My Billing Statements
28

29. Business Rule (Assignment 3)
Business Rule – Non Trivial Rules
 Subscription plan upgrades are effective immediately
 Subscription plan downgrades are effective as of new billing cycle
 In case of credit card rejection system will repeat billing attempts
three times two days apart. Upon third rejection customer will be
downgraded to a “Free” Subscription Plan
29

30. Development Plan (Assignment 4)
Agile
Versions
Sprint Planning
Daily SCRUMs
Backlog
Roles and Responsibilities
30

31. Agile Umbrella
31

32. Planned vs. Agile
32
VS

33. Planned vs. Agile
 Planned Process
 Exhaustive Planning (plan until you are exhausted)
 Prescriptive
 Document Centric
Agile Process
 Iterative Planning
 Non-prescriptive
 Practice Centric
33

34. False Agile
Just Because You Call It Agile It Does Not Mean It Is
34

35. You Are Not Agile If
Requirement Frontloading
QA Backloading
You Move Dates Instead of Feature Negotiating
You Extend Sprints/Iterations
You Are Not Producing Code by Third Week of the
Project
You Have No Business Representation
You Are Not Tracking Requirements
You Do Not Keep Track of Velocity/Drumbeat
35

36. Versions (Assignment 4)
Version 0.1 = MVP = Alpha
 Sprint 1
 Sprint 2
 Sprint 3
 Sprint 4
Version 0.X = Beta
Version 1 = GA
36

37. Roadmap (Assignment 4)
37

38. Sprint Planning (Assignment 4)
Sprint Duration
 2 – 3 weeks
Sprint
 Stories – Stories that are close together go together
 Story Estimation – Hours or Story Points (Fibonacci Estimation)
 Working Hours = Ideal Hours (1 day = 6 ideal hours)
 Process Tasks (meetings, planning, etc)
 Working Hours vs. Process Hours (do not double dip)
 Schedule Feature Holidays
38

39. Sprint Planning (Assignment 4)
39

40. Daily SCRUMs (Assignment 4)
SCRUM Duration
 15 min at most
What to Talk About
 Only 3 questions
 What have you done yesterday?
 What are you doing today?
 Are you blocked?
 No rabbit trails
 Take it outside
 Must have planning software in front of you
40

41. Backlog (Assignment 4)
Backlog Size
 It is not the size, it is how you use it
 2–3 Sprints ahead
What to Keep in the Backlog
 User Stories
 Tasks
 Bugs
 Technical Debt
41

42. Roles and Responsibilities (Assignment 4)
Roles = Separation of Concerns
 Why – Business Guy/Girl
 What – Product Guy/Girl
 When – Project Guy/Girl
 How – Technical Guy/Girl
Business Co-Founder
 Why and What
Technical Co-Founder
 When and How
42

43. Estimation (Assignment 5)
Resourcing
 Front End Developer – Market Price
 Designer – Market Price
Infrastructure
 Server Hosting – AWS or Rackspace
43

44. KPIs (Assignment 6)
Estimated vs. Actual
Story Points Per Release
Stories Per Sprint
Defects Per Sprint
Story Churn
Defects Post Release
44