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. Do you fix bugs before writing code? Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

conversionxl.com

SEPTEMBER 10, 2013

It’s Not a Conversion Problem, It’s a Customer Development Problem. The product or website (be it software, e-commerce, or a service) might be awesome , but if it puts itself in front of the wrong market, or packages itself so the right market can’t figure out why it’s awesome, the startup will fail.

Customer Development 60

Customer Development Conversion Developer Customer 60

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

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

ConversionXL

SEPTEMBER 24, 2020

Dave McClure’s conversion metrics visualize where different conversion optimization opportunities lie—including those for acquisition. If you don’t have customers, our articles on customer development and how to write compelling copy without customers can help you get started. Image source ).

Acquisition 111

Acquisition Software Review PPC Analytics 111

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

OCTOBER 20, 2008

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

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?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

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. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

David Teten

SEPTEMBER 23, 2017

An investor had few hard metrics other than the actual financials, and little technology to make the process scaleable. Over the past few decades, better metrics became available, and investors could take a more analytical, data-driven approach. Many tools designed for B2B marketing in general are also relevant to investors.

Private Equity 60

Private Equity Venture Capital Equity Technical Review 60

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. But there is more to technical debt than just the interest payments that come due.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

David Teten

APRIL 1, 2021

This typically includes: Relationships with relevant service providers in your vertical, often with pre-negotiated discounts: coaches, lawyers, accountants, common software vendors, consultants. You might hire a really amazing designer, and perhaps even charge companies for their service for cost recovery purposes. Advantages.

Private Equity 78

Private Equity Venture Capital Portfolio Equity 78

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Dates are irrelevant.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

steveblank.com

JULY 8, 2011

Home Books for Startups Guide Secret History-Bibliography Steve Blank Startup Tools Steve Blank Entries RSS | Comments RSS Email Subscription Get Steve Blank via your RSS Feed RSS - Posts RSS - Comments Categories Air Force (12) Ardent (10) Audubon (1) Big Companies versus Startups: Durant versus Sloan (39) Business Model versus Business Plan (..)

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Steve Blank

APRIL 2, 2009

Metrics – Mine is Bigger Than Yours The first thing SuperMac needed to do was to change how our potential color desktop publishing customers viewed our products versus our competitors’ products. As hokey as it is, when confronted with uncertainty or unknowns, human beings like to be reassured by comparative metrics.

Silicon Valley 124

Silicon Valley Technical Review RSS Software Review 124

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. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? When an investor says he wants to invest in you, or an acquirer says they want to buy you, dont believe it till you get the check.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

ConversionXL

JANUARY 31, 2014

note: If you’re a startup, you’ll want to use customer development questions for your page to resonate with future traffic). All of this is to inform a landing page design that’s in-line with your target market expectations which plays a huge role in reducing the amount of friction it takes for them to convert.

Analytics 134

Analytics Video Matching Conversion 134

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

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. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

ConversionXL

MAY 22, 2014

To guide the discussion, we’re going to be using Dave McClure’s Conversion Metrics as a framework to see where different conversion optimization opportunities lie. For Acquisition, we’re primarily asking how do first time visitors & potential customers find you? Upon inspecting the source code, visitors would find the following.

Software Review 116

Software Review PPC Analytics Search 116

conversionxl.com

FEBRUARY 4, 2014

note: If you’re a startup, you’ll want to use customer development questions for your page to resonate with future traffic). All of this is to inform a landing page design that’s in-line with your target market expectations which plays a huge role in reducing the amount of friction it takes for them to convert.

Analytics 98

Analytics Software Review Conversion Video 98

www.vccafe.com

MARCH 11, 2013

VC Cafe highlights everything you need to know from hosting your code in hackathons to open source legal docs. Steve Blank on Lean Customer Development. Customer service. Design/Front End: Twitter Bootstrap : Include this in your website, and you are half finished. LiveRoad : A Great IDE for design is very helpful.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. Over time, such teams either explode due to irreconcilable differences or dramatically slow down. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. As the product matured, they were able to ratchet up the quality to prevent regression on features that had been truly embraced by their customers.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. We all owe him our thanks for persevering.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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. At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g.

Employee 146

Employee San Francisco Lean Software Review 146

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