2008 Agile 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 7, 2013
As we head into 2013, it's a good time to reflect on how far the Lean Startup movement has come: When I first started blogging in August of 2008, I had no idea what to expect. We stand on the shoulders of giants: customer development, the theory of disruptive innovation, the technology life-cycle adoption theory, and agile 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. Heck, thats what it says right there in the agile manifesto.
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. By shipping software early, you give them continuous feedback about how it well its working.
Startup Lessons Learned
NOVEMBER 13, 2008
Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. November 13, 2008 8:59 PM eisrael said. November 14, 2008 3:19 AM Hitchens said. Good stuff.
Expert insights. Personalized for you.
167 
Let's personalize your content