Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. For software, the easiest batch to see is code. When something goes wrong with production software, its almost always because of an unintended side-effect of some piece of code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Lean 68

Lean San Francisco Web Advisory Board 68

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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

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? Software is generally always getting better or getting worse. You can tell a lot about a company from their deployment flow.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 2, 2009

The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value. My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Funnel averages over time. 3comments: Charles Crawford said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

MARCH 16, 2009

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. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first. Hes often felt that there was something missing.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Bring your questions.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. More recently it's skewed to software & web. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. All customers will see the new software as soon as it’s deployed.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

JULY 5, 2010

Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MAY 31, 2010

Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. Do you know the difference between Durant and Sloan ? If not, youd better watch video of his talk ASAP. And then you can buy a t-shirt. And then you can buy a t-shirt.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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 continuous deployment leads to lower quality software than software built in large batches. Monitoring of real-world metrics. Or variations thereof.

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. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Bring your questions.

San Francisco 158

San Francisco Management Software Review Product 158

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

MARCH 17, 2009

I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. April 23, 2010 in San Francisco.

Lean 76

Lean San Francisco Web Continuous Deployment 76

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? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. But along the way, something strange happened.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned - the Conference (April 23.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. That’s all fine and dandy. Is that mass all that critical?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. So heres the question that I pose to you - our startup helps software companies develop a scalable revenue engine in the form of software-specific hardware devices.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. As a shoestring entrepreneur with a SaaS (well, not really, but sort of) offering that we present to very large companies (think 10K+), I love your common sense suggestions about metrics and testing.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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

APRIL 26, 2009

We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. In that same spirit, here are some suggestions for tactics you can use to increase the leverage of your product development efforts: Free and open source software (and even hardware ).

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

AUGUST 24, 2009

Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. The problem is that there are no other metrics they can look at to judge the content of a book to know if it’s worth reviewing. Is that a lot? In that I see opportunity.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MAY 14, 2009

This shift allowed us to crank out working software quickly as a service. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

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. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

APRIL 18, 2010

internet/consumer software companies. internet/consumer software companies. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer

Lean 167

Lean San Francisco Continuous Deployment Startup 167

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? Can you have a piece of software with bad product design and good technical design? This btw, is not true to all aspects of software and all realms of life. But I think they're still mostly orthogonal.

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

JULY 15, 2010

And the fact that the effects of this IPO vanishing act are being felt first and foremost in the software business also makes sense to me. In fact, I believe that the software business is the canary in the coal mine: increasingly, all businesses are going to look more and more like software businesses.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

APRIL 26, 2010

Want to talk about applying the lessons beyond software, internet, and small companies? Want to talk about applying the lessons beyond software, internet, and small companies? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. It exceeded my expectations totally. Details are below.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. In fact, MVP is quite annoying, because it imposes extra overhead.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168