Continuous Deployment Distribution Product Development 
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 27, 2010
One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. We already know who to distribute the product to (or else why would we care what they think?).
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
Startup Lessons Learned
APRIL 26, 2009
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Leveraged distribution channels.
Startup Lessons Learned
SEPTEMBER 18, 2008
Lessons Learned by Eric Ries Thursday, September 18, 2008 How to get distribution advantage on the iPhone I have had the opportunity to meet a lot of iPhone-related companies lately. There are other models, in other distribution channels. On Facebook, viral distribution has proved decisive. I havent found any yet.
Startup Lessons Learned
JULY 28, 2010
If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. They were interested in the tools and new distribution medium kaChing provided. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here.
Startup Lessons Learned
SEPTEMBER 30, 2008
Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.
Expert insights. Personalized for you.
123 
Let's personalize your content