Remove Continuous Deployment Remove Cost Remove Hosting Remove Revenue
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

Lessons Learned: The lean startup

Startup Lessons Learned

My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. Case Study: Continuous deployment makes releases n. Whether they also lead to dramatically higher returns for investors is a question Im looking forward to studying.

Lean 168
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: 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. When operating with continuous deployment, its almost impossible to have integration conflicts. Case Study: Continuous deployment makes releases n. Small is beautiful.

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.

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. More on that in a moment.

Customer 167
article thumbnail

It's a startup, not a spreadsheet

Startup Lessons Learned

And so the spreadsheet is built with conservative assumptions, including a final revenue target. No matter how low we make the revenue projections for this new product, it’s extremely unlikely that they are achievable. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

There are three fundamental situations that change what your company needs to do: creating a new market (the original Palm), bringing a new product to an existing market (Handspring), and resegmenting an existing market (niche, like In-n-Out Burger; or low-cost, like Southwest Airlines). Case Study: Continuous deployment makes releases n.