Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. In teams that have a business culture, the MBAs pick time.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. A "startup within the startup" feeling is a good thing.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 8, 2009

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. That’s what most startup decisions are like. Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

OCTOBER 16, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. One good example is the way in which we''ve adjusted the length of different phases of our agile sprints.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. By far the most important thing you want to hire for in a startup is the ability to handle the unexpected.

San Francisco 146

San Francisco Lean Agile Java 146

Steve Blank

JANUARY 21, 2010

The startup founder who gets fired just as his/her company is growing into large company could be a cliché – if it wasn’t so true – and painful. Scalable Startups at Adolescence. In our previous post we posited that Scalable Startups are designed to become large companies. Let’s take a look at why. What’s Next.

Agile 120

Agile Development Team Review Leadership Merger 120

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

This is Part 2 of the series: 5 lessons from 150 startup pitches.??? About twenty people on Answers OnStartups have asked this question in one form or another: When I meet an angel investor, he may ask: "What if a big company copies your idea and develops the same website as yours after your website goes public?".

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

DECEMBER 7, 2008

Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy. When a startup encounters difficult technical problems, this is the guy you want solving them. I would characterize them as intolerant but not arrogant.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94