Startup Lessons Learned

FEBRUARY 7, 2013

Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile. Therefore, we needed a new management toolkit designed explicitly for iteration, scientific learning, and rapid experimentation.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

JUNE 8, 2009

I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. So the product development team was busy creating lots of split-tests for lots of hypotheses. Yet it had one huge advantage. Expo SF (May.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JANUARY 19, 2009

One, which is described in great detail in the Mythical Man-Month (in finding that link, I discovered that today is coincidentally the exact 11th anniversary of my first purchasing that book: Jan 19, 1998), is that as you add people to a team or project, there is an increase in communications overhead that makes everyone slightly less productive.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Steve Blank

NOVEMBER 1, 2010

But nine months after the first call was made in 1998, Iridium was in Chapter 11 bankruptcy. Second, since it knew the solution, it went into a 8 -year Waterfall engineering development process. Waterfall development is a sequential way to develop a product (requirements, design, implementation, verification – ship.)

Business Plan 335

Business Plan Customer Business Model Customer Development 335