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. Heck, thats what it says right there in the agile manifesto.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. Eric, I landed upon your blog when I was searching for the path to CTO a couple of months back and I have been a frequent to the site since then. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. The book takes its name from Steves theory of the four stages of growth any startup goes through. Phases of product & company growth.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 15, 2008

If she is, return the name of the hypothesis she was exposed to before. Return the name of the hypothesis chosen or assigned. From the point of view of the caller of the function, they just pass in the name of the experiment and its various hypotheses. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Great post! Expo SF (May.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Particularly the Continuous Deployment and Split testing posts. Case Study: Continuous deployment makes releases n. The blog is fantastic as well. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

AUGUST 3, 2009

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. Case Study: Continuous deployment makes releases n. Thank you.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Case Study: Continuous deployment makes releases n. Expo SF (May.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. Case Study: Continuous deployment makes releases n. I like this term.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 7, 2008

On the iPhone, it seems that two are driving most of the installs: the "newest apps" RSS feed (which may be combined with PR) and a primitive form of SEO, when people search the App Store for a specific kind of app. If necessary, consider doing this under a different brand name than the one you are wedded to using. Expo SF (May.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Google was not the first search engine, but it's the one that succeeded.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. I'm a technology hacker in exactly the searching situation you mention; having just come to the end of the setup of my current venture and looking for the next challenge.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). However, a commitment to quality alone is not enough.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. Not many customers ever browse the app directory or search for specific apps - they dont have to, they find out about apps by being invited by a friend. And I dont see much searching for apps going on. And what distinguishes a good app?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Instead of telling people to look for *the* root cause, I have them search for *a* or *some* root causes. Case Study: Continuous deployment makes releases n. Why wasn’t it immediately obvious how to fix the problem?

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 13, 2008

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Case Study: Continuous deployment makes releases n. Combining agile development with customer developm. See if their answer is about tactics or strategy.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. This team had been working for many months in a standard agile configuration: a disciplined engineering team taking direction from a product owner who would prioritize the features they should work on. What a waste. And who can blame them?

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 24, 2009

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Combining agile development with customer developm.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. 1 comments: Josh Moore said. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. Case Study: Continuous deployment makes releases n. The value of the attention that the media company collects determines how profitable it is.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

APRIL 7, 2010

I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 13, 2010

Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

OCTOBER 23, 2009

Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Case Study: Continuous deployment makes releases n. Startups are the lifeblood of our economy.

San Francisco 121

San Francisco Indiana Lean Startup 121