Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MAY 7, 2009

Lessons Learned by Eric Ries Thursday, May 7, 2009 Fear is the mind-killer Fear is an emotion that slows teams down. I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. It makes us more cautious.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? February 11, 2009 8:05 AM Anonymoussaid. June 15, 2009 9:27 PM Mark Graban said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. January 2, 2009 8:54 AM mancjew said. January 2, 2009 8:57 AM Abbas said. Abbas February 22, 2009 3:33 PM cwillu said. Would love to get in touch.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. Remember Hamlet?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Once the different parts of the team can trust each other again, well have the basis we need to start a true continuous improvement feedback loop.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. April 27, 2009 10:54 AM DSarathy said.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

NOVEMBER 7, 2008

February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. We run a web development company and we start by creating a splash page very similar to what is describe here. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. Great post - I think Ill try this.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. the version that would facilitate the investment of real money) was planned for late-2009. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. July 3, 2009 7:49 AM Eric said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. March 14, 2009 8:34 AM Can Sar said. April 11, 2009 1:22 AM CeeTee said.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

FEBRUARY 22, 2009

Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. February 22, 2009 5:54 PM CapnCleaver said. February 22, 2009 10:14 PM Aleks said. February 23, 2009 2:22 AM Clement said. February 23, 2009 9:23 AM Clement said.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 13, 2008

Thank yo u January 3, 2009 4:07 PM BillSeitz said. May 8, 2009 2:27 PM Eric said. May 8, 2009 2:39 PM VictusFate said. There is much work that I need to do (the only developer so far) before we have something customers can use. Case Study: Continuous deployment makes releases n.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. September 3, 2009 12:25 PM Omar Ead said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

APRIL 4, 2010

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? Those who are interested in work-in-process might want to take a look at Work in small batches and Continuous deployment - Eric) Some specific TPS practices appear in Lean Startups. Case Study: Continuous deployment makes releases n.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Take a look and let me know what you think.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. March 3, 2009 9:54 PM surya said. March 3, 2009 10:02 PM Sean Murphy said. March 3, 2009 11:15 PM kareem said. March 3, 2009 11:28 PM Jon said. Dont even go there.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. August 28, 2009 1:15 PM Derek Scruggs said.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 9, 2009

Lessons Learned by Eric Ries Thursday, April 9, 2009 Built to learn Its been an exhilarating ride since the Web 2.0 Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Ill continue to post about additional events as I get them scheduled.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. February 13, 2009 4:05 AM Eric said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

DECEMBER 8, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

SEPTEMBER 14, 2008

September 25, 2009 5:23 PM jchunter said. 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?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 12, 2010

Some of my favorites: Ash Maurya (whose Achieving Flow in a Lean Startup was one of my favorite posts of 2009), Brant Cooper , CindyAlvarez , Laura Klein , Kevin Dewalt , Giff Constable - and I must be missing many more. Case Study: Continuous deployment makes releases n. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JUNE 2, 2010

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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? Take a look and let me know what you think.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. July 6, 2009 4:21 PM Anonymoussaid. July 6, 2009 8:43 PM Eric said.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

DECEMBER 23, 2009

Lessons Learned by Eric Ries Wednesday, December 23, 2009 Why vanity metrics are dangerous In a previous post, I defined two kinds of metrics: vanity metrics and actionable metrics. Case Study: Continuous deployment makes releases n. In this post, Id like to talk about the perils of vanity metrics.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 5, 2010

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. January 21, 2009 6:39 AM Kevin Merritt said. January 21, 2009 1:19 PM Jon Bischke said. January 23, 2009 4:13 PM TS said. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140