Startup Lessons Learned

SEPTEMBER 10, 2008

This is still an essential practice, especially on the web. There was a time when "web content" was considered "not code" and therefore not routinely source controlled. Notice that none of those five reasons deals with TDD or automated testing, which have changed the game. This is the approach of test-driven-development (TDD).

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

APRIL 9, 2009

To do that we will create end-user demand and drive it into the sales channel, educate the channel and customers about why our products are superior, and help Engineering understand customer needs and desires. We will accomplish this through demand-creation activities (advertising, PR, tradeshows, seminars, web sites, etc.),

Silicon Valley 268

Silicon Valley Technical Review RSS PR 268

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 And a special thanks is due to all of our presenters, panelists, and mentors. We all owe you.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

Lessons Learned by Eric Ries Thursday, June 17, 2010 No departments Big companies have departments. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. Startups are companies.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Steve Blank

JULY 27, 2009

And the odds in your favor are even higher, as most of your peers wouldn’t even get into the game due to some unspoken belief that in a meritocracy, good things will come to those who wait. While MBA’s have a ton of useful skills, what they don’t have is what most marketing departments lack – customer insight.

Silicon Valley 120

Silicon Valley RSS Technical Review California 120

Startup Lessons Learned

JANUARY 7, 2010

Lessons Learned by Eric Ries Thursday, January 7, 2010 Is Entrepreneurship a Management Science? for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. Read the rest at The Conversation - Harvard Business Review.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. It had a pretty good technical design. That "good design" turned out to be technical debt, after all.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. My success is due in no small part to their early and enthusiastic endorsement. The term was known by maybe a few dozen people. Youll probably get a better result, anyway.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

OCTOBER 20, 2008

Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. And has the tension goes down, it will be easier to get the whole team (including the MBAs) to embrace TDD and other good practices as further refinements. I'm a die hard believer in TDD.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. This time, Im discussing the challenge for corporate CFOs and VCs alike in holding entrepreneurs accountable.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. What is customer development?

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Talking to potential customers and competitors customers. One approach to the issue you bring up that's worked for us is to set an initial due date that’s overly aggressive, and expect that we’ll probably blow through it (while suspending disbelief as much as possible).

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. Im also excited to share two long-form reviews from actual attendees. Technically you argue it goes back 30 years when StorageTek was founded. More recently it's skewed to software & web. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

FEBRUARY 20, 2009

So when we start checking in code more often, release more often, or conduct more frequent design reviews, we can actually do a lot to make those steps dramatically more efficient. Junior developers tend to take a more traditional approach and have to be coached into following this line of thinking. Expo SF (May. . Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. For now, Id like to ask a favor.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

JUNE 15, 2009

Many times when I interview a development team caught in the pincers of this situation, they want my help "fixing people." So developers stuck in this world tend to think the other developers on their team are either, deep in their souls, plodding pedants or sloppy coders. Glad you don't develop software for space shuttles.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

NOVEMBER 9, 2009

Once he was on board, I sat down with him on a weekly basis to review our progress with our list of software vendors. Reply Daily Review #21 | The Queue Blog , on November 9, 2009 at 8:06 pm Said: [.] Think Different I still remember the day I discovered that I thought about progress differently than other people.

Silicon Valley 331

Silicon Valley Software Review RSS Technical Review 331

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. We didnt even practice TDD across our whole team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

AUGUST 24, 2009

If you’re a startup raising money or just want to see your name online, there’s not a better blog on the web. Dinner in a Strange Land When I was in my mid 20′s working at ESL, I was sent overseas to a customer site where the customers were our three-letter intelligence agencies. Or is it just someones end of innocence ?

Silicon Valley 206

Silicon Valley PR Technical Review RSS 206

Steve Blank

JUNE 15, 2009

Convergent Technologies When I was in my 20’s I worked at Convergent Technologies , a company that was proud to be known as the “Marine Corps of Silicon Valley.” I had thrown myself into a startup because work was an exciting technical challenge with a fixed set of end points and rewards. The Adventure of a Lifetime.

Entrepreneur 290

Entrepreneur Silicon Valley Technical Review RSS 290

Steve Blank

NOVEMBER 12, 2009

The presentation didn’t have a single word about Lean Startups or Customer Development. Reply Dan Hodgins , on November 13, 2009 at 1:12 am Said: Hi Steve, Just listened to your “Retooling Early Stage Development&# for about the 10th time tonight as I was cleaning my room. Your results may vary.

Venture Capital 234

Venture Capital Silicon Valley RSS Hockey Stick 234

Steve Blank

APRIL 20, 2009

Berkeley Haas Business School was courageous enough to give me a forum teach the Customer Development Methodology. The Man Who Shot Liberty Valance I always had been curious about how Silicon Valley, a place I had lived and worked in, came to be. After I retired, Jerry Engel , director of the Lester Center on Entrepreneurship , at U.C.

Silicon Valley 294

Silicon Valley RSS San Francisco Technical Review 294

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

The Next Web

JANUARY 27, 2013

It’s been slightly over two years since I attended Startup Weekend in September 2010, which literally changed my world for the better. Now, two years later, it is a good time to share some important lessons that I learned after taking the Red Pill that day in September 2010. This is only relevant for non-technical founders like myself.

Netherlands 159

Netherlands Technical Review Software Review Cofounder 159

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. They’ll increase code quality, prevent defects and educate your developers. However, hindsight indicates we forgot to do something important when developing IMVU: When the product changed, we did not update the code to reflect the new product, leaving us with piles of dirty code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 13, 2009

The Principles of Product Development Flow: Second Generation Lean Product Development Labels: product development , recommended reading 7comments: fnazeeri said. Wow, great review! Because of this we have had to educate ourselves in product development just to help keep projects on track. Expo SF (May. .

Product Development 153

Product Development Developer San Francisco Product 153

Up and Running

MAY 23, 2016

Broadly speaking, this action plan is going to be broken up into three sections: the testing plan, the execution plan, and the review section. And, the very last section— the review section — is really just a list of milestones you create that prompt you to review and revise your plan. Your forecast would have been for nothing.

Software Review 74

Software Review Software Delaware Forecast 74