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

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 5, 2009

That’s because the model is based on assumptions about customers that are totally unproven. If we already knew who the customer was, how they would behave, how much they would pay, and how to reach them, this wouldn’t be a disruptive innovation. The solution is to change our focus from outputs to inputs. If it costs $0.10

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

www.subelsky.com

FEBRUARY 25, 2010

Im still able to surprise people who have worked with me for awhile with how quickly I can turn their feature ideas into something they can play with and show customers. For continuous integration, like many Rails shops, we use CruiseControl.rb - its easy to install and customize, but I dont think people are especially enamored of it.

Lean 41

Lean Baltimore Ruby Maryland 41