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.

Agile 111

Agile Customer Development Developer San Francisco 111

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!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

APRIL 9, 2009

However, for those who werent able to get in (or are real gluttons for punishment), I will be speaking the night before at a free event hosted by The Vancouver Ruby/Rails/Merb Meetup Group. Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. Eric, Great article - provides context and vocabulary for dialog on a very interesting tension in startups. Excellent article.

Technical Review 168

Technical Review Software Review San Francisco Lean 168