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. There are three stages: We start with ideas about what our product could be. How about documentation that nobody reads? the data on a regular basis.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MAY 31, 2010

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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. I documented the lesson plans etc on [link] March 4, 2009 5:25 AM Eric said. Case Study: Continuous deployment makes releases n.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JULY 6, 2009

Slides are below: The Lean Startup fbFund Edition View more documents from Eric Ries. Say you're not creating a product but doing a service? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. This is why I constantly stress the need to set specific, actionable targets for new product initiatives or new feature split-tests. Case Study: Continuous deployment makes releases n.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JULY 3, 2009

The Lean Startup fbFund Edition View more documents from Eric Ries. davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. And we’ve validated that learning by being able to demonstrate that when we change the product as a result of that learning, the key macro metrics improve. Let me illustrate.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Add onto that the incredible amounts of infrastructure code that we reused, and we were able to bring our product to market months earlier. In most cases, simple changes are simple to make.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 7, 2013

PayPal, under the leadership of David Marcus and Bill Scott, re-defining and re-engineering itself by embracing Lean Startup to improve the product experience. This doesn't mean pointing to the product and describing the product's value, but rather the marketing provides value itself.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

AUGUST 16, 2010

First, SlideShare is a fantastic product (that I use on a regular basis) and an impressive company example of Lean Startup practices in action. If your company is using minimum viable product , you’ve probably said the same thing yourself. But I have decided to make an exception today, for two reasons.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. It took me a long time to understand that benefit of our product. This probably sounds illogical.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

NOVEMBER 5, 2008

Youd better be able to speak their language and translate what your product does into benefits that they understand. Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Case Study: Continuous deployment makes releases n. If not, you might want to take a look.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60