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

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”). For example, when your company adds ano ther blade to its disposal razors , the product’s technical development, marketing and sales will follow relatively predictable paths.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

SEPTEMBER 11, 2009

I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them.

Community 158

Community Management Lean Software Review 158