Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. February 21, 2009 12:10 AM Harold Fowler said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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

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? It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. But all things are never equal. (Of

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. why couldnt the engineer see the problem in their sandbox?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

APRIL 4, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. Nothing is more demoralizing to an engineering team. leanstartup bmorrow : Not just for engineers: ask why 5x every time something unexpected happens.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

JULY 28, 2010

the version that would facilitate the investment of real money) was planned for late-2009. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. the version that would facilitate the investment of real money) was planned for late-2009. The result? The response was surprisingly positive.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. Instead, we do everything possible to validate the founders belief.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Continuous deployment is another such technique, one with a unique power to change development team dynamics for the better. One is used by engineers to refer to the process of getting code fully integrated into production. Why does it work?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

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

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

OCTOBER 5, 2008

For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

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

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Yet talent organized improperly can lead to failure. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. September 25, 2009 5:23 PM jchunter said.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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 work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

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. You can learn more about that by reading The engineering managers lament.) August 28, 2009 1:15 PM Derek Scruggs said.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 7, 2008

And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Seems like a fairly low-cost method of gauging customer interest for a would-be product. February 7, 2009 5:40 AM Major_Grooves said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. July 30, 2009 7:35 AM Hazem Awad said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 28, 2008

Most important slide: live demo Prototype product Key questions: what will it take to ship a working product? whos on the engineering team? can the team bring the product to market? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? how do you know anyone would want it?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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

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. Then you set up a web app to co-ordinate volunteers who can wipe a hard drive and install Ubuntu. February 22, 2009 5:54 PM CapnCleaver said. Ill explain in a moment.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. 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

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

JULY 5, 2010

As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. No departments The Five Whys for Startups (for Harvard Business R.

Customer Development 166

Customer Development Developer San Francisco Customer 166