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. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Massive proprietary databases? Expo SF (May.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good? It didnt work.

Software Review 164

Software Review Engineer Management Technical Review 164

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. Open APIs and data-oriented architecture (aka "web 2.0"). We didnt think wed able to compete with that.

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, The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. 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. The Lean Startup Intensive is tomorrow at Web 2.0. It wouldnt boot. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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. The human tendency to moralize about debt affects engineers, too. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. When we build products, we use a methodology. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 14, 2009

They know how much it costs to bring in a customer and they know how much money they can expect to make on each one. Our cost to acquire a customer on AdWords was only a few cents. In these examples I was selling enterprise software where the vocab matched perfectly. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. Though technology tools and Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

APRIL 18, 2010

Truth: The Lean Startup method is not about cost, it is about speed. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer internet/consumer software companies. Truth: The Lean Startup method is not about cost, it is about speed. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. Because of the cost and intensity of this program, it is designed for startups with significant venture backing or who have reached profitability. The cost is equivalent to an entry-level FTE.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 11, 2009

Why do Citizens of Humanity jeans cost $200 , when physically similar pants can be had for one-tenth the price? Brands are so pervasive that even those people who want to make a statement against it (do you build all your own software from source?) The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

MAY 17, 2009

Last I heard from the venue, there are still some seats available; the ticket cost is only $25 if you register online. 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. You can register online here. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment DC 60

Startup Lessons Learned

OCTOBER 19, 2009

Consider the method used by TPGTEX Label Solutions, a Houston -based software company that specializes in bar codes and labels for manufacturers and chemical companies. It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We Expo SF (May.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

AUGUST 3, 2009

My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Definitely highlights the beauty of the web. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. Most of all, these arguments stemmed from a simple misconception: that the code we had written was an asset, and that it would cost us to throw it away.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 18, 2009

In November, Im doing two events at the Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

San Francisco 60

San Francisco DC Sweden Continuous Deployment 60

Startup Lessons Learned

AUGUST 20, 2009

In order to maximize such opportunities, this generation of entrepreneurs combines extremely low costs with faster cycle times to produce what I call lean startups. [.] How I would frame the topic for business/tech readers: Is Seed,Series A->C funding destined to disappear for software startups? Expo SF (May.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

MARCH 27, 2009

While some cost-cutting measures reduce that number, others increase it. In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Otherwise, cutting costs just leads to going out of business a little slower. What counts as an iteration? Work in small batches.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

OCTOBER 11, 2010

(I am often asked to explain how to apply Lean Startup approaches to domains beyond software. On the other extreme, modern web-based applications face almost no technical risk, and are governed by high market uncertainty. On the extreme opposite end are rapid iteration businesses like software or fashion. And I'm glad we did.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

APRIL 9, 2009

Lessons Learned by Eric Ries Thursday, April 9, 2009 Built to learn Its been an exhilarating ride since the Web 2.0 This is true whether youre selling million-dollar software to huge enterprises or selling fifty-cent virtual clothes to teenagers. The Lean Startup at Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 13, 2008

By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Best of luck, Your Software." (OK, Good stuff.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Remember that the cost of the solutions is proportional to the problem caused. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 1, 2009

Which comes to the second major principle: halt work that leads to more waste, even if it means abandoning sunk costs. If they were an unknown web 2.0 Just because something looks pretty, or feels like a good idea, or has a lot of sunk cost in it, does not mean it should be pursued. Not even if its generating revenue.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 8, 2008

In this post I want to talk about the nuts and bolts of how to integrate continuous integration into your team, and how to use it to create two important feedback loops. First, a word about why continuous integration is so important. I would like the users of my software to test and give their feedback to me. Expo SF (May.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

MARCH 13, 2009

In some businesses, especially in certain industries like traditional enterprise software, you simply cannot bring a new product to market on your own. Slow progress, but has cost less than 150k aud so far. Im just about starting a software company with a very dedicated team. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 168

San Francisco PR Lean Early Stage 168

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. Thirdly, revamp how intellectual property rights are applied to software and code. Expo SF (May.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

Our CTO is the CEO himself, but he lacks the understanding of the new software development processes and the new technologies. In school I was being pounded day and night with anything that has to do with agile software development. The Lean Startup Intensive is tomorrow at Web 2.0. Sure, it seems efficient. Not necessarily.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. Incremental and proportional software complexity.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 23, 2009

In the process, they learned a lot by asking initial prospects to sign a non-binding letter of intent to buy the software. – Eric Ries In April of 2009 my partner and I had an idea for a web app, a B2C platform that we are selling as SaaS [software-as-a-service]. They then tried to shop the app around, and found no takers.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Stick to some kind of absolute-cost rule, like "no one is allowed to spend more time on the refactoring for a given feature than the feature itself, but also no one is allowed to spend zero time refactoring." Heres a company I met with recently.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. Take mod_perl , for example.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 12, 2009

Resegmented market (low cost variety). Heres a situation where you offer to do the job for 1/10th the cost. Here your challenge is to convince that manager that you really can do the job at such low cost. They must be thinking "if its costing people their jobs, it must really work. Maybe I should try that." Expo SF (May.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89