Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

David Teten

OCTOBER 1, 2015

What are the terms of their relationship with the founder? How would one set up such a startup to eventually raise capital from outside VCs, who will be wary of ‘dead equity’ (i.e., If we believe in founders enough, we should believe in their potential more than what they could be paying us to build the product.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Nice write-up.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 9, 2009

MarkH : Key takeaways from Erics great talk #w2e #leanstartup 1) "building a culture to learn " @ericries Marks point is the one that seems to have had the biggest impact from the talk as a whole: that startups should be built to learn. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In a startup, we should take full advantage of our options, even if they feel dirty or riddled with technical debt. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

adam.heroku.com

MAY 18, 2012

Founders and early employees tend to be very self-directed so the need for management is nearly non-existent. Some startups, on reaching this stage, declare “we’ve got to grow up and act like a real company now” and immediately try to switch to heavy-handed tactics. Stage 2: The first hires.

Developer 92

Developer Database Architecture API 92

Startup Lessons Learned

NOVEMBER 18, 2008

Its even more critical in lean startups when they need to manage growth. I believe its important that product teams be cross-functional, no matter what other job function the product champion does. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60