Bootstrapping Continuous Deployment Engineer Product 
Startup Lessons Learned
JANUARY 18, 2010
Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.
Startup Lessons Learned
APRIL 29, 2013
Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). in ten years?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
MARCH 16, 2009
In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. But, over the years I’ve realized that the toughest problem - the one that matters most and was consistently the most challenging - was figuring out what the product backlog should be.
Startup Lessons Learned
FEBRUARY 9, 2009
The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Labels: events 2comments: Andrew Meyer said.
Startup Lessons Learned
MARCH 29, 2010
I believe it means were achieving product/market fit for a set of ideas. These case studies range in size and scope: from pre-product/market fit to already exited, bootstrapped to venture-backed, solo practitioner to large organization. Ideas, products, and capital flow easily across borders. Congratulations. Not anymore.
Startup Lessons Learned
JUNE 5, 2009
I think this idea is particularly appealing to those of us from an engineering background. Sometimes an early negative result from an experiment is a harbinger of doom for that product, and means it should be abandoned. That’s not too surprising, because our product was pretty bad in those days. So far, so good.
Startup Lessons Learned
APRIL 14, 2009
This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months. What’s going on?
Expert insights. Personalized for you.
151 
Let's personalize your content