Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: The trade-off, though, is a more structured presentation format.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. As usual, Id like to post the slides and then offer some additional commentary.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. Heres their description of the event: The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. Bring it on!

Lean 60

Lean Austin San Francisco Continuous Deployment 60

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. For example, take the lean dictum of working in small batches.

Product Development 153

Product Development Developer San Francisco Product 153

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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The Lean Startup Intensive is tomorrow at Web 2.0. Small is beautiful.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. The Lean Startup Intensive is tomorrow at Web 2.0. Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? Are we going too fast?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. Id like to point out something else about the example above.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 7, 2008

We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. Seems like a fairly low-cost method of gauging customer interest for a would-be product. The Lean Startup Intensive is tomorrow at Web 2.0.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. Chris and I had the opportunity to present on our approach this past spring at the MySQL Conference. Labels: agile , continuous deployment 1 comments: timothyfitz said.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

OCTOBER 5, 2009

Or, if it really was prevented, what was the opportunity cost of choosing to prevent it ahead of time? And in most situations, there is significant cost involved in negotiating over the right estimates to plug in. I have been present for these kinds of negotiations many times in my career. How upset will those customers be?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. But lean startups cant afford to be satisfied with just that definition, because there are situations where working code is itself a form of waste. Expo SF (May. for Harvard Business Revie.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 2, 2008

It costs not just the time of the actual meeting, but the time getting there and back, and the time preparing for it beforehand and thinking about it afterward. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May. for Harvard Business Revie.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 30, 2008

Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Massive proprietary databases?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The cost will be felt in jobs -- thousands of new jobs that could have been created here, but werent. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

MARCH 29, 2010

Traveling the past year, I have heard loud and clear that its time for the Lean Startup movement to enter its next phase. Heres a tiny sample: "Case studies, case studies, case studies presented by real people. Ive asked each presenter not to pull any punches and to, whenever possible, share real data: what worked, what didnt.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

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. A crisis is sometimes needed to force that reexamination.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. The Lean Startup Intensive is tomorrow at Web 2.0.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

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.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. The lean startup focuses on situations where we have both an unknown problem and an unknown solution. The Lean Startup at Web 2.0

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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 Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. As with many lean startup practices, its getting started thats the hard part. Expo SF (May.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

APRIL 18, 2010

Lessons Learned by Eric Ries Sunday, April 18, 2010 Four myths about the Lean Startup Myth: Lean means cheap. Lean startups try to spend as little money as possible. 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

Its obvious that can lower your development costs, but I think its even more important that it can reduce your time to market. Im definitely curious about your thoughts on how to present the company right. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

JUNE 17, 2010

And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 5, 2010

Lessons Learned by Eric Ries Tuesday, October 5, 2010 The Lean Startup Bundle People often ask me if they can buy "Lean Startup in a box" from me. People want to get started with Lean Startup but arent exactly how. Its called the " The Lean Startup Bundle " and it is available this week only. Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? This model of joint accountability is at the heart of the lean startup, and is just as applicable to venture-backed, bootstrapped, and enterprise startups. The Lean Startup Intensive is tomorrow at Web 2.0. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JANUARY 12, 2009

Direct mapping of outputs to inputs : URLs to files, code and presentation intermixing. PHP encourages one of the worst programming heresies of all: intermixing code and presentation logic in a giant mish-mash. Yes, Python developers DO tend to cost more. Memory-resident code made it slightly slower to iterate on scripts.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

OCTOBER 20, 2008

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Thats why we need continuous integration and test-driven development. Any advise on how the decision to rewrite may change for lean startups?

Software Review 164

Software Review Engineer Management Technical Review 164

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. At present would represent the $30,000 revenue company. The Lean Startup Intensive is tomorrow at Web 2.0. April 15, 2009 9:20 PM Shaun said.

Customer 167

Customer San Francisco Lean Hockey Stick 167