Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.

Agile 111

Agile Customer Development Developer San Francisco 111

Steve Blank

JUNE 11, 2009

Posted on June 11, 2009 by steveblank When my students ask me about whether they should be a founder or cofounder of a startup I ask them to take a walk around the block and ask themselves: Are you comfortable with: Chaos – startups are disorganized Uncertainty – startups never go per plan Are you: Resilient – at times you will fail – badly.

Cofounder 230

Cofounder Founder Silicon Valley Technical Cofounder 230

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. Labels: sllconf Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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 previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 13, 2011

At 11:45am I'll be honored to share the stage with two great entrepreneurs: Introducing The Lean Startup, by Eric Ries with case studies, Intuit’s Scott Cook and Instagram’s Kevin Systrom And in the evening, the book launch party is also part of Disrupt. By learning to be rapidly responsive and agile. You can grab one here.

Lean 155

Lean Seattle Los Angeles San Francisco 155

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

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

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

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

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 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. Instead, we do everything possible to validate the founders belief. We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 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

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

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

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

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

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But I think in a lean startup, the development methodology is too important to be considered "just management."

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. So let me say for the record: we didnt start with any of this at IMVU. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. The batch size is the unit at which work-products move between stages in a development process. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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 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. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. The response was surprisingly positive.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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

Steve Blank

MAY 9, 2017

The founders were simply wrong about their assumptions about customer needs. It turns out the term “visionary founder” was usually a synonym for someone who was hallucinating. Founders Need to Run the Company Longer. So, almost like clockwork 20 th century startups fired the innovators/founders when they scaled.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

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

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

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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

FEBRUARY 22, 2010

One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. I already advocate cross-functional teams as part of the lean startup methodology. Last year, I traveled to dozens of cities talking about lean startups and meeting people interested in entrepreneurship. None of these are impossible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. The lean startup focuses on situations where we have both an unknown problem and an unknown solution.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. Go on an agile diet quickly. More on that in a moment.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

OCTOBER 11, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. How can established companies benefit from implementing Lean Startup? Of course, you can also continue the conversation by attending The Lean Startup Conference. What can Lean Startup do about this? They’ll jump in to answer in the coming days. (Of

Lean 167

Lean Silicon Valley Agile Cofounder 167

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. They are leaders, visionaries, founders and managers having tremendous success. The Lean Startup Intensive is tomorrow at Web 2.0. Yet talent organized improperly can lead to failure. I was an engineer on the engineering team. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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