from an idea to a product
DESCRIPTION
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.TRANSCRIPT
SERGEY SUNDUKOVSKIY PH.D.
From an Idea to a Product1
Introduction2
Background3
Agenda4
Product Building
WHY BUILD PRODUCTS?Costly
UncertainTime Consuming
5
Product Building (cont.)
DON’T, IF YOU CAN AVOID ITPartner
Use ExistingIntegrate
6
Product Building (cont.)
WHAT DO YOU GET OUT IT?Improved Margin (if you build it right)
Control (more or less)Opportunity (if you do it fast enough)
7
Well It Could Have Happened8
How Do You Eat an Elephant?9
HOW?10
Design Centric Approach11
WalkMe12
Guided Flow13
Help Bar
Wireframes14
Wireframes (cont.)15
Wireframes (cont.)16
Wireframe Structure17
Wireframing Tools18
Mockups19
Mockups (cont.)20
Mockups (cont.)21
Static Prototype
Wire it together
22
Static Prototype (cont.)23
Static Prototype (cont.)24
Prototyping Tools25
Mark Up26
Who
You Can’t Outsource What You Do Not Understand
27
Offshore Development
It is not going to be cheaper
28
Fixed Bid Projects29
Just do not do it
Someone You Trust30
Have somebody on your side of the table
All The Wrong Reasons31
Wrong Expectations Solution to Ignorance (outsourcing what you do not understand) It Will Be Cheaper (min 30% overhead) We Can Achieve Instant Scalability (it takes time to hire) Poaching Is not a Problem (no difference) We Can Minimize Office Distractions (hallway magic)
All The Right Reasons32
Right Expectations Somewhat Easier to Find Talent 24 h Dev/QA Cycle Improved Ramp Up/Ramp Down Cycles Specific Expertise
Vendor Speak33
What Do They “Really” Mean34
We Can Do Anything (we do not have a specialization)We Need a Product Spec (we are going to sit and wait until you
give us specification on stone tablets) We Can’t Tell You Finish Date (we have not looked at the
details)This Can’t Be Done (we do not know how to do it)We Made It Work on a Local Machine
Works Locally
We are not shipping your computer
35
What Do They Mean36
We Are Making Good Progress (things have likely stalled)We Are Working on the Back-End (we have not done much)We Will Tie Lose Ends Later (it will not be our problem)We Are 90% Done
90% Done Problem
What Do They Mean by That?
37
Congruent Culture
Pick a Congruent Culture
38
Offshore Team Picking39
Congruent Culture (challenge authority)Language Gap (make sure you speak it)Working Hours Overlap (4+)Right Size (30+ large enough to have a bench)Right Size (100- small enough to care)Right Focus (we do everything)Do Not Let It Grow (micro-teams)
Managing Your Project40
Do Not Throw It Over the Wall41
Nothing good will come of it
Planned vs. Agile42
VS
SCRUM
Do you SCRUM?
43
Agile SCRUM Process44
Show and Tell
Weekly Show and Tell. This is the only way
45
Weekly Activities46
Daily SCRUM Meetings What did you do? What are you working on? Are you blocked?
Weekly SPRINT Planning What User Stories are we going to do? Are they clear? What is the estimate?
Weekly Show and Tell Do not tell it to me, show it to me
Defining Your Product47
Defining MVP48
MVP Core Functionality
Ideal MVP
49
Ideal MVP
Mini-Me is an Ideal MVPCore Functionality
Identical “DNA” Same Major Features Same Major Functionality Same Usability Not Up To Scale Not As Pretty
50
MVP Features
“Easy to Use Was not on the List”
51
MVP Attributes
Intelligent Design ConceptsIrreducible Complexity
Can’t Take Anything Away Can’t Be Simpler
Most Efficient For What It Does Most Efficient Wins Most Efficient Survives
Path to Intent Most Straightforward Path to Intent
52
Irreducible Complexity
Simplest Mousetrap
53
Path To Intent
“Reboot After Every Click”
54
Intent Documentation Elements
Intent Documentation Assumptions Epics User Stories System Use Cases Business Rules Actors
55
User Stories
As Who I Want This and Why
56
User Stories Myopic View
Watch Out For Myopic View
57
“Nirvana” Features
Admin Installation Analytics Account Management Help Management Walk Through Management Tutorial Management Video Management App Management
58
“Nirvana” Drilldown
Account Management – Allows user to manage accounts and account related activities in the system Manage User Accounts (create, update, delete) Manage Master Account (update) Manage User Permissions (author, update, publish) Manage Account Subscription (upgrade, downgrade, cancel) Manage Payments (credit card info)
59
Mind Map60
Core Functionality = MVP = Alpha
Account Management – Allows user to manage accounts and account related activities in the system Reset Password – Allows account users to reset credentials
61
Beta
Account Management – Allows user to manage accounts and account related activities in the system Manage Account Subscription (upgrade, downgrade, cancel) Manage Payments (credit card info)
62
GA
Account Management – Allows user to manage accounts and account related activities in the system Manage User Accounts (create, update, delete) Manage Master Account (update) Manage User Permissions (author, update, publish)
63