Startup Lessons Learned

APRIL 26, 2009

We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. In that same spirit, here are some suggestions for tactics you can use to increase the leverage of your product development efforts: Free and open source software (and even hardware ).

Product Development 88

Product Development Developer San Francisco Product 88

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. The webcast is free with registration and will include a live Q&A with attendees. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

FEBRUARY 11, 2009

Having had a number of years to try and answer this question at cocktail parties and social gatherings of all kinds, I thought Id try and expand on his framework a little, and then try and use these answers to help make suggestions for those who are trying to get people to buy virtual goods. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

AUGUST 1, 2009

In the meantime, I hope some of you will find the lean startup a helpful framework. So I don't think the Apple experience should be used to discount lean, agile, or customer development-type approaches. The only efforts a new product team should be expending are those that lead to validated learning about customers. Expo SF (May.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 13, 2009

In some businesses, especially in certain industries like traditional enterprise software, you simply cannot bring a new product to market on your own. As weve quietly signed up dozens of paying customers for our software (and kept them), Ive faced intense pressure from family, friends, staff, even our attorneys, to just "Launch".

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

DECEMBER 7, 2008

Our CTO is the CEO himself, but he lacks the understanding of the new software development processes and the new technologies. In school I was being pounded day and night with anything that has to do with agile software development. Case Study: Continuous deployment makes releases n. I am basically a one-man shop.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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. As always, Paul is right.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 12, 2009

a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Expo SF (May. Expo (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89