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
FEBRUARY 10, 2009
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
OnlyOnce
AUGUST 6, 2015
If your organization still does software development through a waterfall process or has separate and distinct development, QA, and IT/Operations teams, I’d say you should run, not walk, to get this book. It just uses storytelling techniques to make its points and give color and examples for more memorable learning.
The Next Web
SEPTEMBER 18, 2012
Wercker : a continuous deployment solution for software developers, hosted in the cloud. If you’re going to the Demo Day in Silicon Valley, these are the startups you’ll be hearing from: Peerby : Peerby enables people to rent goods in their neighborhood and just won over 100,000 euros at the Green Challenge.
Startup Lessons Learned
APRIL 4, 2010
Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.
Feld Thoughts
MARCH 11, 2010
I’ve become a big advocate of true Agile development (partly because of my experience with Rally Software – the leader in Agile software development environments) and – more recently – the notion of trying to get to continuous deployment which has been popularized by Eric Ries.
Startup Lessons Learned
OCTOBER 16, 2013
We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.
Expert insights. Personalized for you.
167 
Let's personalize your content