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

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

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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?) .

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Steve Blank

JANUARY 15, 2017

I-Corps uses Lean Startup methods to teach scientists how to turn their discoveries into entrepreneurial, job-producing businesses. But I haven’t forgotten that before everyone else thought that teaching scientists how to build companies using Lean Methods might be a good for the country, there was one congressman who got it first.

Lean 274

Lean Technical Review Government Washington 274

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. Great to read posts about introducing lean approaches into more teams.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Up and Running

DECEMBER 6, 2012

Today, I want to introduce you to a new concept for starting and growing successful companies: Lean Planning™. Before I dive too deeply into the Lean Planning methodology, it makes sense to talk about its history and where it comes from. Lean Planning is born. At the time, we used Business Plan Pro and Basecamp for this.

Lean 147

Lean Silicon Valley Forecast Technical Review 147

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

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 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. The Lean Startup Intensive is tomorrow at Web 2.0. Ive attempted to embed the relevant slides below.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. January 6, 2010 12:49 AM Anonymoussaid. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Sounds very similar to agile development which is the way. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. for Harvard Business Revie.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. kaChing has been very active in the Lean Startup movement. kaChing has been very active in the Lean Startup movement. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Steve Blank

JUNE 11, 2009

Agile – you may find the real opportunities for your company was somewhere else. This means you still need to have a resilient personality, and be agile. And you’ll still need to have a resilient and agile personality, as new customer and product opportunities will appear and change your work. How quickly will you recover?

Cofounder 230

Cofounder Founder Silicon Valley Technical Cofounder 230

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) The Lean Startup movement has made tremendous progress in the past year. It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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

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

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

Steve Blank

JULY 7, 2015

My guests on Bay Area Ventures on Wharton Business Radio on Sirius XM Channel 111 were: Eric Ries , entrepreneur and author of the New York Times bestseller, The Lean Startup. Eric was the very first practitioner of my Customer Development methodology which became the core of the the Lean methodology. Origins of the Lean Startup.

Lean 120

Lean Silicon Valley Technical Cofounder Channel 120

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. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 As it turned out, my thinking was short sighted at best.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 22, 2010

Lessons Learned by Eric Ries Monday, February 22, 2010 Why diversity matters (the meritocracy business) Diversity is the canary in the coal mine for meritocracy. I already advocate cross-functional teams as part of the lean startup methodology. I already advocate cross-functional teams as part of the lean startup methodology.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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. March 26, 2010 8:42 AM ankur aggarwal said. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. steve Joshua , on January 5, 2010 at 3:19 pm Said: Fantastic entry, thanks very much Steve. The first reaction from my CEO was, “that’s why you’re running the department.”

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

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. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

MARCH 3, 2009

March 17, 2009 7:48 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.

Employee 146

Employee San Francisco Lean Software Review 146

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

FEBRUARY 22, 2009

January 14, 2010 12:43 AM wesley chun said. speaking of Python, over a decade ago, the creator of Python wrote an essay called Computer Programming for Everybody (CP4E) which turned into a DARPA grant describing how programming should be taught like reading, writing, and arithmetic: [link] January 14, 2010 1:25 AM drhowarddrfine said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143