Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. 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. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo (and a call for help) Ive been asked to speak this year at the Web 2.0 Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources. Expo SF (May. .

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. August 3, 2009 10:52 AM Chris Hopf said. August 3, 2009 11:49 AM Jason Brownlee said. August 3, 2009 8:08 PM William Mitchell said. Great post.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") April 27, 2009 8:59 AM Anonymoussaid.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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 Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. July 13, 2009 7:38 AM George said. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. This is why agility is such a prized quality in product development. I know of at least five former employees that went on to become startup founders. Labels: agile , customer development 5comments: William Pietri said.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. The Lean Startup Intensive is tomorrow at Web 2.0. Ive attempted to embed the relevant slides below.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Instead, we do everything possible to validate the founders belief. We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 7, 2008

To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. What a great post.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. February 21, 2009 12:10 AM Harold Fowler said. February 21, 2009 7:39 AM Rocky1138 said. February 21, 2009 12:26 PM Anonymoussaid. February 21, 2009 3:08 PM SCC said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. February 13, 2009 4:05 AM Eric said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Heck, thats what it says right there in the agile manifesto. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Or, perhaps theyll create an opening for another web platform to start a new cascade. But by the time I was building my first websites for commercial use , PHP had taken over.

PHP 166

PHP Software Review Ruby San Francisco 166

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. Go on an agile diet quickly.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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 There are so many more people to thank: Sarah Milstein and the Web 2.0

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Hearpreneur

JANUARY 15, 2021

To play up the name even more, I use when you need a best friend on the web as my tagline. 5-My co-founders’ wife came up with it. As much as I would like to take credit for the name it was my co-founders’ wife that thought of it. The thoughts were LI Shades Co, Island Shades, things like that.

Naming 127

Naming Entrepreneur Mexico Cofounder 127

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. If they were an unknown web 2.0 August 1, 2009 7:39 AM Ravi Mohan said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Was it an important or irrelevant fact that most of our web code was procedural and not object-oriented?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. .

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MARCH 27, 2009

Lessons Learned by Eric Ries Friday, March 27, 2009 Cash is not king Cash on hand is just one important variable in a startup’s life, but it’s not necessarily the most important. Unfortunately for the current crop of founders, there is intense pressure to engage in selective memory when companies tell the story of their founding.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. I was really overwhelmed this time.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

MARCH 25, 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 Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

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

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Were trying to put some of these "its the system, stupid" ideas into practice on NileGuide (www.nileguide.com) April 28, 2009 9:19 PM Jake Faris said. September 3, 2009 12:25 PM Omar Ead said. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Steve Blank

APRIL 30, 2009

New Century, New Channels For many of you reading this, boxes sitting on a retail shelf may seem hopelessly outdated, but the same marketing lessons hold for “award winning&# web sites or social media. Reply Bill Allred , on May 1, 2009 at 10:46 am Said: This is a really common pitfall.

Sales 120

Sales Silicon Valley RSS Las Vegas 120

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. There was a time when "web content" was considered "not code" and therefore not routinely source controlled. February 14, 2009 11:12 PM Eric said.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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