Remove Continuous Deployment Remove Design Remove Marketing Remove Search
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

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.

article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so.

article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

article thumbnail

Refactoring for TDD and interaction design

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The same process works in Interaction Design. Much better is to infer the right toolkit by searching for commonalities among actually-built experiences.

article thumbnail

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Pretty soon, a soul-searching meeting ensues. Pretty soon, a soul-searching meeting ensues. Case Study: Continuous deployment makes releases n.