Steve Blank

SEPTEMBER 5, 2018

And if their initial guesses were wrong, they needed a process that would permit them to change early on in the product development process when the cost of changes was small – the famed “pivot”. This same risk averse, conserve the cash, VC mindset would return after the 2008 meltdown of the housing market.).

Lean 335

Lean Burn Rate Startup IPO 335

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. As always, we had a great discussion with the students, which is helping refine how we talk about this.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Nice write-up.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. How dare you! =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 7, 2008

Lessons Learned by Eric Ries Friday, November 7, 2008 Using AdWords to assess demand for your new online service, step-by-step If you want to build an online service, and you dont test it with a fake AdWords campaign ahead of time, youre crazy. November 7, 2008 7:36 PM nitesh said. November 7, 2008 7:41 PM nitesh said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Labels: product development 15comments: mukund said. October 1, 2008 2:13 AM archenland said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 The three drivers of growth for your business model. Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. Choose one. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. October 13, 2008 6:47 PM Luke G said. December 4, 2008 4:43 PM Valto said. . Eric, love the blog. Connect (off)line? Thanks much.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. 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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. November 13, 2008 8:59 PM eisrael said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. October 6, 2008 9:41 PM Eric said.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. September 15, 2008 9:12 PM Hitchens said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. 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

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Ideas. 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. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. We try to take advantage of that phenomenon twice if possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. At the end of the day, the product development team of a startup (large or small) is a service organization. Great article.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

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. Start-ups supposedly dont have time for detailed processes and procedures.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

DECEMBER 16, 2009

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. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. You can find the 2005 version here. Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 18, 2008

Lessons Learned by Eric Ries Thursday, September 18, 2008 Lo, my 5 subscribers, who are you? September 19, 2008 2:08 PM gmlk said. September 19, 2008 2:25 PM Eric said. Thanks again, Eric September 19, 2008 2:26 PM Eric said. September 19, 2008 2:27 PM gmlk said. September 19, 2008 2:35 PM gmlk said.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

FEBRUARY 28, 2009

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 29, 2009

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. but rest assured they would be. . Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 12, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The basic idea is to avoid building something based on what you think it might need to do in the future.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 30, 2009

During the same period (1987 – 1990) and I did some work at MIT under Eric von Hippel on “user driven innovation with regard to software development&# which today would probably fall under the heading of “open source software development approaches.&# Expo SF (May. Conference streaming, sponsors, discounted tickets.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

APRIL 9, 2009

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. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167