Agile Blog Continuous Deployment Definition 
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
JANUARY 18, 2010
Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 7, 2008
In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. I havent had to work this model under those conditions, so I cant say anything definitive.
Startup Lessons Learned
JULY 9, 2010
And that narrow definition of entrepreneurship doesn’t count all of the managers inside established companies who are effectively engaged in the same process of building an internal startup (see What is a startup? for my more expansive definition). for my more expansive definition). What motivates all these entrepreneurs?
Startup Lessons Learned
AUGUST 26, 2009
Im always excited to see how these ideas are expressed by entrepreneurs in their own words: petewarden : Another blog post, this one on the @ericries Lean Startup Workshop I attended: [link] #leanstartup tmarkiewicz : Notes from the Lean Startup Dinner with @ericries [link] #leanstartup And I can never resist sharing some positive feedback.
Startup Lessons Learned
SEPTEMBER 22, 2008
Examples of this are well-known, and (in my definition) include any product that causes new customers to sign up as a necessary side-effect of existing customers normal usage: Facebook, Myspace, AIM/ICQ, Hotmail, Paypal. Case Study: Continuous deployment makes releases n. Expo SF (May.
Startup Lessons Learned
SEPTEMBER 30, 2008
We lack a consistent and clear definition of the job. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? And what about if deployment takes forever? I would love to see some blog posts on any experiences you have had with set-based design.
Expert insights. Personalized for you.
167 
Let's personalize your content