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.
7. 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
31. All The Wrong Reasons
31
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)
32. All The Right Reasons
32
Right Expectations
Somewhat Easier to Find Talent
24 h Dev/QA Cycle
Improved Ramp Up/Ramp Down Cycles
Specific Expertise
34. What Do They “Really” Mean
34
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
36. What Do They Mean
36
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
39. Offshore Team Picking
39
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)
46. Weekly Activities
46
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
50. Ideal MVP
Mini-Me is an Ideal MVP
Core Functionality
Identical “DNA”
Same Major Features
Same Major Functionality
Same Usability
Not Up To Scale
Not As Pretty
50
52. MVP Attributes
Intelligent Design Concepts
Irreducible 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
61. 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
62. 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
63. 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