Agile Cofounder Continuous Deployment 
Startup Lessons Learned
JUNE 15, 2009
Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
DECEMBER 28, 2009
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
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. Heck, thats what it says right there in the agile manifesto.
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. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.
Startup Lessons Learned
FEBRUARY 16, 2009
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.
Startup Lessons Learned
NOVEMBER 13, 2008
Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.
Expert insights. Personalized for you.
167 
Let's personalize your content