Remove Continuous Deployment Remove Customer Development Remove Document Remove Product
article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

article thumbnail

Tesla and Adobe: Why Continuous Deployment May Mean Continuous Customer Disappointment

Steve Blank

For the last 75 years products (both durable goods and software) were built via Waterfall development. This process forced companies to release and launch products by model years, and market new and “improved” versions. The Old Days – Waterfall Product Development. Waterfall – The Customer View.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Top 120 Startup Posts for 2010

SoCal CTO

Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc.

article thumbnail

Lean Startup at Scale

Startup Lessons Learned

Palantir is a deep technical play and we had a lot of code to write just to fill out the product vision that we had already validated with potential customers; it took us two straight years of development to go from early prototypes to software that could be used in production. So what was going on?

Lean 167
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document.

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. What is customer development?

Agile 76
article thumbnail

Lessons Learned: Ideas. Code. Data. Implement. Measure. Learn

Startup Lessons Learned

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. How about documentation that nobody reads? the data on a regular basis.