Architecture Continuous Deployment Cost Product 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
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
Startup Lessons Learned
APRIL 26, 2009
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.
Startup Lessons Learned
NOVEMBER 14, 2013
By the end of his workshop, you will know how to apply innovation accounting to truly track the progress of your product. We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. Thus we reduce the risk of deployments. How do you address that?
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
OCTOBER 5, 2009
It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?
Expert insights. Personalized for you.
167 
Let's personalize your content