Executive Summary -> Handed to DeveloperSpent Most of Your BudgetBuilt the Wrong Thing – Not Proving Your NumbersProduct Quality - Code is Crappy, Full of Bugs, Missing Critical FeaturesDoesn’t Scale Past a Couple UsersNot Protected – Access to Code, Rights on Code
Before you build your MVP as a non-technical founder
Making Sure You Are Ready toBegin Building Your MVPColoftApril 2013Tony Karrer, Ph.D.CEO, TechEmpower, Inc.firstname.lastname@example.org://socalcto.com
2Background• Ph.D. Computer Science, LMU Professor CS 10 Years• Founder– Sprinkler Systems Installation (age 15)– Knowledge Stream ($59M exit)– TechEmpower (1997 - present)– Aggregage (2010 – present)• Part-Time CTO / Technical Advisor– Talk with 100+ startups each year
7Document for a Developer• Business / Product Concept• User Types• User Stories• Wireframes• Feature Specification• Technical Requirements (Scale, Systems)• Others– Personas– Use cases– Requirements
10Protect Yourself• Own the Document/Issue Tracker/Code Repository,Hosting Arrangement, SSL Certificates, etc.• Iterations• Deliverables/Features/Functions• Test, Fix Process• Price - Not to Exceed• Termination• Agile?
11Development Issues• http://www.socalcto.com/2010/03/symptoms-of-weak-development-team.html• Missed deadlines• Delivery of code/product that clearly has not been tested;Bugs – no big deal. The system keeps crashing – noproblem; Annoyed at testers for finding bugs.• Fixing one thing breaks something else• No attention to detail, don’t ask questions