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. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. February 21, 2009 12:10 AM Harold Fowler said. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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? Labels: product development 15comments: mukund said. 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.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Ive attempted to embed the relevant slides below. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 7, 2008

February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. We run a web development company and we start by creating a splash page very similar to what is describe here. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. Great post - I think Ill try this.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. April 27, 2009 10:54 AM DSarathy said.

Product Development 88

Product Development Developer San Francisco Product 88

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

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Great post.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. But also, the ETL doesn't change much anymore (except when integrating a new system), now that the warehouse is in production most of the change occurs in the marts and analytic products.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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? Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team?

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

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 7:49 AM Eric said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. March 26, 2009 6:15 PM Will said. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

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

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

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

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

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. Labels: agile , listening to customers 3comments: hauteroute said. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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

SEPTEMBER 13, 2008

Thank yo u January 3, 2009 4:07 PM BillSeitz said. May 8, 2009 2:27 PM Eric said. May 8, 2009 2:39 PM VictusFate said. There is much work that I need to do (the only developer so far) before we have something customers can use. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. The result? The result?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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

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

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

Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. Andreessen realized that the game had changed.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

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. May 11, 2009 9:42 PM Artem said. May 11, 2009 10:12 PM Nicholas Kormas said. May 13, 2009 6:38 AM Jason Lander said. May 14, 2009 10:05 PM Jeff said.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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

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

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

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

Ideally, by the time I code it up, we'll have many customers using the platform which means I'll be working on a product I know is viable, and that's paying for the time I'm spending to automate it. Agile Development, meet Agile Business. After your product launch. Point #1: Developing a Proof of Concept.

Software Review 284

Software Review Startup Technical Review Hosting 284

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. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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. I think Drucker said it best. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MAY 31, 2010

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? Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 14, 2008

September 25, 2009 5:23 PM jchunter said. 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?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131