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

MARCH 26, 2019

The class was unique in that it was 1) team-based, 2) experiential, 3) lean-driven (hypothesis testing/business model/customer development/agile engineering). When we started this class, the concept of Lean (business models, customer development, agile, pivots, mvp’s) was new to everyone.

Lean 248

Lean Business Model Balance Sheet Video 248

Startup Lessons Learned

DECEMBER 23, 2009

Lessons Learned by Eric Ries Wednesday, December 23, 2009 Why vanity metrics are dangerous In a previous post, I defined two kinds of metrics: vanity metrics and actionable metrics. In this post, Id like to talk about the perils of vanity metrics. My personal favorite vanity metrics is "hits."

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

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. Our mystery keynote is now revealed and I couldnt be more excited. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Steve Blank

MARCH 29, 2012

When Bob Dorf and I wrote the Startup Owners Manual we listed a series of Customer Development principles. I thought they might be worth enumerating here: A Startup Is a Temporary Organization Designed to Search. Pair Customer Development with Agile Development. Not All Startups Are Alike.

Customer Development 328

Customer Development Developer Customer Cofounder 328

Steve Blank

JULY 13, 2021

A decade later, I began to teach the foundations of Lean, first at UC Berkeley (Customer Development) and then at Stanford using cases and business plans. For each of these parts of the course design we needed to consider where on the spectrum of directed versus experiential each of the five parts of the class would fall.

Lean 433

Lean Agile Business Model Business Plan 433

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

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

MARCH 3, 2015

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. It taught lean theory ( business model design , customer development and agile engineering) and practice. Seeing Is Believing. It’s a big idea.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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. We''ve had to design and implement training programs to help on-board people to our culture and technology.

Lean 167

Lean Startup Software Engineering Agile 167

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 argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. Departments were built and were even metrics-driven.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. Expo SF (May.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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

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

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

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

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

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.

Product Development 153

Product Development Developer San Francisco Product 153

Steve Blank

MARCH 4, 2014

These groups are adapting or adopting the practices of startups and accelerators – disruption and innovation rather than direct competition, customer development versus more product features, agility and speed versus lowest cost. They measure their success on metrics that reflect success in execution, and they reward execution.

IRR 335

IRR Startup Business Model Agile 335

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

Startup Lessons Learned

OCTOBER 11, 2013

Problems arise when companies isolate areas of the business in what Eric refers to as “functional silos”—independently operating teams (design, engineering, marketing, legal, etc.) You have to go find your own customers to experiment with, you have your own brand, so you have to think like a Lean Startup.

Lean 167

Lean Silicon Valley Agile Cofounder 167

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

Technical Review 168

Technical Review Software Review San Francisco Lean 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. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Instead, we try to accelerate with respect to validated learning about customers. After you’ve spent months on a painstaking new design, who wants to be told what color blue to use?

San Francisco 154

San Francisco Lean Metrics Design 154

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. However, there’s the other side of the coin, which is the product design.

Technical Review 47

Technical Review Design Las Vegas Product 47

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. shoes in order to deduce possible competitors’ moves and anticipate customer needs.

Customer Development 196

Customer Development Developer Customer Silicon Valley 196

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

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. No vanity metrics should be looked at. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

AUGUST 26, 2009

And do your customer development. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Provide early seed capital, and be the ones to make those introductions.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68