Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. The batch size is the unit at which work-products move between stages in a development process. Every time an engineer checks in code, they are batching up a certain amount of work.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 8, 2009

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the product development team was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

NOVEMBER 8, 2008

Our goal in product development is to find the minimum feature set required to get early customers. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified. Very well written article. Case Study: Continuous deployment makes releases n.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. When they see a problem with the teams process, why dont they just fix it? Hire a CTO or VP Engineering. As usual, a fantastic article. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94