article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

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.

article thumbnail

Continuous deployment for mission-critical applications

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Tesla and Adobe: Why Continuous Deployment May Mean Continuous Customer Disappointment

Steve Blank

In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. Agile is a tremendous advance in reducing time, money and wasted product development effort – and in having products better match customer needs. They want newer things.

article thumbnail

Hands-on Lessons for Advanced Topics in Entrepreneurship

Startup Lessons Learned

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. LSC: One of the biggest fears people have about a continuous deployment environment is that it introduces more risk to engineering. Thus we reduce the risk of deployments.

article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Labels: five whys root cause analysis , product development 11comments: Peter Severin said.

article thumbnail

Lessons Learned: Validated learning about customers

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? All things being equal, of course, you’d rather have more revenue rather than less. And yet revenue alone is not a sufficient goal.

Customer 167
article thumbnail

Lessons Learned: Continuous deployment and continuous learning

Startup Lessons Learned

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. At IMVU it’s a core part of our culture to ship.