Startup Lessons Learned

JULY 29, 2009

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. Case Study: Continuous deployment makes releases n.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 12, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. Case Study: Continuous deployment makes releases n.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0, Case Study: Continuous deployment makes releases n. Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? After an hour with a team talking dirty about deployment, youll know. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 30, 2009

During the same period (1987 – 1990) and I did some work at MIT under Eric von Hippel on “user driven innovation with regard to software development&# which today would probably fall under the heading of “open source software development approaches.&# Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. These tests are written by the engineers themselves, and they must all pass every time.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Case Study: Continuous deployment makes releases n. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 8, 2008

Our open source counterparts who did solve the scale problem, had some serious hardware costs to deal with. So did I when I finally found myself building an app with real scalability, a few years later, but a combination of our just-in-time scalability technique and great open source scaling tools, made it manageable.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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

The Next Web

AUGUST 6, 2013

Editor’s Note: The following is a guest post by James Donelan , the VP of engineering at MuleSoft , provider of the world’s most widely used integration platform. Others claim that it’s unproven , unscientific and gets your product to market in a haphazard way that is ungrounded in quality. Lean startup engineering.

Lean 132

Lean Startup Continuous Deployment Open Source 132

Startup Lessons Learned

SEPTEMBER 10, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 10, 2008

You have customers, they are using your product, and you are trying to help them. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I see startups struggle with this all the time.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. For readers concerned about the chasm, I recommend reading Seth Godin's thoughts on "Being remarkable" and finding a unique edge/twist for your products and marketing (edgecraft). Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 16, 2008

Usability testing is great for coming up with ideas about what to change in your product, but dont forget to split-test those ideas to make sure they work, too. Case Study: Continuous deployment makes releases n. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Sorry about this being out of context but I wonder if youve read "What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services". Case Study: Continuous deployment makes releases n.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 18, 2008

You can find out what it would take for them to adopt your product, and then follow up a week later and see if they did. Same with finding out what it would take to get them to recommend your product to a friend. Case Study: Continuous deployment makes releases n. You can even meet the friend. can I talk to them?"

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. Case Study: Continuous deployment makes releases n.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. So dont just kill the feature - iterate.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MAY 22, 2009

For example, the agile practice of an in-house customer or product owner that can make authoritative prioritization decisions seems like it doesnt translate very well to startups. In almost every case, people who ask me about the MVP already have a product in development - and it is plenty good enough to start getting feedback.

Lean 76

Lean San Francisco Continuous Deployment Startup 76

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

FEBRUARY 11, 2009

Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Although he didnt know much about our app when he started, he was able to be productive from day one, because we immediately put him to work extending our applications use of the library in question.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

OCTOBER 11, 2010

We loved the product. Test users loved the product. I envisioned the product would be popular with 8 to 12 year old boys. I already knew how the product would be used. I found the perfect person at the department of Industrial Design Engineering of the Delft University of Technology. It was way ahead of its time.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. The store determines which products sit on which shelves, and which yours sits next to. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. Case Study: Continuous deployment makes releases n. This is what the BSD license was invented for, for example.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 28, 2008

The entrepreneurship progarms of the business, engineering, and undergraduate schools are all tackling the subject this semester, and Im honored to be part of it. hitchens - theyre not open to the public as far as I know, but if you have an affiliation with Stanford engineering, undergrad, or GSB, its possible you could come audit.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 29, 2008

Question 1: When youre adding features to a product used by an existing user base, do you still do split testing to determine usage patterns? Existing customers already have an expectation about how your product works, and its important to take this into consideration when adding or changing features. Absolutely, yes.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 4, 2009

In this scheme, all of the data related to a specific feature of a product are stored on the same machines. We can take advantage of the many open source libraries out there that dont scale especially well, and write as much non-scalable code as we want. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

DECEMBER 7, 2008

Each experiment is like a little mystery, and if you can get into a mindset of open-mindedness about the answer, the answers will continually surprise and amaze you. A few days ago I open-sourced a framework for split-testing, A/B testing or continous optimization. Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

Startup Lessons Learned

JANUARY 12, 2009

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Add onto that the incredible amounts of infrastructure code that we reused, and we were able to bring our product to market months earlier. Thats simply impossible on most platforms.

PHP 166

PHP Software Review Ruby San Francisco 166