Startup Lessons Learned
JULY 13, 2009
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.
Startup Lessons Learned
NOVEMBER 12, 2013
Currently at Facebook, Kent has pioneered effective software development, co-authoring the Agile Manifesto , which modernized product development, and writing a slew of books with practical advice for engineering teams. What strategies succeed or fail in altering entrenched patterns?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.
Startup Lessons Learned
AUGUST 3, 2009
I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
Startup Lessons Learned
SEPTEMBER 22, 2008
Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). April 23, 2010 in San Francisco.
Startup Lessons Learned
OCTOBER 5, 2008
But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. April 23, 2010 in San Francisco. This post has been removed by the author. Bring your questions.
Startup Lessons Learned
SEPTEMBER 30, 2008
Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.
Expert insights. Personalized for you.
153 
Let's personalize your content