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. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Our mystery keynote is now revealed and I couldnt be more excited. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Steve Blank

JUNE 3, 2010

If you’ve been reading my book on Customer Development and follow my work on Market Type , this type of innovation is best for adding new products to existing markets. In fact the people a large firm needs for this kind of innovation looks suspiciously like startup founders and the processes needed look like Customer Development.

Search 251

Search Agile Customer Development Technical Review 251

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. on April 10, 2009 at 6:58 am Said: Amazing blog. Greetings from Crete, Greece Reply Jerry Ji , on April 10, 2009 at 11:09 am Said: Simply _THE BEST_ war story I’ve read in months.

Silicon Valley 271

Silicon Valley Technical Review RSS PR 271

Startup Lessons Learned

NOVEMBER 7, 2008

If you cant find any , maybe that means you havent figured out who your customer is yet. 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. May 6, 2009 3:03 PM Ivan Acosta-Rubio said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. The answer depends on your answer to two questions: which step in the Customer Development process are you on?

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

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

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? January 18, 2009 8:22 AM Dan Khan said. Cheers, -Dan January 18, 2009 9:04 PM Ivo said. January 20, 2009 1:12 PM Anonymoussaid. April 12, 2009 12:28 AM kenshin said. Great article!

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

Steve Blank

APRIL 27, 2009

And in hindsight, we seemed a bit more agile and innovative in WWII.) Yet decades later the military lacked the agility to write a spec in two years, let alone get 10′s of thousands of new systems deployed on aircraft as Terman had done. How was this possible? invention of electronic warfare, part I and [.]

Silicon Valley 210

Silicon Valley Technical Review Europe Germany 210

Steve Blank

APRIL 6, 2009

If you are a practitioner of Customer Development, ESL was doing it before most us were born. In 1962 Wheelon left for a new job as the first director of the CIA’s Directorate of Science and Technology where he was responsible for development of OXCART , the A-12 Spyplane, and three major satellite reconnaissance systems.

Silicon Valley 201

Silicon Valley Stealth RSS California 201

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. February 11, 2009 8:05 AM Anonymoussaid. June 15, 2009 9:27 PM Mark Graban said. link] June 20, 2009 2:52 PM Anonymoussaid. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. 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. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. June 15, 2009 8:24 AM Stevesaid.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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? Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 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. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

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 3:11 AM Eric Williamson said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 13, 2008

Those rates gave us a map that told us a lot about our customers; insights that proved stable even when the company grew orders of magnitude bigger. Only much later did I realize that this was an application of customer development to online marketing. Thank yo u January 3, 2009 4:07 PM BillSeitz said. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. March 25, 2009 4:44 PM Dan McGrady said. March 25, 2009 5:04 PM j pimmel said. Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 28, 2010

the version that would facilitate the investment of real money) was planned for late-2009. the version that would facilitate the investment of real money) was planned for late-2009. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The result? The result? Expo SF (May.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. Great points Eric. Another OODA loop fan! Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. link] May 11, 2009 9:04 PM Ian Wilson said. Would this advice translate equally to businesses where the potential number of customers is small (BtoB rather than BtoC)? May 11, 2009 9:42 PM Artem said.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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. And do your customer development. These quotes are, as is my custom, straight from twitter. August 28, 2009 1:15 PM Derek Scruggs said.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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

MAY 31, 2010

When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Steve Blank

MAY 9, 2017

The watershed moment was in 2009 when the co-founder of Netscape, Marc Andreessen, formed a venture firm and started to invest in founders with the goal to teach them how to be CEOs for the long term. A few, like John Doerr at Kleiner Perkins and Don Valentine at Sequoia, had operating experience in a large tech company.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

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