Lean Startup for AaltoES Summer of Startups
•Download as PPTX, PDF•
14 likes•4,317 views
Introduction to lean startup and the story of nextdoor.fi as lean startup
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Lean Startup for AaltoES Summer of Startups
Similar to Lean Startup for AaltoES Summer of Startups (20)
More from Marko Taipale
More from Marko Taipale (20)
Recently uploaded
Recently uploaded (20)
Lean Startup for AaltoES Summer of Startups
- 1. Lean startup Marko Taipale – Huitale Summer of Startups
- 3. I.What is a Startup? II.Our story III.Q&A
- 4. I.What is a (lean) Startup?
- 8. Make the cycle as short as possible
- 9. ” Where do I get the ideas to build?” what to build
- 11. “No plan survives first contact with the customers” - Steven Blank
- 12. Customer Development Customer Discovery Customer Validation Customer Creation Scale Company
- 13. Customer Development Customer Discovery Customer Validation Customer Creation Scale Company Hypotheses, experiments, insights Data, feedback, Insights Agile Product Development
- 14. Customer Development Problem Team Customer Discovery Customer Validation Customer Creation Scale Company Hypotheses, experiments, insights Solution Team Data, feedback, Insights Agile Product Development
- 15. Iterating the business model - The Pivot Business Model Iteration Strategy Tactical Agile Product Development Customer Development Source: Ann Miura-Ko Maples Investments
- 16. “Should I do whatever my customers want me to do?”
- 17. “Should I do whatever my customers want me to do?”
- 18. Create product vision and validate it with customer development Vision = a boundary for her wishes
- 19. Is agile about delivering features as fast as possible?
- 20. Nr 1 waste = Unused features Building a feature maybe the wrong answer Who cares about velocity? We can work on highest priority story – who cares?
- 21. It is not about how much but rather how little you can release Minimum Viable Product
- 22. Find your Minimum Viable Product It should make you feel embarrassed
- 23. “It's the things that are not there that we are most proud of"
- 25. Why? Who? What?
- 27. 120 man days / Beta -70 functionalities -50 User interface (1. day = get some laptops)
- 30. 30 000 visitors / month >2 000 active users >300open offer/request 3 days lead time
- 31. 1/day release to production 24/7 monitoring 1/day backups 1/day biz reports 5 integrations
- 32. 550+ acceptance tests >80% test coverage 28 IE6 issues 2 bugs (in 3 years)
- 33. 0 people in operations 0 testers 0 full-time developers Production bug fix < 1h
- 34. Ok.. So how we do it?
- 35. Product Queue READY MMFs Themes 3 7 2 2d 2d 6d 15min 1min 2h
- 36. Product Queue READY MMFs Themes 3 7 2 2d 2d 6d 15min 1min 2h From READY to DONE 6 days Dev time: From NOT STARTED to DONE 8 days DWT: (PQ size * Dev Time) / capacity = (7 * 8) / 2 = 28 days
- 37. Problem team Solution team Product Queue READY MMFs Themes 3 7 2 2d 2d 6d 15min 1min 2h From READY to DONE 6 days Dev time: From NOT STARTED to DONE 8 days DWT: (PQ size * Dev Time) / capacity = (7 * 8) / 2 = 28 days
- 38. ! Problem team
- 39. Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 40. Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 41. Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 42. PLAN! Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 43. Review! Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 44. Themes (3) Product Queue (7) READY (2) In Progress (2) Done TODO Done X Y Z SMART goals MMF Biz Value Definition of READY Definition of DONE Updated metrics
- 45. Comments for service offers and requests Owner: Marko Size: S 5 days QUEUE: 1.6.2010 DONE: 6.6.2010 READY: 3.6.2010 3 days
- 46. “Never doubt that a small group of thoughtful, committed people can change the world Indeed, it is the only thing that ever has” - Margaret Mead
- 47. Marko Taipale @markotaipale huitale.blogspot.com marko.taipale@huitale.com I help companies to improve by showing what I have done how I have done it and what I have learned about it. I am a CTO of a lean startup
- 48. Photo credits Flickr users http://www.flickr.com/photos/kodomut/ http://www.flickr.com/photos/amagill/ http://www.flickr.com/photos/themarmot/ http://www.flickr.com/photos/unloveable/ http://www.flickr.com/photos/shapourbahrami/ http://www.flickr.com/photos/thatguyfromcchs0 http://www.flickr.com/photos/fxtreme/ http://www.flickr.com/photos/aussiegall http://www.flickr.com/photos/lululemonathletica http://www.flickr.com/photos/4yas http://www.flickr.com/photos/sualk61/ http://www.flickr.com/photos/can3ro55o/ http://www.flickr.com/photos/jwdill/ http://www.flickr.com/photos/minidriver/ http://www.flickr.com/photos/donaldmacleod/ http://www.flickr.com/photos/jburgin/ http://www.flickr.com/photos/jmherrala/ http://www.flickr.com/photos/xurble
Editor's Notes
- Today: 45 min presentation, 15 min questions, 20 mins+ coaching for each startupThegoals 1) how to develop only what’s really needed 2) how to be agile in what you do
- Huitale is a product companyWe are also consulting others about how to create products in agile and lean way.
- Make the world a better placeFind scalable business model
- Startup learning cycle (Plan-Do-Check-Act)
- Example: In our product development it takes 8 days to get idea to production with measurements in place
- Customer is LOST
- Plan won’t survive.
- Who is your customer? User != CustomerParallel process to product developmentDiscover, Validate, Create,scale
- Information flows
- Problem team figures out the problem (might have PO)Solution team works on the solution to the problemCOLLABORATION – UX, Architecture visions
- on average companies (you might also think new product area as a company)changes their biz model 2,5 times - drastically.
- Porsche
- VolvoExample: 300 configurations, (NO TESTING – DROP CUSTOMER)
- Test manually if you customer really wants itNext: Ok, lets take a look back a bit…
- DoD – Do you validate the things are used? Do you drop features?Statistics say that 2/3 of features are not used
- Can be better than Maximum Product!What’s your MVP?
- Why?:No online marketplace for local services,Services are problematic to buy (prize?, quality?, who? Where?Who: Anyone nearby from entrepreneurs to students to senior citizens, anyone who needs or offers servicesWhat: household services like childcare and such, portal, marketplace
- MVP – shame!
- Integrations
- - Release every day, automated deployment with rollbacks Monitoring backups and business reports every day integrations so it is not a standalone product
- All testing is automated (performance, acceptance, unit, integrations)
- We do not have too many ppl (4 developers)
- So how we do it?!
- Esimerkki: ”improve communication between users” themeComments and private messaging between users
- Problem team: PO (CEO), 1 techie, 1 uxd, 1 sales/marketingSolutions team: 4 members, 2 java guys, 1 UXD (ext), 1 html dude (ext)
- Meet the usersLet users vote and do researchUsers feedbackMetricsCollaboration partnersNew ideas / competition
- Initial state
- 2 to be ready
- On got defined ready
- Plannning on demand
- Done – review on demandIP blockkaa, one done
- Automated tests and quality metrics, production next day, metrics for each feature (remove waste)DOD and READYDaily standups
- A card: Predicatability, layouts, cycle and lead times, metrics to measure the value for each feature