Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 7, 2008

Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Eric, Excellent article about an essential technique for startups. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. Ive linked to your article from mine.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

MARCH 16, 2009

In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Following XP puts you in a good place to start doing continuous improvement. March 31, 2009 12:48 PM PM Hut said.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 29, 2009

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. Eric, Great article - provides context and vocabulary for dialog on a very interesting tension in startups.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JANUARY 2, 2009

The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value. You can read the article to find out why. You can read the article to find out why. Thank you for this excellent article. Thanks for the article. Retention cohort analysis.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

SEPTEMBER 15, 2008

Thanks for writing this article. I saw you speak yesterday at the FB garage and it reminded me of this article. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Great post Eric!

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. An excellent article and responses. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 18, 2008

What led you to become a subscriber, versus just reading an article and leaving like everybody else? (or, In order to convince me, Id to see another link to an article here somewhere that I enjoyed. Read some articles, liked what I saw. Case Study: Continuous deployment makes releases n. How did you hear about it?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. This is possibly the most insightful startup article Ive read in a while. So heres the question that I pose to you - our startup helps software companies develop a scalable revenue engine in the form of software-specific hardware devices.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

NOVEMBER 8, 2008

Very well written article. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I plan to pick up this book though. December 3, 2008 6:42 PM Anonymoussaid. Lots of good usable information.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 8, 2009

Related articles by Zemanta The Sharp End of the Stick (steveblank.com) Validated learning about customers (startuplessonslearned.blogspot.com) 4comments: mike@dataspora.com said. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

MAY 20, 2010

Although the article is a bit me-centric, I think they did a good job capturing the fact that this is more than just the bloggers and writers, but represents a shift in thinking among entrepreneurs all over the world. The article includes comments from Kevin Dewalt and Drew Houston. Case Study: Continuous deployment makes releases n.

Lean 153

Lean San Francisco Arlington Continuous Deployment 153

Startup Lessons Learned

AUGUST 24, 2009

Having read your interesting article on the "Quicksand" we authors must wade through to market our work to the public, I was prompted to quote from it in an article title "Gatekeepers" (title borrowed from you) on my Facebook wall and in my blog as part of my promotion for my upcoming novel, "Marathon.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

MARCH 11, 2010

for Harvard Business Review) In the latest article for my series in HBR, I discuss the problem of how to figure out how much process startups should have. for Harvard Business Review) In the latest article for my series in HBR, I discuss the problem of how to figure out how much process startups should have.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

OCTOBER 21, 2008

Lessons Learned by Eric Ries Tuesday, October 21, 2008 Lean startups vs lean companies Venture Hacks has a great article today on lean startups. I want to take up one of the questions posed in the Hacker News discussion of the article: The question in my mind against most of these efficiency driven programs is simple. Go read it.

Lean 121

Lean San Francisco Continuous Deployment Startup 121

SVPG

OCTOBER 24, 2012

What I'd like to write about in this article is an increasing trend I am seeing towards both continuous delivery and continuous discovery. Continuous Delivery is an increasingly popular notion today. I have written recently about how product teams do product discovery in parallel with product delivery.

SCRUM 63

SCRUM Continuous Deployment Engineer Product 63

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Case Study: Continuous deployment makes releases n. Dont forget to leave a comment.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

OCTOBER 30, 2008

Everyone from the receptionist to engineers is selling. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Reprioritize & rerationalize all R&D. Everybody should be selling.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

FEBRUARY 24, 2009

When wed go into a product planning meeting, often an engineer or product person would have already run a small scale A/B experiment , and so already have some data to go on. Ive embedded the audio and slides below, but I recommend you c lick through to the Venture Hacks article if youre interested. Expo (and a call for he.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. In response to Five Whys that noticed that not all new engineers were reading the list, we expanded it into a new engineer curriculum. We never set out to build a world-class engineering-training process.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 3, 2009

Thanks for the interesting article. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. If you have further thoughts, please leave them as a comment. Cross posting is good.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

JANUARY 27, 2009

Andrew Chen recently did a great article on the economic model underlying freemium (it includes a detailed spreadsheet, too!). Your article disticly illustrates the models in which one can make free work. Case Study: Continuous deployment makes releases n. Pretty good deal, right? I like that concept.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

OCTOBER 19, 2009

Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. This article is part of a trend that has taken me a bit by surprise: the adoption of lean startup techniques outside the traditional domain of high-tech startups.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JUNE 22, 2009

As the CTO/VP Engineering, I was the worst offender. That means that I (and other engineers) were able to participate in the problem team discussions. Such discussions would have been impossible in our execution-oriented engineering team meetings. Case Study: Continuous deployment makes releases n. Context matters.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 20, 2009

This article also appeared on BusinessWeek.com. Read the rest of the article here. Related articles by Zemanta The Promise of the Lean Startup (gigaom.com) Labels: lean startup 11comments: Ravi said. Case Study: Continuous deployment makes releases n. It is a truly fun place to work. Am I getting the mix right?

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

AUGUST 1, 2009

I really enjoyed this article, my first time reading any of your stuff. Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Thanks for another great article! Made me think!

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 13, 2009

Since we hadnt shown him much in the way of progress recently, we actually brought in the article to show off. Great article. We did the same for our company, although your article does an excellent job of identifying a lot of the psychology and "false strategy" that drives many launches. Alan March 13, 2009 2:18 PM alon said.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

MAY 1, 2009

Related articles by Zemanta Continuous deployment in 5 easy steps (4cloudcomputing.blogspot.com) The Lean Startup workshop coming soon (startuplessonslearned.blogspot.com) The Lean Startup Talk From Web 2.0 Case Study: Continuous deployment makes releases n. If youre interested, you can find out more here.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

DECEMBER 8, 2008

Lessons Learned by Eric Ries Monday, December 8, 2008 Continuous integration step-by-step Lets start with the basics: Martin Fowlers original article lays out the mechanics of how to set up a CI server and the essential rules to follow while doing it. Great article. Case Study: Continuous deployment makes releases n.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JULY 9, 2009

You can even see the humiliating evidence of my smug incompetence in this absurd article from 1999.) Google was not the first search engine, but it's the one that succeeded. Case Study: Continuous deployment makes releases n. Could we have built the first college-based social network five years before Facebook ?

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 22, 2010

Vivek Wadhwa and his team continue their excellent work investigating the true nature of entrepreneurship. Their recent article suggests that startups led by women are actually more successful, on average, than those led by men. Vivek Wadhwa and his team continue their excellent work investigating the true nature of entrepreneurship.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

MARCH 24, 2009

Most of the content for my presentation is drawn from my original article on engagement loops , with new diagrams courtsey of my friends at Kontagent and a few new examples. Jesse - my attempt in this article was to simultaneously explain the engagement loop and also to give insight into when it should be used.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 8, 2009

Eric, I wrote up the outline for a government program to promote entrepreneurship I call the "Civilian Innovation Corps" This would be a program supported jointly by government and private investors and would immediately jumpstart the innovation engine in this country. Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90