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

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. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. It was a great experience to see a relatively new startup hub in action - and thriving. Their model looks like a key ingredient in the startup brew there.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 29, 2013

This post was written by Sarah Milstein, co-host of The Lean Startup Conference. We’re looking for speakers for the 2013 Lean Startup Conference. If you’re a Lean Startup veteran, feel free to skim the beginning, as this is mostly stuff you already know. Last week, we announced that our short application form was live.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? But I dont think most startups really have a need for someone to do that on a full time basis. It became harder and harder to separate how the software is built from how the software is structured. Massive proprietary databases?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. you get the idea. you get the idea.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

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

APRIL 25, 2011

It’s been just over a year since the inaugural Startup Lessons Learned conference , and it’s time to do it again. The Lean Startup movement has made tremendous progress in the past year. Kent Beck himself helped us explain that “quality work” means something different when we’re facing the extreme uncertainty of a startup.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. 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.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

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

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Everyone else can register to come to both sessions for free, including the Lean Startup talk in the main conference. What does this mean for you?

Lean 76

Lean San Francisco Web Continuous Deployment 76

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

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. First of all, the Startup Lessons Learned conference exceeded my wildest expectations. He inspired me to take a deeper look at what we all thought we understood about startups.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

MARCH 16, 2009

Jim Murphy is a long-time agile practitioner in startups. 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. But startups sometimes have trouble applying agile successfully. Embedded in that assumption is why startups fail.

Agile 111

Agile Customer Development Developer San Francisco 111

crowdSPRING Blog

DECEMBER 8, 2011

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Small Business and Startups: For Great Customer Service, Speed Counts – [link]. Small Business and Startups: For Great Customer Service, Speed Counts – [link].

Social Media 94

Social Media Small Business Design Media 94

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." You can tell a lot about a company from their deployment flow. I havent met anyone who would do a day-long deployment every day. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

OCTOBER 5, 2008

But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. Expo SF (May. . Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

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. They just assumed it was the way software companies worked. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. You can click here to learn more.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

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 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? The Lean Startup Intensive is tomorrow at Web 2.0.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. 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. Very few startups fail for lack of technology.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In a startup, we should take full advantage of our options, even if they feel dirty or riddled with technical debt. Startups are always moving, so invest in moving faster and better.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 26, 2009

Its a force that allows startups to build products at parity with much larger companies - cheaper and much faster. Its a key lean startup concept. We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? In an early-stage startup especially, revenue is not an important goal in and of itself. Let’s start with a simple question: why do early-stage startups want revenue?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 8, 2008

I was building a new startup in 1999, and wanted to do it right. It felt like software that grownups were supposed to use, and we didnt qualify. That startup didnt turn out so well, but not for lack of technology. Now you can build an app at true web scale without incurring any software costs, or any fixed hardware costs.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

APRIL 18, 2010

Lessons Learned by Eric Ries Sunday, April 18, 2010 Four myths about the Lean Startup Myth: Lean means cheap. Lean startups try to spend as little money as possible. Truth: The Lean Startup method is not about cost, it is about speed. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer

Lean 167

Lean San Francisco Continuous Deployment Startup 167