Architecture Continuous Deployment Engineer Software 
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. Can this methodology be used for startups that are not exclusively about software?
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. This engineering manager is a smart guy, and very experienced.
Startup Lessons Learned
NOVEMBER 14, 2013
Jez, who is a principal at ThoughtWorks, co-author of the Jolt Award-winning Continuous Delivery and the forthcoming Lean Enterprise , will address one of the thorniest areas of Lean Startup: how to reduce cycle times by constantly releasing updated software to customers and quickly responding to their feedback.
Startup Lessons Learned
AUGUST 8, 2009
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Heres my take.
Expert insights. Personalized for you.
167 
Let's personalize your content