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

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. Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Steve Blank

SEPTEMBER 5, 2013

We think teaching teams a formal methodology around the Lean Framework (Business Model design, Customer Development and Agile Engineering) is a natural evolution of how successful incubators/accelerators will build startups. The next customer segment we tried was startup founders. Technology in search of a market.

Lean 315

Lean Customer Development Sales Cycle Business Model 315

Steve Blank

MAY 6, 2015

Back then, an entrepreneur used a serial product development process that proceeded step-by-step with little if any customer feedback. Best practices in software development started to move to agile development in the early 2000’s. Microsoft Windows 3.0). Lessons Learned.

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

MARCH 6, 2013

. + 1,000 startup founders, investors, and press! Vinod Khosla Founder Dave McClure Founding Partner Eric Ries Author Steve Blank Serial Entrepreneur & Professor Todd Park CTO Travis Kalanick CEO & Co-Founder Joe Zadeh Director of Product Sam Shank Co-Founder & CEO NEW!

Lean 165

Lean Cofounder Startup Software Engineering 165

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. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

AUGUST 18, 2010

Here’s his story of when Customer Development failed. We were lucky to learn about Customer Development early on in the life of our startup. Along the way we were fortunate to meet Steve, develop strategic partnerships, and raise a series A round of investment. So how did Customer Development fail us?

Customer Development 230

Customer Development Developer Customer California 230

Steve Blank

JULY 7, 2015

Eric was the very first practitioner of my Customer Development methodology which became the core of the the Lean methodology. Jon Sebastiani , founder and CEO of KRAVE Jerky , a company that got its start in my class at Berkeley back in 2011 and was recently acquired by Hershey. Taking My Class.

Lean 120

Lean Technical Cofounder Silicon Valley Channel 120

Steve Blank

AUGUST 27, 2012

It was great to watch him embrace the spirit and practice of customer development. He was constantly in front of customers, listening, selling, installing and learning. I got to spend time inside his company while I was using their software to analyze early-stage ventures. And that’s where the problem was. he’d declare.

Founder 316

Founder Cofounder Advisory Board Burn Rate 316

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 242

Customer Development Developer Customer Silicon Valley 242

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 same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

JULY 25, 2023

In contrast, designing AI-driven enterprise software or building dating apps are comparatively simple problems.) I’ve known Professor Cristobal Garcia since 2010 when he hosted my first visit to Catholic University in Santiago of Chile and to southern Patagonia.

Lean 294

Lean Chile Ukraine Spain 294

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. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Steve Blank

JANUARY 28, 2020

We had just started an enterprise software company, Epiphany , and we were one of those disruptors. Customer Development became one of the three parts of the Lean Startup as Eric Ries and Alexander Osterwalder provided the other two components (Agile Engineering and the business model canvas.)

Lean 428

Lean Business Model Government Agile 428

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

MAY 31, 2010

When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Steve Blank

JUNE 25, 2009

These companies would take our computers and put their name on them and resell them to their customers. Business customers were starting to ask for “office automation solutions” – word processing, spreadsheets, graphing software on a desktop. Hiring a VP of Sales in customer discovery typically sets a startup back.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

JANUARY 18, 2010

This case presents a further complication: desktop software. Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. Read on to find out.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Please leave feedback!) Can you make a build in one step? Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

MARCH 18, 2011

Startups needed millions of dollars of funding just to get their first product out the door to customers. Software companies had to buy specialized computers and license expensive software. VC’s went back to basics, to focus on building companies while their founders worked on building customers.

Internet 334

Internet IPO Silicon Valley Agile 334

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 9, 2009

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. It uses principles of agile software development, open source and web 2.0, February 9, 2009 7:45 PM Joseph Flahiff said. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. Were a software company, so what we do everyday is turn ideas into code. Labels: agile , listening to customers 3comments: hauteroute said.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. Another is used by marketing to refer to what customers see.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

DECEMBER 20, 2013

Doctors, researchers and Principal Investigators in this class got out of the lab and hospital talked to 2,355 customers, tested 947 hypotheses and invalidated 423 of them. We kept track of all this data by instrumenting the teams with LaunchPad Central software.). Basil Ayish , MBA, Business Development. Lessons Learned.

Lean 241

Lean Customer Development IP Agile 241

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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. Just as a business incurs some debt to take advantage of a market opportunity developers may incur technical debt to hit an important deadline.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 5, 2008

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. More recently it's skewed to software & web. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." How long does the software sit un-deployed? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74