Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Im also excited to share two long-form reviews from actual attendees. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 3, 2009

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. Case Study: Continuous deployment makes releases n. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 18, 2008

From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). After all, someone else’s view will be averaged in, too.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Startups are the lifeblood of our economy.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

JANUARY 12, 2009

Some of them are probably still cursing my name, because - lets face it - PHP can be pretty painful. Almost every PHP-based website is burdened with ugly URLs that contain the name of the file that implements each page. The IMVU downloadable client, just to name one example, is written primarily in python.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I think this is one of your better posts this year, because you are addressing a risk that you face AFTER some early success, when your guard is down and you are more inclined to believe that you know what you are doing and therefore do not need to be as diligent at framing your hypotheses and how you plan to verify them. I apologize ).

Community 158

Community Management Lean Software Review 158