Architecture Continuous Deployment Customer Development 
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
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.
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
JULY 29, 2009
Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. That’s what Just-in-time Scalability is all about.
Startup Lessons Learned
SEPTEMBER 30, 2008
If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? That means knowing whats written and whats not, what the architecture can and cant support, and how long it would take to build something new. Thats more than just drawing architecture diagrams, though.
Startup Lessons Learned
NOVEMBER 13, 2008
It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
167 
Let's personalize your content