Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 The three drivers of growth for your business model. Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? 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. Very few startups fail for lack of technology.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. When operating with continuous deployment, its almost impossible to have integration conflicts. Sounds very similar to agile development which is the way. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. By shipping software early, you give them continuous feedback about how it well its working.

Software Review 164

Software Review Engineer Management Technical 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. Case Study: Continuous deployment makes releases n. but rest assured they would be. .

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Ideas. Labels: agile , listening to customers 3comments: hauteroute said. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. Playing with new technologies. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time). Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. Hey Someone else who is extending the agile/lean approach beyond just developing software. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Web Advisory Board 68

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. September 15, 2008 9:12 PM Hitchens said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 12, 2008

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? Case Study: Continuous deployment makes releases n. Expo SF (May. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 28, 2008

Lessons Learned by Eric Ries Tuesday, October 28, 2008 A hierarchy of pitches Every company will need to pitch itself from time to time. Now there was nothing wrong with their analysis: anyone who invents a technology as sophisticated as The Transformers is definitely going to make a lot of money. are there any good substitutes?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

JANUARY 7, 2010

So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." You can tell a lot about a company from their deployment flow. After an hour with a team talking dirty about deployment, youll know. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. Case Study: Continuous deployment makes releases n. Automated tests make defects visible.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 Lo, my 5 subscribers, who are you? September 19, 2008 2:08 PM gmlk said. September 19, 2008 2:25 PM Eric said. Thanks again, Eric September 19, 2008 2:26 PM Eric said. September 19, 2008 2:27 PM gmlk said. September 19, 2008 2:35 PM gmlk said.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JANUARY 15, 2010

And when companies pursue sustaining innovations — like a product line extension or a new technology designed to serve an existing customer segment — this procedure makes complete sense. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Case Study: Continuous deployment makes releases n. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Here in Tampa, our biggest challenge is convincing the regions technology "leadership" that grassroots economic development is a good thing. My 2008 revenues were over $100k on a 35k inventory.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 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. It uses principles of agile software development, open source and web 2.0, and lean manufacturing to guide the creation of technology businesses that create disruptive innovation.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 9, 2010

Typical explanations tend to focus on the well-known anecdotes and larger than life archetypes we have in mind: the twenty-something college dropouts (men, of course) from Stanford inventing some radical new technology. Case Study: Continuous deployment makes releases n. The academic research tells a very different story.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Marc Prenskys Weblog: Cell Phones in Class Marcs writing has been a huge influence on me in thinking through the consequences of the way the current generation of "digital natives" is educated. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 16, 2008

Lessons Learned by Eric Ries Tuesday, September 16, 2008 How to Usability Test your Site for Free Noah Kagan has a great discussion of usability testing which can help get you over the "thats too hard" or "thats too expensive" fear. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Seth Godin: How often should you publish? 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 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. Case Study: Continuous deployment makes releases n. Its this second point I want to emphasize. . Expo SF (May. Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, September 6, 2008 Greasemonkey compiler Ive been incredibly impressed by Greasemonkey , the Firefox add-on that lets you easily extend the browser with simple Javascript. Case Study: Continuous deployment makes releases n. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Not crossing the chasm What does life feel like in the chasm ? We talk a good game about technology adoption curves and crossing the chasm, but most of us dont seem to recognize when its happening. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 19, 2009

I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. Particularly the Continuous Deployment and Split testing posts. Case Study: Continuous deployment makes releases n. Sounds a little abstract, though, doesnt it? Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

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

JUNE 17, 2010

The engineering team feels burned too, and feels that they were blamed for deficiencies in the spec as if it was their fault that the technology doesn’t really support what the artists want to do. Case Study: Continuous deployment makes releases n. So they react in two ways. So they react in two ways. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 7, 2013

Scott Summitt iteratively leveraging the emerging technologies of digital fabrication and 3d-scanning to change people's lives. As we head into 2013, it's a good time to reflect on how far the Lean Startup movement has come: When I first started blogging in August of 2008, I had no idea what to expect. It's a big tent.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

SEPTEMBER 3, 2009

If you look at the typical startup, you will see the vast majority of their energy and time invested in building new technology. We act as if the biggest risk to startup success is that the technology won’t work. Case Study: Continuous deployment makes releases n. Take the example of the Hoverboard. Expo SF (May.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

JUNE 21, 2010

And yet, we so often loose sight of the fact that startups are not their products, their technological breakthroughs, or even their data. Even the most radical new inventions always build upon previous technology. Even the most radical new inventions always build upon previous technology.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168