Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. that we learned different.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 5, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

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

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 2, 2008

Do the engineers understand what they are building? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Can they tell a good release from a bad one?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. 1 comments: flixsterwidgettest said. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

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?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. Like gmlk, I usually subscribe the first time I find something useful. You can even meet the friend.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? How to listen to customers, and not just the loud. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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). How do you plan for it?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. You have customers, they are using your product, and you are trying to help them. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Life is so easy in the days before the "launch" - you just focus on building and polishing those new features.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. Thoughts on scientific product development Lo, my 5 subscribers, who are you? When will you be speaking? wow, dead on.

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? And wait until you see a "non-technical" designer writing simple code to try and speed up a release.

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