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

JULY 5, 2010

Brant and Patrick undertook a difficult challenge: to provide a generally accessible introduction to Customer Development, without diluting its impact or dumbing-down its principles. Case Study: Continuous deployment makes releases n. On the minus side, that has made it a wee bit hard to understand. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

OCTOBER 26, 2009

Every time you listen to customers, you fear diluting your vision. Every time you listen to customers, you fear diluting your vision. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

AUGUST 24, 2009

And as everyone’s attention starts to focus on those same indicators, their value is being diluted. We’ve learned that data can be used as a reality-check against vision without diluting the mission or reverting to “sum of all features&# focus groups. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Lean Technical Review Distribution 113