Startup Lessons Learned

OCTOBER 26, 2009

Customers kept demanding that we add this or that IM feature, and we were routinely refusing. We were afraid that this was just the tip of the iceberg, and that once we “gave in&# to these five demands there would be five more, ad infinitum. Case Study: Continuous deployment makes releases n. Expo SF (May.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. Case Study: Continuous deployment makes releases n. Gatekeepers are overloaded. Expo SF (May.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 4, 2010

Many journalists and conference organizers attempt to fill this demand by giving successful entrepreneurs the opportunity to tell their stories: in magazines, on blogs, and on stage. It sells newspapers and magazines. But if you’re attending a conference or reading a magazine, you aren’t bound by those rules.

San Francisco 167

San Francisco Lean PR Metrics 167

Startup Lessons Learned

OCTOBER 5, 2009

In other words, a principled way to combine agility with stability. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. In other words, a principled way to combine agility with stability.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133