Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. 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. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Labels: product development 15comments: mukund said. But a good day looked like this.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

MARCH 4, 2014

These groups are adapting or adopting the practices of startups and accelerators – disruption and innovation rather than direct competition, customer development versus more product features, agility and speed versus lowest cost. Strategy Maps. StageGate Process. This is a big idea. Lessons Learned.

IRR 335

IRR Startup Business Model Agile 335

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. A Fundraising Survival Guide [link] Raising money has a mysterious capacity to suck up all your attention. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. 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.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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, February 9, 2009 7:45 PM Joseph Flahiff said. Check out what I am doing at.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. Expo SF (May. Amazon PostRank

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

SEPTEMBER 8, 2008

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. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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, Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 15, 2009

In practice, how developers respond to this dilemma is determined by their incentives, which are driven by the culture of their team. Who will ultimately bear the cost of their mistakes? One of the distinctions that has helped at the executive level is to stress that you're reducing the COST of failure, rather then its PROBABILITY.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Or your cost of customer acquisition just magically floats up to match your customer lifetime value. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Although there is cost and overhead associated with continuous deployment, the benefits are immense. Danger, Will Robinson.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

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. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. I’ve met a lot of gatekeepers in the past few months. Is that a lot? Is that good? ideas (e.g.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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? Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 18, 2010

Truth: The Lean Startup method is not about cost, it is about speed. Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

MARCH 29, 2010

Of course, readers of this blog know that the lean in "lean startup" doesnt refer to cost, but - rather - to Lean Thinking. Of course, readers of this blog know that the lean in "lean startup" doesnt refer to cost, but - rather - to Lean Thinking. 699 buys you months of server infrastructure." I think this is a fair question.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

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

It is the ultimate product development get-started guide to Lean Startup. But," you are sure to ask, "how much will all this bundling cost me?" It is the ultimate product development get-started guide to Lean Startup. But," you are sure to ask, "how much will all this bundling cost me?" Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

MARCH 23, 2009

I started writing and teaching about shipping imperfect products a few years ago but this is a far better, practical and more powerful presentation. There is a lot to be said about the opportunity cost of perfection, iterative evolution and the difference between shipping a lemon and shipping a band aid. Expo SF (May. Amazon PostRank

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

MAY 22, 2009

Loved it and great speaker, but disagree with portrayal of agile only dealing with known problems #leanstartup Im really interested in perspectives on this point. For example, the agile practice of an in-house customer or product owner that can make authoritative prioritization decisions seems like it doesnt translate very well to startups.

Lean 76

Lean San Francisco Continuous Deployment Startup 76

Startup Lessons Learned

AUGUST 8, 2009

Because of the cost and intensity of this program, it is designed for startups with significant venture backing or who have reached profitability. I continue to work on additional programs and products for bootstrapped and angel-backed startups, as well as for enterprise and future entrepreneurs. . Sounds like an amazing workshop.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

JANUARY 27, 2009

Here the key is for your free customers to get value from the site that is greater than the costs they perceive by the fact that youre selling access to them. When the goals not clear, I think you wind up with situations that are essentially value-destroying, where free users are actually driving up costs. Expo SF (May.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

SEPTEMBER 19, 2009

In my presentation this morning, I emphasized three key areas: reducing the personal cost of failure for entrepreneurs, innovation-friendly legal reforms, and access to the digital means of production (slides from my White House presentation are available at the end of this post). Expo SF (May. Amazon PostRank

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

AUGUST 18, 2009

Expo NYC , immediately followed by an event or two in Boston - details to be announced. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? I really value both.

San Francisco 60

San Francisco DC Sweden Continuous Deployment 60

Startup Lessons Learned

OCTOBER 19, 2009

"We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002. Development time is typically no more than two to three weeks, and it generally takes just a few orders to cover development costs. Read the rest. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

JANUARY 6, 2009

The first event is January 21, and is being put on by Dealmaker Media as part of their Strategy Series events: In the Trenches: Cutting Costs in a Tight Economy. There are no canned presentations, so you can come set the agenda. The format is Q&A around a conference table with four "speakers" and a moderator. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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. Getting started with split-testing and the one-line split-test.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

FEBRUARY 10, 2009

Ship more infrequently While this may decrease downtime (things break and you roll back), the cost on development time from work and rework will be large, and mistakes will continue to slip through. That leads to a seemingly-obvious question: what is progress in software development? If a feature worked, wed keep it. We made it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JUNE 12, 2009

So far, we have limited registration at the workshops to people who can afford the admittedly high cost of entry. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

Lean 60

Lean Programming San Francisco Continuous Deployment 60