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. So I initially gravitated to the CTO title, and not VP of Engineering. What does your Chief Technology Officer do all day? Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Techniques from lean manufacturing can be part of a startups innovation culture. Speed up or slow down? Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

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. His keynote will kick off the day as well as our module on the build phase of the fundamental feedback loop that powers all startups. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

JUNE 17, 2010

Startups are companies. Startups aspire to become big companies. Therefore, startups should have departments. Each of these benefits also exists in startups, which is why most startups are also organized in departments. I once worked at a startup with an exceptional functional department system.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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? ) In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. kaChing has been very active in the Lean Startup movement. It was written by Sarah Milstein in collaboration with kaChing CEO Andy Rachleff.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. Every time an engineer checks in code, they are batching up a certain amount of work. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

Lean 68

Lean San Francisco Web Advisory Board 68

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. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. If you want to see the original video, use the link above.

Lean 115

Lean Video San Francisco Continuous Deployment 115

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. My path to lean startups began with Kent Beck and extreme programming.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MARCH 16, 2009

Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully. Embedded in that assumption is why startups fail. Hes often felt that there was something missing. This is a significant improvement on the traditional waterfall methodology. Enter Jims post.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. I think this idea is particularly appealing to those of us from an engineering background. But this is wrong, too.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

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

NOVEMBER 7, 2008

It was one of those brilliant startup brainstorms that comes to the team in a flash, with a giant thunderclap. Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Eric, Excellent article about an essential technique for startups. The Lean Startup Intensive is tomorrow at Web 2.0.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. Expo SF (May. .

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Hackers Guide to Investors [link] Whatever help investors give a startup tends to be underestimated.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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

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

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. We tend to equate startup success with making money, but that is a poor choice.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 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

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. One is used by engineers to refer to the process of getting code fully integrated into production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 10, 2008

I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. but I have not seen that dysfunction in any of the startups I advise, so hopefully its behind us. At IMVU, our rule was that a new engineer needed to push code to production on their first day.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are on-schedule and on-budget, but their gross metrics are way off. They are on-schedule and on-budget, but their gross metrics are way off. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 2, 2008

October 17, 2009 10:34 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JANUARY 7, 2010

As an entrepreneur, I often saw the best practices of general management fail startups. My most recent startup created a marketplace for customers to buy and sell virtual goods for their 3D avatar. As an entrepreneur, I often saw the best practices of general management fail startups. Applied out of context, they were dangerous.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. Bring it on!

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process. Expo SF (May. .

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131