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. Heck, thats what it says right there in the agile manifesto.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 8, 2008

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? And what about if deployment takes forever? By delegating and training, we create a corps of leaders who could step in to provide CTO-like services on demand. Have you worked with or for a great CTO?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 26, 2009

Anyone who has worked in a real-world product development team can tell you how utopian that sounds. As a result, we tried many different stratagems to avoid giving the impression that we were a fully-featured IM system, going so far as to build our initial product as an add-on to existing IM programs.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

NOVEMBER 18, 2008

I believe its important that product teams be cross-functional, no matter what other job function the product champion does. . Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JUNE 8, 2009

Periodic or on-demand reports are one possibility, but we can do much better. I got a powerful taste of datablindness recently, as I’ve started to work with various large companies as partners in setting up events, speeches, and other products to sell around the Lean Startup concept. We can learn to see. Expo SF (May.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 7, 2013

A few of the detailed case studies include: Tech legend Bill Gross building an MVP in 1999 to test demand for online car sales, which grew into CarsDirect.com. Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

MARCH 11, 2010

High-profile startup Friendster had first-mover advantage in the social networking space, but created openings for competitors when it could not scale to meet demand. High-profile startup Friendster had first-mover advantage in the social networking space, but created openings for competitors when it could not scale to meet demand.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 5, 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. Using AdWords to assess demand for your new online.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

OCTOBER 4, 2010

Many journalists and conference organizers attempt to fill this demand by giving successful entrepreneurs the opportunity to tell their stories: in magazines, on blogs, and on stage. Case Study: Continuous deployment makes releases n. Most of the received wisdom about business and entrepreneurship is simply wrong. Expo SF (May.

San Francisco 167

San Francisco Lean Metrics PR 167

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. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 19, 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. Using AdWords to assess demand for your new online.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

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. What if customers actually like the “crap&# product? Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 11, 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. Using AdWords to assess demand for your new online.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

OCTOBER 5, 2009

In other words, a principled way to combine agility with stability. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. In other words, a principled way to combine agility with stability.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. oh, and on the book front, you'll be able to get all of my essays so far in ebook, print-on-demand, and kindle editions - coming soon. Case Study: Continuous deployment makes releases n. Leave your thoughts in a comment.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

NOVEMBER 17, 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. Using AdWords to assess demand for your new online.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

DECEMBER 7, 2008

As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

DECEMBER 14, 2009

In other words, the minimum viable product is designed to answer the question: does the product generate enough demand and margin to support a growing ecosystem? In other words, the minimum viable product is designed to answer the question: does the product generate enough demand and margin to support a growing ecosystem?

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

NOVEMBER 22, 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. Using AdWords to assess demand for your new online.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 2, 2010

This is just like a startup to me, complete with distribution and product development challenges, ecosystem design and many, many customers. Do you have a suggestion for a guest speaker or case study that illustrates a particular lean startup concept: minimum viable product, continuous deployment, validated learning, the pivot?

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

FEBRUARY 12, 2009

In the world of startups, this is like trying to sell a product to a very demanding customer who needs to see a lot of features before buying. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Wed train them on-demand as they came in, and send them into the world (or onto the phones) with written instructions and voter contact data. Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

SEPTEMBER 11, 2009

until I couldn't seem to find a way from getting away from all these nasty, vulgar teens (or people pretending to be teens) demanding explicit sex every time I went there. Case Study: Continuous deployment makes releases n. I was very enthusiastic about IMVU, and loved their tutorials, and praised them on my blog, etc.

Community 158

Community Management Lean Software Review 158