Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. Were a software company, so what we do everyday is turn ideas into code. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. I havent met anyone who would do a day-long deployment every day. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 24, 2009

One is explaining the world as it used to work: the importance of gatekeepers, the scarcity implied by limited distribution, and the resulting quality bar that the industry is so proud of. Mostly it is the time and expense required to create the means of distribution for that industry. It’s just taking some longer than others.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. Leveraged distribution channels. For a specific application of this idea, see How to get distribution advantage on the iPhone.)

Product Development 88

Product Development Developer San Francisco Product 88

The Next Web

AUGUST 6, 2013

There is a lot of talk about the lean startup and whether it works or not. But the lean startup model, when you boil it down, simply says that when you launch any new business or product you do so based on validated learning, experimentation and frequent releases which allow you to measure and gain valuable customer feedback.

Lean 132

Lean Startup Continuous Deployment Open Source 132

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

APRIL 14, 2009

Because they have no presence in the market, they have to find distribution channels to bring in customers. So heres the question that I pose to you - our startup helps software companies develop a scalable revenue engine in the form of software-specific hardware devices. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 10, 2008

His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) I’ve been in the software industry for a long time. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. That’s all fine and dandy.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. 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. The Lean Startup Intensive is tomorrow at Web 2.0. I dont really remember why it didnt work.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 18, 2008

For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. Lean Start-up SlideShare prez at Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. 9 - Retweeted "2."

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JULY 15, 2010

And the fact that the effects of this IPO vanishing act are being felt first and foremost in the software business also makes sense to me. In fact, I believe that the software business is the canary in the coal mine: increasingly, all businesses are going to look more and more like software businesses. We have much work to do.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

OCTOBER 7, 2008

Lessons Learned by Eric Ries Tuesday, October 7, 2008 The App Store after the gold rush I wrote earlier about the issue of distribution advantage on the iPhone. I think its helpful to think about two kinds of competition for distribution: acquisition competition and retention competition. So what can you do? Expo SF (May.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. But notice how many hypotheses are baked into this supposedly simple scenario: we believe we have already solved the distribution problem for our product (or else how could customers try it?). Pivot or persevere?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 22, 2010

Even the most radical Bell Curve -style thinkers have to concede that even if there are differences between men and women in the distribution of these traits on average, these curve have substantial overlap, and there should still be a lot more of them represented in high-tech startups. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 22, 2008

For example, trying to make server software more scalable. The Lean Startup Intensive is tomorrow at Web 2.0. 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?

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 4, 2009

Incremental and proportional software complexity. This is great for something like a huge DHT or a distributed work queue. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 23, 2009

In the process, they learned a lot by asking initial prospects to sign a non-binding letter of intent to buy the software. The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner. Read on and judge for yourself.

San Francisco 144

San Francisco Customer Wiki Lean 144

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. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. As always, Paul is right.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

Loyalty is not something that people distribute to all and any that they come into contact with regardless of warrant. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

Community 158

Community Management Lean Software Review 158