Startup Lessons Learned
APRIL 26, 2009
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. April 27, 2009 10:54 AM DSarathy said.
Startup Lessons Learned
SEPTEMBER 15, 2008
In recent years, weve also got great new options all up and down the stack, in particular things like Amazon EC2 and RightScale (none of which would be possible without the free software movement). The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. February 21, 2009 12:10 AM Harold Fowler said. Interesting post.
Startup Lessons Learned
APRIL 4, 2010
Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
Startup Lessons Learned
MARCH 25, 2010
This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Take a look and let me know what you think.
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.
88 
Let's personalize your content