Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Case Study: Continuous deployment makes releases n.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 22, 2008

Just dump the results in a database as you get them, and let your reports calculate scores in real-time. Our response time to the crisis was much too slow, and as part of the post-mortem analysis of why , I took a look at the various metrics that all took a precipitous turn for the worse during that summer.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

NOVEMBER 5, 2008

Observe At the end of each day, wed laboriously enter data, updating the campaigns voter database with information about every voter contact we accomplished that day. That voter database was accessible to staff at every level of the campaign. Case Study: Continuous deployment makes releases n.

Campaign 84

Campaign San Francisco Lean Agile 84