Steve Blank

SEPTEMBER 5, 2018

Tech IPO prices exploded and subsequent trading prices rose to dizzying heights as the stock prices became disconnected from the traditional metrics of revenue and profits. Almost overnight the floodgates opened, and risk capital was available at scale from venture capital investors who rushed their startups toward public offerings.

Lean 335

Lean Burn Rate Startup IPO 335

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

Steve Blank

OCTOBER 15, 2019

These processes reduce risk to an overall organization, but each layer of process reduces the ability to be agile and lean and – most importantly – responsive to new opportunities and threats. Metrics are used to manage process rather than creation of new capabilities, outcomes and speed to deployment.

Government 322

Government Technical Review Acquisition Metrics 322

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

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

MARCH 6, 2013

> Uber's " Reality Therapy 4 Startups": What U Need 2 Know NOW > Steve Blank on why NOT to be an Entrepreneur > Airbnb's Globetrotting Lessons: Building 4 a Global Market > Vinod Khosla - The VC Legend: Interview w/ Dave McClure > Eric Ries on Entrepreneurship: What He's Learned Along the Way > GitHub's Secret 2 Success: Rethinking (..)

Lean 165

Lean Cofounder Startup Software Engineering 165

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 7, 2008

If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. What is customer development?

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. In a customer problem pivot, we try to solve a different problem for the same customer segment. It was painful.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

YoungUpstarts

APRIL 21, 2013

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Such direct experiences allows one to test critical “leap-of-faith” assumptions about what customers like and dislike.

Lean 193

Lean Technical Review North America Startup 193

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Labels: customer development , split-test 7comments: Editor said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

MARCH 29, 2012

When Bob Dorf and I wrote the Startup Owners Manual we listed a series of Customer Development principles. Pair Customer Development with Agile Development. No Business Plan Survives First Contact with Customers. Startup Metrics are Different from Existing Companies. Not All Startups Are Alike.

Customer Development 331

Customer Development Developer Customer Cofounder 331

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. Expo SF (May.

Product Development 153

Product Development Developer San Francisco Product 153

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. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The result was a new process of four-week iterative cycles all about throttling new code.

Lean 167

Lean Startup Software Engineering Agile 167

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. And the results weren’t the traditional PR metrics of number of articles or inches of ink. We were constantly creating metrics to see the effects of different PR messages, channels and audiences on end-user purchases.

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

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

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. dalelarson : "Metrics are people, too." Metrics are a key questions startups face.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. What good are these metrics if they dont help guide product or business decisions?

Metrics 88

Metrics San Francisco Lean Viral 88

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? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? But along the way, something strange happened. Expo SF (May.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. Go on an agile diet quickly. And yet, their investors are frustrated.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. Expo SF (May.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

FEBRUARY 20, 2009

Sounds very similar to agile development which is the way. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No doubt about it, small batches are the way to go RT www.anonymity.eu.tc February 21, 2009 7:39 AM Rocky1138 said. Im a huge fan of small batches as well. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 20, 2008

As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

MARCH 3, 2009

In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 9, 2009 8:35 AM Eric said.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 13, 2008

Those rates gave us a map that told us a lot about our customers; insights that proved stable even when the company grew orders of magnitude bigger. Only much later did I realize that this was an application of customer development to online marketing. Its now a technique I recommend for any web-based startup. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But it worked. We made it. So can you.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123