Startup Lessons Learned

JULY 5, 2010

The Entrepreneur’s Guide is an easy read. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. Many “airport business books&# urge entrepreneurs to never give in. I think theyve succeeded. In fact, they probably will.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. Every time an engineer checks in code, they are batching up a certain amount of work. When operating with continuous deployment, its almost impossible to have integration conflicts.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

APRIL 4, 2010

To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") What are the characteristics of a lean startup?

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). November 25, 2009 9:54 AM Danny Wong said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. This time, Im discussing the challenge for corporate CFOs and VCs alike in holding entrepreneurs accountable. Read the rest here.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

AUGUST 26, 2009

But theres no denying the level of support for entrepreneurs that we enjoy. They take common stock, not preferred, a fact that the entrepreneurs mentioned to me many times. And every year, it looks as if one or two entrepreneurs from the program decide to stay. Some of the mentors are based in Boulder, but many are not.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha. for Harvard Business Revie.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. for Harvard Business Revie.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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. Continuous learning -> Continuous feedback!

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 10, 2008

If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Daily builds are giving way to true continuous integration, in which every checkin to the source control system is automatically run against the full battery of automated tests. Do you make daily builds?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The engineering team would then build that feature, mimicking the UI as close as they could using the current primitives supported by the system. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JUNE 2, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: five whys root cause analysis The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MARCH 25, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 5, 2008

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MARCH 29, 2010

Weve got a new scholarship program up and running. The focus is on case studies and real entrepreneurs. When I was a practicing entrepreneur, startup events usually made me crazy. Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

MARCH 16, 2009

Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System. Last year, I found myself back in Steve Blanks class at Haas, this time trying to teach the students about what its like running engineering alongside customer development. for Harvard Business Revie.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 2, 2008

Giving rise to three verbs: Implement (programming!) The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha. where we turn ideas into code the best way possible.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

AUGUST 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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? for Harvard Business Revie.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

JANUARY 7, 2010

My explicit goal in working with HBR is to foster a dialog between entrepreneurs and more traditional general managers. As an entrepreneur, I often saw the best practices of general management fail startups. My explicit goal in working with HBR is to foster a dialog between entrepreneurs and more traditional general managers.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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? for Harvard Business Revie.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Firmness: A program should not have any bugs that inhibit its function. Great engineers see it and smile.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 12, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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? for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

FEBRUARY 9, 2009

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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? for Harvard Business Revie.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? After an hour with a team talking dirty about deployment, youll know. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 4, 2008

My path to lean startups began with Kent Beck and extreme programming. The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org. Tech entrepreneurs rapidly discover that programming is meaningless when not anchored to customers’ needs.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

APRIL 29, 2013

The Lean Startup Conference is an event by entrepreneurs for entrepreneurs—except that our definition of “entrepreneur” may be different from the one you have in mind. So what kinds of talks do all these entrepreneurs find valuable? Really, it''s a place to learn and connect with other entrepreneurs.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Case Study: Continuous deployment makes releases n.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 12, 2010

For the many entrepreneurs that send me cold emails asking for me to review a business plan or answer a strategic dilemma: Im much more likely to answer if youve already tried getting an answer on the mailing list. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? for Harvard Business Revie.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

NOVEMBER 7, 2008

Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha. for Harvard Business Revie.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 30, 2009

A discounted price is available for early stage entrepreneurs and students. Building on this, I’ve recently become fascinated with the notion of continuous deployment , a concept that has been popularized by Eric Ries and others. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 28, 2008

Most of the times I have seen pitches fail, it is not because they are poorly written, or that the entrepreneur lacks passion. whos on the engineering team? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

JULY 9, 2010

What motivates all these entrepreneurs? What do entrepreneurs look like? And second, what attributes make someone likely to be a successful entrepreneur? The difficulty lies in this paradox: many of the attributes that increase the likelihood of becoming an entrepreneur actually impede startup success.

San Francisco 161

San Francisco Management Founder Lean 161