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. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started.

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. I suddenly lose my ability to judge if our marketing programs are being effective. So the product development team was busy creating lots of split-tests for lots of hypotheses. Use pilot programs.

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

TDD plus continuous integration works as a natural feedback loop: if the team is working "too fast" to produce quality code reliably, tests fail, which requires the team to slow down and fix them. Use pair programming and collective code ownership. Pair programming is the most radical, but also the most helpful.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94