Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors.

Software Review 164

Software Review Engineer Management Technical Review 164