Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. How dare you! =) November 4, 2008 10:58 PM IMVU said. Agile software development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Since we were only paying per click, it didnt cost us anything to cast a wide net. Case Study: Continuous deployment makes releases n.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

FEBRUARY 11, 2009

Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Its obvious that can lower your development costs, but I think its even more important that it can reduce your time to market. Case Study: Continuous deployment makes releases n.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

APRIL 26, 2009

Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments. When you participate in an open community like these you take advantage of tremendous amounts of effort.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

MAY 27, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, Case Study: Continuous deployment makes releases n.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Not crossing the chasm What does life feel like in the chasm ? Or your cost of customer acquisition just magically floats up to match your customer lifetime value. Case Study: Continuous deployment makes releases n. How do you plan for it?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 8, 2009

That is just currently a full personal money sucking process, as you're taxed on income and have no business breaks yet, besides supplies, the majority of costs to start up a business have no tax advantages to creating a start up. Case Study: Continuous deployment makes releases n. September 8, 2009 6:25 PM dbsaid.

DC 90

DC Washington San Francisco SBIR 90

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. Although it costs to pay down the principal, we gain by reduced interest payments in the future. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JANUARY 4, 2009

This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. At the cost of a little extra indirection, you can organize your code around a series of long-lived objects, each of whom communicates with the other objects in simple, easy-to-understand ways.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 Getting started with split-testing One of the startup founders I work with asked me a smart question recently, and I thought Id share it. A few days ago I open-sourced a framework for split-testing, A/B testing or continous optimization.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

Startup Lessons Learned

MAY 22, 2009

If your startup is growing (or aspires to grow), then the costs of a mistake are always going up. Since the cost of failure is monotonically increasing, it actually makes sense to fail sooner, not later. This is the thinking that allowed us to overcome our fear of continuous deployment at IMVU.

Lean 76

Lean San Francisco Continuous Deployment Startup 76