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. After all, the worst kind of waste in software development is code to support a use case that never materializes. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. After all, our startup is on a fixed budget.

Software Review 164

Software Review Engineer Management Technical Review 164

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

JUNE 17, 2010

Startups are companies. Startups aspire to become big companies. Therefore, startups should have departments. Each of these benefits also exists in startups, which is why most startups are also organized in departments. I once worked at a startup with an exceptional functional department system.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

AUGUST 27, 2012

Knowing how to sort between vision and hallucination can avoid chaos inside your startup. He turned his PhD thesis into a killer product, got it funded and now was CEO of a company of 30. It was great to watch him embrace the spirit and practice of customer development. Filed under: Customer Development.

Founder 321

Founder Cofounder Advisory Board Burn Rate 321

Startup Lessons Learned

SEPTEMBER 8, 2008

I was building a new startup in 1999, and wanted to do it right. That startup didnt turn out so well, but not for lack of technology. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. In a successful startup, the development team is also growing.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. Glad you don't > develop software for space shuttles. Expo SF (May. . Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. By far the most important thing you want to hire for in a startup is the ability to handle the unexpected. Those people also tend to go crazy in a startup.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. But startups rarely have either luxury.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 8, 2009

Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. And what hurdles could be eliminated?

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy. Just change it. What a waste.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May. . Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 16, 2009

This is a great example of lean startup thinking. Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all. The Lean Startup Intensive is tomorrow at Web 2.0.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

ConversionXL

SEPTEMBER 10, 2012

“ There are no facts inside your building, so get outside ,” is one of the mantras of Steve Blank , the father of customer development and author of The Startup Owner’s Manual. Once you have your first customer profile written down, go out and meet these people or businesses. Talk to people.

Audience 122

Audience Analytics B2B eCommerce 122

techcrunch.com

OCTOBER 23, 2010

Problem was, I seemed to suck at the whole startup thing. Rather, I didn’t have anyone around me familiar enough with startups to tell me that I was doing it all wrong. So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. You just can’t do it all.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea. Michael Wolfe , On startup #4 and counting.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

JANUARY 30, 2009

Bring in an expert CEO with outstanding business credentials and startup experience to focus on relentless execution. Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. Even a great architecture becomes inflexible. Focus on quality. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Nonetheless, I want to talk about a dysfunction Ive seen in several startups: they are literally refactoring themselves to death. They have a product that has a moderate number of customers. Heres a company I met with recently.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79