Remove Continuous Deployment Remove Engineer Remove Entrepreneur
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

Case Study: Continuous deployment makes releases non-events

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

article thumbnail

Continuous deployment with downloads

Startup Lessons Learned

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. Thanks for the comments.

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. 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.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU. One last comment.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") 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.

Lean 168