Agile Algorithm Continuous Deployment Startup 
Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.
Startup Lessons Learned
JULY 29, 2009
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.
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 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?
Startup Lessons Learned
NOVEMBER 29, 2008
The six key attributes spell ABCDEF: Agility. By far the most important thing you want to hire for in a startup is the ability to handle the unexpected. Those people also tend to go crazy in a startup. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.
Startup Lessons Learned
NOVEMBER 13, 2008
Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.
Startup Lessons Learned
JANUARY 4, 2009
Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. More common is to use a one-way hashing algorithm to map the data to be accessed to one of the shards that store it. But startups rarely have either luxury. to store it.
Startup Lessons Learned
APRIL 7, 2010
Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. When people (ok, engineers) who have been trained in this model enter most startups, they quickly get confused. In Google’s case, often in the millions of people.
Expert insights. Personalized for you.
111 
Let's personalize your content