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.
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. Agile is a tremendous advance in reducing time, money and wasted product development effort – and in having products better match customer needs.
Startup Lessons Learned
APRIL 25, 2011
SLLCONF featured incredible entrepreneurs on stage to put those ideas to rest (watch, for example: Aardvark , Grockit , Dropbox , PBworks ). It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices.
Startup Lessons Learned
MARCH 25, 2010
This is the first post that moves into making specific process recommendations for product development. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. Labels: product development Speed up or slow down? (for Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
FEBRUARY 16, 2009
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.
Startup Lessons Learned
JUNE 2, 2010
One such technique is called Five Whys, which has its origins in the Toyota Production System, and posits that behind every supposedly technical problem is actually a human problem. Read the rest of The Five Whys for Start-Ups. Read the rest of The Five Whys for Start-Ups. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
167 
Let's personalize your content