Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

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

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Our mystery keynote is now revealed and I couldnt be more excited.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

A Smart Bear: Startups and Marketing for Geeks

JUNE 12, 2012

Robert Graham of WhiteTail Software (and this awesome guest post on cold calling ) asks: @whitetailsoft When do you stop #custdev efforts and build the product? Here are the details of both of those customer development experiences. I’ve been wrestling with the details of #leanstartup. Way #1: Go until boredom.

Customer 252

Customer Customer Development Dilution Engineer 252

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 18, 2010

This case presents a further complication: desktop software. Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? Continuous Deployment is a process by which software is released several times throughout the day – in minutes versus days, weeks, or months.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. But its helpful to take a detailed look inside the highly agile process used by Google to ship software. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. Another is used by marketing to refer to what customers see.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 31, 2010

When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

Austin Startup

FEBRUARY 24, 2018

Much of the writing on startups focuses on two elements: finding product-market fit scaling the company once #1 is accomplished For product-market fit, we have a lot of source material to work with from the last decade: Steve Blank’s leadership on Customer Development , and Eric Ries’ on the Lean Startup ?—?along One example.

Warrant 48

Warrant Bootstrapping Framework Hiring 48

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." How long does the software sit un-deployed? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. Please leave feedback!) They just dont happen.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, Labels: events 2comments: Andrew Meyer said. Check out what I am doing at.

Lean 68

Lean San Francisco Web Advisory Board 68

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

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? But along the way, something strange happened.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. More recently it's skewed to software & web. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Revisiting the Software Design Manifesto (and what. Provide early seed capital, and be the ones to make those introductions.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good? It didnt work.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Please register to attend this event as space will be limited.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

APRIL 14, 2009

(For more on how this plays into the process of scaling up, see the Customer Creation stage of the customer development model.) But in the meantime, by iterating on their product with customers, they have a chance to get there on their own. Labels: agile , customer development 15comments: Scott Shapiro said.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MAY 14, 2009

The response so far has been nothing short of overwhelming, and I want to especially thank those of you who participated in the survey and customer validation exercise that helped shape this event. This shift allowed us to crank out working software quickly as a service. For now, Id like to ask a favor. It was a disaster.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

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. We just had our app support a few tens of thousands of customers, and it did well.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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 Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? That’s all fine and dandy.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That mission critical customers wont accept new releases on a continuous basis. That continuous deployment leads to lower quality software than software built in large batches.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

OCTOBER 5, 2008

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 26, 2009

So we tried to craft a strategy that would give us the product development leverage we needed to serve all customers. We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. Even as "just a user" you make the community better by adding momentum.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Retention cohort analysis. Funnel averages over time. You can read the article to find out why.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

JULY 29, 2009

Let's consider cases: Can you have a piece of software with good product design and bad technical design? In that case, the user experience and system performance might be good, but the cost of future development would be high. Can you have a piece of software with bad product design and good technical design?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 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. This is a good sign for you! :) I subscribed because I was inspired by the O'Reilly video, and feel I want to go deeper into the customer development field. So why you?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

FEBRUARY 22, 2009

MUDs made the essential truth about software into a powerful metaphor: that code is magic, giving those who wield it the ability to create new forms of value literally out of thin air. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

APRIL 18, 2010

That process involves rapid hypothesis testing, validated learning about customers , and a disciplined approach to product development. internet/consumer software companies. Truth: The Lean Startup methodology applies to all companies that face uncertainty about what customers will want.

Lean 167

Lean San Francisco Continuous Deployment Startup 167