Both Sides of the Table
MAY 19, 2010
Another topic we debated early in the program was “lean startup” vs. “ fat startup ” where we both took the obvious hedge and said “it depends.” But truthfully both Dana and I are more aligned with the lean startup principles and believe you only go FAT when you’ve really proved out your product / market fit. Employees: 20.
Startup Lessons Learned
JULY 29, 2009
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. In addition, third-party services and API’s enabled us to do more with less, but at a cost: taking on the technical debt of products and teams outside our direct control.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Steve Blank
NOVEMBER 16, 2009
However the Customer Development Model and the Lean Startup work equally well for startups on the web. The first question to ask is: “Does your startup have market risk or is it dominated by technical risk?” Lean Startup /Customer Development is used to find answers to the unknowns about customers and markets. Keep teaching!
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. January 29, 2010 11:18 AM Eric said. > January 29, 2010 12:55 PM Gareth Evans said.
Startup Lessons Learned
OCTOBER 20, 2008
The idea is that once we move to the new system (or coding standard, or API, or.) I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. The Lean Startup Intensive is tomorrow at Web 2.0.
Startup Lessons Learned
DECEMBER 28, 2009
A typical "new feature" release is, in my experience, about 80% changes to underlying APIs or architecture. A typical "new feature" release is, in my experience, about 80% changes to underlying APIs or architecture. The Lean Startup Intensive is tomorrow at Web 2.0. Thats because of the anatomy of a release. Expo SF (May.
Startup Lessons Learned
APRIL 26, 2009
Its a key lean startup concept. Open APIs and data-oriented architecture (aka "web 2.0"). For example, I recently created a customer validation exercise around the Lean Startup Workshop. The Lean Startup Intensive is tomorrow at Web 2.0. The much-promised era of component reuse in software is finally upon us.
Expert insights. Personalized for you.
240 
Let's personalize your content