Remove Continuous Deployment Remove Demand Remove Presentation Remove Technical Review
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

Lessons Learned: Continuous deployment and continuous learning

Startup Lessons Learned

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. Code reviews and pairing Great practices.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Embrace technical debt

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Technical debt works the same way, and has the same perils. I won’t pretend that there aren’t teams that take on technical debt for bad reasons.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

What does your Chief Technology Officer do all day? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim." And what about if deployment takes forever?

CTO 168
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. We didnt even practice TDD across our whole team.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

article thumbnail

Minimum Viable Product: a guide

Startup Lessons Learned

Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Iterate quickly to uncover true market demands. Your presentation was something that I needed right now.