Remove Agile Remove Algorithm Remove Customer Development Remove New York
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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. Enter Jims post.

Agile 111
article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. This is not what I have in mind. Expo SF (May.

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

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. Just as a business incurs some debt to take advantage of a market opportunity developers may incur technical debt to hit an important deadline.

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

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.

article thumbnail

Learning is better than optimization (the local maximum problem)

Startup Lessons Learned

Those of us with a computer science background call it the hill-climbing algorithm. For more on how to figure out which question applies in which context, see Business ecology and the four customer currencies.) And therein lies the most common source of confusion about whether startups should listen to customers.

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

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. Theres no complex algorithm to go wrong, just a simple lookup table. Of course, you could use URL-based sharding to "wrap" a CH algorithm (or any hashing scheme you wanted). Expo SF (May.