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. Rich also organized the first Lean Startup Meetup right here in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

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

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric. Expo SF (May.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

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. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. Expo SF (May.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

SoCal CTO

JANUARY 5, 2011

Steve Blank , January 25, 2010 10 Tips for Adding Game Mechanics to a Non-Gaming Service - ReadWriteStart , September 21, 2010 Startups & VCs: Learn How to Design, Market, & Eat Your Own. - First Principles. Berkonomics , November 29, 2010 Rice Alliance IT/Web 2.0

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

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? ) Eventually, I came to summarize these themes with the phrase " the lean startup." Lean is one of the major trends shaping our world, and its impact goes beyond just optimizing our supply chains.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 7, 2008

February 17, 2010 1:09 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.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 25, 2011

The Lean Startup movement has made tremendous progress in the past year. If you recall, around this time last year we were still fighting various myths , such as “ lean means cheap ” or that we don’t support having a big, world-changing vision. This year, the word pivot has become over-hyped ( even on TechCrunch ).

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

SEPTEMBER 7, 2008

One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars. Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Expo SF (May. for Harvard Business Revie.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible. None of these are impossible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups. Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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 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

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

NOVEMBER 8, 2008

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. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JUNE 17, 2010

The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. The meeting was tense. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

MAY 9, 2012

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. Since then, Brant and Patrick have been tireless advocates for the whole Lean Startup movement. Illustrations by FAKEGRIMLOCK. You can pre-order it starting today.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Steve Blank

JANUARY 6, 2014

In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. But businesses are finding that Continuous Deployment not only changes engineering but has ripple effects on the rest of its business model.

Continuous Deployment 332

Continuous Deployment Customer Agile Cloud 332

Startup Lessons Learned

DECEMBER 8, 2008

For those of you with some background in lean manufacturing, you may notice that integration risk sounds a lot like work-in-progress inventory. As with many lean startup practices, its getting started thats the hard part. This will help me improving me my work skills in term of coding and designing. That what actual CI is.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

APRIL 4, 2010

blog comments powered by Disqus Newer Post Older Post Home 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?) The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

FEBRUARY 22, 2009

:-) January 15, 2010 1:29 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.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

OCTOBER 11, 2010

(I am often asked to explain how to apply Lean Startup approaches to domains beyond software. The key to understanding Lean Startup is to recognize two things: Lean Startup techniques confer maximum benefit in the upper-right quadrant, namely high market uncertainty coupled with fast cycle time. It turned out we indeed could.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

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 Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 13, 2008

July 20, 2009 1:44 PM 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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 5, 2010

While maintaining persistence and willpower is certainly good advice, Customer Development methodologies are designed to give you data and feedback you may not want to hear. The Lean Startup Intensive is tomorrow at Web 2.0. It is incumbent upon you to listen. This is important, since every situation is different. Expo SF (May.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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

AUGUST 26, 2009

I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113