Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." Many of us are not accustomed to thinking about markets or customers in a disciplined way.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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

FEBRUARY 7, 2013

The Embrace infant warmer was developed - by getting out of the country -- and how Rob Emrich learned and scaled his non-profit, Road of Life. BetaBrand building apparel MVPs and testing them quickly with targeted customer communities. LitMotors approach to using Lean Startup to create a new vehicle category. It's a big tent.

Lean 167

Lean Entrepreneur San Francisco Agile 167

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Ive attempted to embed the relevant slides below. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the minus side, that has made it a wee bit hard to understand.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

usersknow.blogspot.com

APRIL 30, 2010

A good answer to this question should really include all of the following: I have both development and design time scheduled for quick follow up work on the feature over the next few sprints. ► February (1) 6 Ways You May Be Failing at Customer Development ► 2009 (9) ► December (1) Which Metrics Equal Happy Users?

Software Review 40

Software Review Agile San Francisco Metrics 40

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

The Equity Kicker

OCTOBER 2, 2014

At that time he was talking about infrastructure monitoring, doing customer development work but had yet to start the company. They were coming out of Alfresco where they’d built a custom solution to monitor their infrastructure as they’d moved from an on premise software company to a cloud play.

Cofounder 95

Cofounder Continuous Deployment Seed Stage Cloud 95

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 13, 2008

Wanted to add one additional note from the perspective of someone who was intimately involved in developing this system. When Eric writes, "By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage." Case Study: Continuous deployment makes releases n.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. The hardest part of entrepreneurship is to develop the judgment to know when its time to change direction and when its time to stay the course. IMVU had a roughly two-month-long development cycle. Heres what it looked like.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 15, 2008

The goal is to have split-testing be a continuous part of our development process, so much so that it is considered a completely routine part of developing a new feature. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

AUGUST 1, 2009

For one, capacity development. Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. What do all those other people do? Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. One of the sayings I hear from talented managers in product development is, “good enough never is.&#

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 7, 2008

Oops - there went several precious weeks of development effort down the drain. If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customer development is in order? Case Study: Continuous deployment makes releases n.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

SVPG

JULY 31, 2013

The surprising thing is that the accomplishments I feel proudest of today are not the actual products I helped create, but rather, the many people across our industry I have helped to hire and develop. I believe in continuous improvement. I love seeing them creating exceptional products, and leading great organizations of their own.

SCRUM 60

SCRUM Continuous Deployment Agile Lean 60

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Labels: product development 15comments: mukund said. What made them exceptional?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 2, 2009

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. My experience is: usually not.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JUNE 17, 2010

Even more surprisingly, the engineering team was equally vocal about their contention that adding rounded corners would add weeks of development time to the project, which would have pushed it out way past its hard deadline, effectively killing it. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 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. Still, a startup product development team is a service organization. Were there to serve customers direclty, as well as all of the other functions of the company.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

AUGUST 3, 2009

You refer to an anonymous Valley-based MMORPG that consumed years and tens of millions in development, but got little commercial traction. 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

FEBRUARY 22, 2009

But its not very open, and not very programmable, unless you have an expensive Mac and an approved developer license. Not only are there free compilers and development systems, but there are also a number of efforts to develop development systems and languages specifically aimed at teaching kids to program.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

OCTOBER 5, 2009

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. As a result, potential customers are being turned away; they can only afford to engage with the customers that are best qualified.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 22, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Want to learn more about me?

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Try About the author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155