Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 10, 2008

At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. Plus, as product development teams in lean startups become adept at learning-and-discovery (as opposed to just executing to spec), its clear that some bugs shouldnt be fixed. Do you have a spec?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 22, 2008

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. The lean manufacturing guys call this visual control and its very powerful. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

David Teten

OCTOBER 1, 2015

These are particularly relevant to first-time founders, since the learnings they go through often inhibit them from successfully launching a company. When the value of the studio’s participation is effectively a commodity (like office space, engineering, capital, etc), the equation flips and should be to the advantage of the founders.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60