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

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

SEPTEMBER 7, 2009

This post describes how following the traditional product development can lead to a “startup death spiral.&# In the next posts that follow, I’ll describe how this model’s failures led to the Customer Development Model – offering a new way to approach startup sales and marketing activities.

Customer Development 232

Customer Development Developer Customer Silicon Valley 232

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. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 12, 2013

On November 14 (that’s this Thursday) at 1p PT, Eric Ries will speak with Kent Beck, a creator of Agile software development, about facilitating the work of engineers and product teams. Indeed, rapid cycles lead to very short release times and low costs of change.

Product Development 167

Product Development Software Review Technical Review Developer 167

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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? In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Labels: product development 15comments: mukund said. But a good day looked like this.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. 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.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

FEBRUARY 9, 2009

Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. 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. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 2, 2008

It costs not just the time of the actual meeting, but the time getting there and back, and the time preparing for it beforehand and thinking about it afterward. A Fundraising Survival Guide [link] Raising money has a mysterious capacity to suck up all your attention. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

MAY 27, 2009

Heres their description of the event: The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. 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.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

YoungUpstarts

JUNE 10, 2018

is the transformation of traditional mechanical chains in production to “cyber-physical” chains where companies, suppliers, and customers are all connected through IT networks and production processes are fully digitized and automated. Essentially, Industry 4.0 Start planning on how to adapt to Industry 4.0 Be Updated.

Agile 100

Agile Analytics Cloud Bankruptcy 100

Startup Lessons Learned

NOVEMBER 14, 2013

Each brave presenter gets five minutes and 20 slides—which advance automatically every 15 seconds. By the end of his workshop, you will know how to apply innovation accounting to truly track the progress of your product. If there’s a problem in production, developers need to own it.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Steve Blank

AUGUST 29, 2016

The end result is often that change can happen but it is going to come at the cost of disruption and difficulty.”. A year ago Sue Gordon, the deputy director of the NGA, sent out an agency-wide memo that said in part, “… we must build speed and flexibility (agility) into our acquisition processes to respond to those evolutions.

Lean 182

Lean Silicon Valley Government Acquisition 182

Steve Blank

AUGUST 29, 2016

The end result is often that change can happen but it is going to come at the cost of disruption and difficulty.”. A year ago Sue Gordon, the deputy director of the NGA, sent out an agency-wide memo that said in part, “… we must build speed and flexibility (agility) into our acquisition processes to respond to those evolutions.

Lean 182

Lean Silicon Valley Government Acquisition 182

Steve Blank

JUNE 25, 2009

Computer hardware companies were faced with their customers asking for low-cost (relatively) desktop computers they had no experience in building. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. The result wasn’t what I expected. Help them?!!

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

JULY 3, 2009

davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Although there is cost and overhead associated with continuous deployment, the benefits are immense. Now for the feedback.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

JUNE 15, 2009

In practice, how developers respond to this dilemma is determined by their incentives, which are driven by the culture of their team. Who will ultimately bear the cost of their mistakes? One of the distinctions that has helped at the executive level is to stress that you're reducing the COST of failure, rather then its PROBABILITY.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. I used to be skeptical of all this talk of “personal brand.&# Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 29, 2010

Heres a tiny sample: "Case studies, case studies, case studies presented by real people. Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand. Heres a tiny sample: "Case studies, case studies, case studies presented by real people.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

SEPTEMBER 2, 2008

Or your cost of customer acquisition just magically floats up to match your customer lifetime value. 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 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? 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?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

APRIL 18, 2010

Truth: The Lean Startup method is not about cost, it is about speed. Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

JUNE 17, 2010

And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 5, 2010

It is the ultimate product development get-started guide to Lean Startup. But," you are sure to ask, "how much will all this bundling cost me?" It is the ultimate product development get-started guide to Lean Startup. But," you are sure to ask, "how much will all this bundling cost me?" Phew, Im exhausted.

Lean 153

Lean San Francisco Startup Continuous Deployment 153

Startup Lessons Learned

MAY 22, 2009

Lessons Learned by Eric Ries Friday, May 22, 2009 The Lean Startup at SIPA follow-up I had wonderful time presenting at SIPA last night , and was completely exhausted by the incredible post-speech response. 2009 05 21 The Lean Startup At SIPA View more OpenOffice presentations from Eric Ries.

Lean 76

Lean San Francisco Continuous Deployment Startup 76

Startup Lessons Learned

MARCH 23, 2009

I started writing and teaching about shipping imperfect products a few years ago but this is a far better, practical and more powerful presentation. There is a lot to be said about the opportunity cost of perfection, iterative evolution and the difference between shipping a lemon and shipping a band aid. Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

SEPTEMBER 19, 2009

In my presentation this morning, I emphasized three key areas: reducing the personal cost of failure for entrepreneurs, innovation-friendly legal reforms, and access to the digital means of production (slides from my White House presentation are available at the end of this post). The Geeks are doing their part.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

MAY 17, 2009

Lessons Learned by Eric Ries Sunday, May 17, 2009 Last chance to register for The Lean Startup at HP on May 21 This coming Thursday, May 21, is the last time Im currently scheduled to give the full Lean Startup presentation in the Bay Area. Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs.

Lean 60

Lean San Francisco Continuous Deployment DC 60