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.
Steve Blank
JANUARY 6, 2014
In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. But businesses are finding that Continuous Deployment not only changes engineering but has ripple effects on the rest of its business model. They want newer things.
Startup Lessons Learned
NOVEMBER 14, 2013
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.
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Every time an engineer checks in code, they are batching up a certain amount of work. When operating with continuous deployment, its almost impossible to have integration conflicts.
Startup Lessons Learned
SEPTEMBER 15, 2008
See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering.
Startup Lessons Learned
SEPTEMBER 22, 2008
is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
167 
Let's personalize your content