Startup Lessons Learned

NOVEMBER 14, 2013

Jonathan Irwin will lead a workshop on advanced interview skills , including the different kinds of customer interviews, how to develop questions, and how to apply the answers to an actual decision around a product. By the end of his workshop, you will know how to apply innovation accounting to truly track the progress of your product.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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

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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Similar results apply in product management, design, testing, and even operations.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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 25, 2011

And this year, we’re going to talk not just about business and product development, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. Yes, you really can use continuous deployment – even in an SEC regulated environment. Wealthfront CTO Pascal-Louis Perez will show you how.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 4, 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?

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. (See

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Five Whys has its origins in the Toyota Production System.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). in ten years?

Lean 165

Lean Technical Review Startup Software Review 165

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. Case Study: Continuous deployment makes releases n.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." Whats wrong with this picture?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Have you worked with or for a great CTO?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 30, 2009

.&# In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. Case Study: Continuous deployment makes releases n. Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. The temptation is try and build a toolkit of general pieces, which can be assembled into many kinds of final product. Case Study: Continuous deployment makes releases n. The same process works in Interaction Design.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Expo (and a call for he.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 2, 2008

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 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 12, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months. What’s going on?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

After an hour with a team talking dirty about deployment, youll know. 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,

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Combined with the technology trends above, it also enables rapid deployment strategies like just-in-time scalability.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 6, 2009

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. Labels: events , slides , video 7comments: Eemo said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. So the product development team was busy creating lots of split-tests for lots of hypotheses.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113