Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. The number of Lean Startup meetup groups has crossed 100, spreading out from traditional startup hubs like San Francisco and New York to a wide variety of places.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 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." April 23, 2010 in San Francisco. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MAY 31, 2010

I had really debated about whether there was any value in spending the time and money to fly to San Francisco when there was a perfectly serviceable simulcast going on in Cleveland. All I can tell the folks who attended the simulcasts is that I’m not missing either the time or the money.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted. Expo SF (May.

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. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 8, 2008

When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." The theory of Product/Market Fit is one key component of customer development, and I highly recommend Marcs essay on that topic.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 22, 2008

You get increasing growth by optimizing the viral loop , and you get revenue as a side-effect, assuming you have even the most anemic monetization scheme baked into your product. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Similar results apply in product management, design, testing, and even operations. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Hearpreneur

DECEMBER 16, 2020

It could be more revenue, hiring clients or launching a new product or service, but every new year is an exciting time because it’s ripe with opportunity. 4- Remain agile as a brand. For 2021, I want to remain agile and understand our industry’s changes to apply them to our business decisions and ensure growth this coming year.

Entrepreneur 147

Entrepreneur Agile San Francisco Artificial Inteligence 147

Startup Lessons Learned

JULY 28, 2010

It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

OCTOBER 7, 2016

series that also includes the Future of Work , the Future of Corporate Agility, Skill-Sharing, and more in the weeks leading up to Lean Startup Week. It also adds the customer empathy piece that was missing for me from agile or Lean methods. How do we give our employees tools to have productive conversations with the community?

Government 165

Government Lean Startup San Francisco 165

Startup Lessons Learned

JANUARY 12, 2010

Rich also organized the first Lean Startup Meetup right here in San Francisco. Rich also organized the first Lean Startup Meetup right here in San Francisco. April 23, 2010 in San Francisco. The SF Meetup now has over five hundred members, and has spawned many other meetup events. Expo SF (May.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

AUGUST 2, 2008

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? April 23, 2010 in San Francisco. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

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

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. April 23, 2010 in San Francisco. TechStars encourages them to go wherever opportunities take them.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JULY 5, 2010

The results of the Customer Development process may indicate that the assumptions about your product, your customers and your market are all wrong. They tell them to persist in their dream of building a great product and/or company, no matter what the odds are or what the market might be telling them – success is just around the corner.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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? Labels: product development 15comments: mukund said. But along the way, something strange happened. It became harder and harder to separate how the software is built from how the software is structured.

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. There are three stages: We start with ideas about what our product could be. Labels: agile , listening to customers 3comments: hauteroute said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. He wrote it in 2000, and as far as I know has never updated it. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 7, 2010

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? April 23, 2010 in San Francisco. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 17, 2008

If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Expo SF (May.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 30, 2009

In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. April 23, 2010 in San Francisco. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Steve Blank

APRIL 21, 2011

All the teams were showing us what agile looked like, but this week several would remind us what focused and relentless really meant. its product or service) to its customers. Should they create a freemium version of their current product? If you have more than one product, how will you package it into various offerings?

Channel 235

Channel Artificial Inteligence San Francisco Business Model 235

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 9, 2010

In management jobs related to operations – that is, the people tasked with actually making and distributing physical products – this kind of thinking is now considered ludicrous, thanks to a century of progress. April 23, 2010 in San Francisco. In fact, making mistakes is seen as “proof&# of being second-class.

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

DECEMBER 23, 2009

Now picture product prioritization meetings in such a company. Im talking about the adhoc crisis decisions, the periodic product prioritization meetings, and the failure post-mortems. Now picture product prioritization meetings in such a company. Consider a teams last few critical decisions. Those are the easy meetings.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

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

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 12, 2008

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? Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 6, 2009

Say you're not creating a product but doing a service? 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? April 23, 2010 in San Francisco. Expo SF (May.

Lean 115

Lean Video San Francisco Continuous Deployment 115