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.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant. I remember one such meeting vividly. So they react in two ways.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Most of all, I wanted to say a huge thank you to all of you: readers, entrepreneurs, agents of change.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JANUARY 7, 2010

for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. My explicit goal in working with HBR is to foster a dialog between entrepreneurs and more traditional general managers. I think we have a lot to learn from each other.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 12, 2010

I continue to believe that the explosion of interest in the lean startup has very little to do with me. Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. You can follow some of that debate here and here ; I continue to believe that this idea is correct.

Software Review 87

Software Review Design Software San Francisco 87

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. Code reviews and pairing Great practices.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. And do your customer development.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

FEBRUARY 22, 2009

Heres what I do know: The future strength of our economy depends on its ability to create, support, and sustain entrepreneurs. (If If you are somehow not convinced of this point, Ill let Fareed Zakaria explain ) We know who the next generation of entrepreneurs are going to be. They are in school, right now, all across this country.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. What is customer development?

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. Case Study: Continuous deployment makes releases n.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

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

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I have a lot of good news to report on this front. For now, Id like to ask a favor.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

crowdSPRING Blog

DECEMBER 8, 2011

Design for Continuous Deployment – [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template tco use today) – [link]. A good culture avoids these dangers: Eight Dangers of Collaboration – [link]. Don’t Be A Free User – [link]. Cheap Willl Be Smart.

Social Media 94

Social Media Small Business Design Media 94

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. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. So-and-so made a mistake why did his mistake get checked in?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JULY 2, 2009

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

You refer to an anonymous Valley-based MMORPG that consumed years and tens of millions in development, but got little commercial traction. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Case Study: Continuous deployment makes releases n. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

AUGUST 8, 2012

For new speakers, we’ll provide hands-on help developing presentations, plus speaker training. A few notes: * Although it's impossible to review a video blind (your speaking skill is part of what's being evaluated), we promise to review the written part of your application blind. So we hope you'll consider applying anyway.

Lean 164

Lean Houston Continuous Deployment Technical Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Over time, such teams either explode due to irreconcilable differences or dramatically slow down.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. And I’ve seen companies fail the other way – the so-called Friendster effect: having a high-profile technical failure just when customer adoption is going wild.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 18, 2008

From a technical point of view, its amazing. Even with only a few months of development, third parties have crammed every single category in the store full of apps. All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 18, 2013

So we’ve added an extra day and expanded into two larger venues--giving us the chance to offer hands-on breakout sessions, increase your chances of meeting fellow entrepreneurs with events that let you share ideas and learn together, and create active mentoring opportunities with real experts. So we hope you''ll consider applying anyway.

Lean 167

Lean San Francisco Startup Continuous Deployment 167

Startup Lessons Learned

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Case Study: Continuous deployment makes releases n.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

JANUARY 12, 2009

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. And yet I keep returning to PHP as a development platform, as have most of my fellow startup CTOs. But by the time I was building my first websites for commercial use , PHP had taken over.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

At a certain point in IMVU’s development, we faced a difficult choice. You should know that there are thousands of entrepreneurs who read this blog, some of whom are working on new platforms that will see the light of day someday. my Developer Tokens already answer the question for me. Thank you so much.

Community 158

Community Management Lean Software Review 158