Startup Lessons Learned

JUNE 15, 2009

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.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

APRIL 29, 2013

Not to mention $200,000 in staff time and hard costs. Generously, it might cost you $20,000. In other words, you could test ten book ideas for the cost of publishing one. Last year, the co -founders of B ack to the Roots talked about their innovation accounting and how they were ignoring sales metrics in order to grow.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

FEBRUARY 28, 2009

I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product. The only reason we learned the art of metrics-based decision making at IMVU was out of necessity. But code written that doesnt help the company succeed is a sunk cost.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. Case Study: Continuous deployment makes releases n.

Community 158

Community Management Lean Software Review 158