Steve Blank

DECEMBER 13, 2010

Here’s the course announcement from Professor Vergara (in English): Customer Development Course in Chile – Lean Launchpad. The objective of this course is that groups of students finish with a completed software product that has real customers and an identified market.

Chile 235

Chile Silicon Valley Lean Agile 235

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

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

MARCH 3, 2015

Berkeley in 2010 to run the Lester Center for Entrepreneurship in the Haas School of Business we were teaching entrepreneurship the same way as when I was a student back in 1995. The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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. Eric Ries co-founded Catalyst Recruiting while attending Yale, and continued his entrepreneurial career as a Senior Software Engineer at There.com. Taking My Class.

Lean 120

Lean Technical Cofounder Silicon Valley Channel 120

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

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

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. Those early text-based games were programmed by their own users, and it was by far the best tutorial I could ever have received in the power of software.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Co mpanies also face Wicked problems.

Lean 294

Lean Chile Ukraine Spain 294

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

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. While that’s not true, it is a fact that entrepreneurs only have one word for “startup.” .

Customer Development 196

Customer Development Developer Customer Silicon Valley 196

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

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

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

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

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

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? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

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

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. This case presents a further complication: desktop software. Read on to find out.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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, Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

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 Continuous Deployment 113

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

Steve Blank

MARCH 18, 2011

Lean Startups/Back to Basics (2000-2010): No IPO’s, limited VC cash, lack of confidence and funding fuels “lean startup” era with limited M&A and even less IPO activity. Startups needed millions of dollars of funding just to get their first product out the door to customers. 2001 – 2010: Back to Basics: The Lean Startup.

Internet 334

Internet IPO Silicon Valley Agile 334

Startup Lessons Learned

APRIL 14, 2009

Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Force anyone who is in customer contact to take the role of the Product Owner and insist that they deliver something new on a short regular interval. (For Perhaps thats a fallacy?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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? Software is generally always getting better or getting worse. How fast do they iterate? Does it require weeks of QA?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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

Steve Blank

MAY 22, 2009

If you’re in markets that still exhibit at them (semiconductors, communications, enterprise software, etc.,) Everyone should be articulate and agile in describing and demoing the products.) this may be a useful read. For bigger booths a good rule of thumb is to have two to four staffers for every 100 square feet of exhibit space.

Silicon Valley 128

Silicon Valley RSS California Customer Development 128

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 76

Lean San Francisco Web Continuous Deployment 76

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. When It’s Darkest Men See the Stars - Steve Blank , November 24, 2010 When It’s Darkest Men See the Stars. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

MAY 27, 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, No departments The Five Whys for Startups (for Harvard Business R.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

MAY 14, 2009

The response so far has been nothing short of overwhelming, and I want to especially thank those of you who participated in the survey and customer validation exercise that helped shape this event. We changed our model to B2B and adopted Agile around 2002. This shift allowed us to crank out working software quickly as a service.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

FEBRUARY 22, 2009

MUDs made the essential truth about software into a powerful metaphor: that code is magic, giving those who wield it the ability to create new forms of value literally out of thin air. January 14, 2010 12:43 AM wesley chun said. January 14, 2010 12:43 AM wesley chun said. January 14, 2010 4:55 AM Ronald S Woan said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That mission critical customers wont accept new releases on a continuous basis. That continuous deployment leads to lower quality software than software built in large batches.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122