Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. You dont need "war team meetings," and you dont need status reports I even believe in doing launches on a continuous basis (see continuous ship ). Case Study: Continuous deployment makes releases n.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 7, 2008

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. Case Study: Continuous deployment makes releases n.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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

MARCH 16, 2009

And Im thankful that Scrum/Agile doesnt address everything too. :) I think in my original article I mentioned how there is a wide (tho narrowing) gap between the world of product managers and the agile world. William: I actually posted an article about the role of the Product Manager in Scrum. March 31, 2009 12:48 PM PM Hut said.

Agile 111

Agile Customer Development Developer San Francisco 111

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

NOVEMBER 8, 2008

This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. 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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 8, 2009

It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. 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.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JUNE 5, 2009

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. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. And yet their numbers continue to grow, month after month. This is possibly the most insightful startup article Ive read in a while.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

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

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

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

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. Take a look and let me know what you think.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

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

Startup Lessons Learned

FEBRUARY 24, 2009

Some highlights, at least for me: We experienced a great science experiment for the scenario: what would happen if a big company tries to compete with you given complete knowledge about your idea and designs? Ive embedded the audio and slides below, but I recommend you c lick through to the Venture Hacks article if youre interested.

Lean 74

Lean San Francisco Continuous Deployment DC 74

SVPG

JULY 31, 2013

This article is a little bit different, but if you make it to the last paragraph, I''m hoping it will help better explain where I''m coming from. In the spirit of the inspirational This I Believe project, I thought I would share with you the beliefs that underly so much of my writing and teaching. I believe in technology. I could go on.

SCRUM 60

SCRUM Continuous Deployment Agile Lean 60

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

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

OCTOBER 30, 2008

The Entire Video of John Doerr Giving 10 Tips for Start-ups to Avoid the Econalypse Related articles by Zemanta Ten ways to save your company by John Doerr John Doerrs 10 Ways to Stay on Top Ten ways to save your company by John Doerr John Doerr: 10 ways for companies to stay afloat in rough times (MG Siegler/VentureBeat) 1 comments: fnthawar said.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

OCTOBER 19, 2009

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. That’s why entrepreneurship in a lean startup is really a series of MVP’s, each designed to answer a specific question (hypothesis). Read the rest. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

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. Revisiting the Software Design Manifesto (and what.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. Great article as always, Eric. Great article, Eric. I have one comment on style: could you break up your articles with subheadings? It would make article more approachable initially, and easier to scan when I go back to reference it. enjoyed your article.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

Heres the working definition Ive started using: A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. Case Study: Continuous deployment makes releases n. In a future post, Ill attempt to unpack this definition in detail. Take a look and let me know what you think.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

JUNE 22, 2009

I think i must have read this article a few times since you first posted it - mainly as a theoretical excercise. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

APRIL 9, 2009

And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. When people ask about how to reconcile metrics with interaction design, usability testing, or in-person customer interviews, this is the issue they are really talking about. The slides look great.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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

AUGUST 1, 2009

My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Discover whats in customers heads, and tackle problems where design is a differentiator. I really enjoyed this article, my first time reading any of your stuff. Thanks for another great article! Great Post !

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation.

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.) Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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

Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups. You can see the design of the program here. Case Study: Continuous deployment makes releases n. September 8, 2009 6:25 PM dbsaid. conference attendees.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JANUARY 4, 2009

Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. It also doesnt make sense to design your app for scalability from the start, since you may have to create many iterations before you find a version that requires any scalability at all. 21comments: Imran said.

San Francisco 151

San Francisco Architecture Startup Database 151