How does development look different at a startup where learning (rather than working software) is our most important measure of progress?
Lean Startup is about creating companies with a BIG VISION, where we want to change the world and do something really significant. It's a methodology developed by Eric Ries to combine Agile Development with Customer Development so that we can be disciplined about how we create our startups. Come learn the concepts behind Lean Startup and discover how development looks different when you're creating things that nobody else done before.
[Slides from my ScrumClub Presentation (December 9, 2010)]
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
Lean Startup: How Development Looks Different at a Startup
1. Lean Startup
How Development Looks Different at a Startup
Abby Fichtner
Developer Evangelist for Startups, Microsoft
@HackerChick
http://HackerChick.com
2. “Getting used to emergent design is hard
because if feels like you’re going to be just
hacking! And if you’ve prided yourself on
being a very good developer and always
doing well-thought-out designs, it turns your whole world
upside down and says “no, all those things you thought
made you great, now those same things actually make you a
bad developer.” Very world-rocking stuff.”
- Abby Fichtner “Hacker Chick”
3.
4. “Considering the incredible amount of human energy, passion, and
creativity that we invest in creating new products & services…
@EricRies
6. Promise of the Lean Startup
Instead of building our startups according to myths
We can guide them with facts and knowledge
@EricRies
7. We won’t waste our time building
things that nobody wants.
@EricRies
8.
9.
10.
11.
12.
13.
14.
15. “Most technology start-ups fail not because the
technology doesn’t work, but because they’re making
something that there is not a real market for”
@EricRies
29. Minimum Viable Product (MVP)
strategy for fast & quantitative
market testing of a product or feature
wikipedia
30. “Papa built our last tree house in a day!”
“Yeah, but that tree house was a couple pallets
and a ladder”
The Minimum Viable Tree House by Christian Wyglendowski
31.
32.
33. We had an idea for a new product.
We went off & built it, put it on our website.
Not a single person clicked thru to it
What did we learn from that?
34. We had an idea for a new product.
We went off & built it, put it on our website.
Not a single person clicked thru to it
Was there a faster way to get through
that learning loop?
45. Product/Market Fit
When a product shows strong demand by
passionate users representing a sizeable market
The Entrepreneur’s Guide to Customer Development: A “Cheat Sheet” to the Four Steps (@BrantCooper, @Vlaskovits)
69. WiredReach Case Study
BEFORE AFTER
2 week release cycles Multiple releases/day
Releases were all-day events Releases are non-events
Release size: 100’s LOC Release size: < 25 LOC
More emergency releases Less fire-fighting
@AshMaurya
75. Beyond Agile
Agile Lean Startup
Solution Unknown Problem Unknown
Elicit Stories from Customers Validate Features with Market
Get Through the Loop
2 Week Sprints
as FAST as possible
Continuous Integration Continuous Deployment
Done = Software Ready to Go Done = Validated Learning