Startup Lessons Learned

SEPTEMBER 12, 2013

And the urgency stems not from an agile competitor, a first-mover market, or a power-law distribution of reward, but rather from the need to achieve enough velocity to overcome the tremendous gravitational pull of business-as-usual. Further, my products are actually processes. of our minimum viable product.

Lean 162

Lean Startup Ratchet New York City 162

Startup Lessons Learned

MAY 7, 2009

They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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. The "just fix it" mentality is counter-productive here. At the end of the day, the product development team of a startup (large or small) is a service organization.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Steve Blank

JUNE 18, 2020

If negotiations fail, China may respond and escalate, via one of many agile strategic responses short of war, perhaps succeeding in coercing the foundry to stop making chips for American companies – turning the tables on the United States. Short of war, there would be no obvious way to get those foundries back.

Taiwan 436

Taiwan China United States Arizona 436