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. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 19, 2009

Consider the method used by TPGTEX Label Solutions, a Houston -based software company that specializes in bar codes and labels for manufacturers and chemical companies. It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We Why didn’t we learn more?

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JULY 2, 2009

Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. It's so old and so buggy that it's a real pain to ship 3D software on it. Luckily, in most prevention situations, even the first few steps in prevention can pay time-savings dividends quickly.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. If thats not a team-wide phenomenon, then its still a form of waste, because everyone has to learn every lesson before it starts paying dividends. Case Study: Continuous deployment makes releases n. Heres a company I met with recently.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79