Continuous Deployment Distribution Download Founder 
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
SEPTEMBER 2, 2008
You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Update: PDF version for "lazy linux users" and others who love freedom.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 4, 2008
It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Is there anywhere I can download the presentation? Try this download link February 16, 2009 9:21 PM Anonymoussaid.
Startup Lessons Learned
AUGUST 24, 2009
One is explaining the world as it used to work: the importance of gatekeepers, the scarcity implied by limited distribution, and the resulting quality bar that the industry is so proud of. Mostly it is the time and expense required to create the means of distribution for that industry. It’s just taking some longer than others.
Startup Lessons Learned
SEPTEMBER 6, 2008
Ive been even more impressed by the various Greasemonkey compilers out there, that let you turn a Greasemonkey script into a full-blown Firefox extension, for easy distribution. Case Study: Continuous deployment makes releases n. Ive made some pretty minor modifications to it, mostly in the way of simple usability changes.
Startup Lessons Learned
SEPTEMBER 15, 2008
I usually use a "funnel report" that looks like this: Control Hypothesis A Hypothesis B Registered 1000 (100%) 1000 (100%) 500 (100%) Downloaded 650 (65%) 750 (75%) 200 (40%) Chatted 350 (35%) 350 (35%) 100 (20%) Purchased 100 (10%) 100 (10%) 25 (5%) In this case, you could run the report for any time period.
Startup Lessons Learned
SEPTEMBER 18, 2008
For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. Could this be done on mouse focus, commenting amounts, answer percentages, download percentages, etc? Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
123 
Let's personalize your content