2008 Continuous Deployment SCRUM 
Startup Lessons Learned
SEPTEMBER 10, 2008
Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Please leave feedback!)
Startup Lessons Learned
OCTOBER 5, 2008
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Nice write-up.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. September 11, 2008 2:06 PM Editor said. September 15, 2008 9:19 PM James said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.
Startup Lessons Learned
JULY 29, 2009
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. One last thought.
Startup Lessons Learned
APRIL 9, 2009
Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. How to Build a Lean Startup, step-by-step Get started with a detailed guide to three key lean startup techniques: continuous deployment, rapid split-testing, and root cause analysis (five whys).
Startup Lessons Learned
DECEMBER 6, 2008
Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.
Expert insights. Personalized for you.
144 
Let's personalize your content