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.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JUNE 5, 2009

She has a separate team, with its own culture and office, and a mandate straight from top management to innovate without regard to the company’s historic products, channels, or supply chain. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 14, 2009

Because they have no presence in the market, they have to find distribution channels to bring in customers. First of all, it means that most aggregate measures of success, like total revenue, are not very useful. People talk about funding funding funding, bootstrapping, etc., Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167