Continuous Deployment Naming Product Development 
Startup Lessons Learned
FEBRUARY 10, 2009
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JANUARY 18, 2010
Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.
Startup Lessons Learned
AUGUST 3, 2009
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. MVP, despite the name, is not about creating minimal products. There is a distinction between product and offering.
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Case Study: Continuous deployment makes releases n. Interesting post.
Startup Lessons Learned
NOVEMBER 7, 2008
So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.
Startup Lessons Learned
SEPTEMBER 7, 2008
In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.
Expert insights. Personalized for you.
123 
Let's personalize your content