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.
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.
Startup Lessons Learned
JULY 9, 2010
And that narrow definition of entrepreneurship doesn’t count all of the managers inside established companies who are effectively engaged in the same process of building an internal startup (see What is a startup? for my more expansive definition). for my more expansive definition). What motivates all these entrepreneurs?
Startup Lessons Learned
JULY 29, 2009
Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.
Startup Lessons Learned
SEPTEMBER 30, 2008
We lack a consistent and clear definition of the job. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? With multiple people trying to work to the same standard, we had to be a lot crisper in our definitions. to those stereotypes, but its not easy.
Startup Lessons Learned
AUGUST 26, 2009
Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. Articulate, inspirational.
Expert insights. Personalized for you.
167 
Let's personalize your content