Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. Case Study: Continuous deployment makes releases n.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 25, 2011

And this year, we’re going to talk not just about business and product development, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. For readers of this blog, Steve needs no introduction. Yes, you really can use continuous deployment – even in an SEC regulated environment.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. For more on continuous deployment, see Just-in-time Scalability.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already).

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

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. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 2, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Case Study: Continuous deployment makes releases n.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

OCTOBER 5, 2008

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. Once the different parts of the team can trust each other again, well have the basis we need to start a true continuous improvement feedback loop.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JANUARY 7, 2010

Although much of it will sound familiar to readers of this blog, whats new is my first step towards the " new entrepreneurship " that is my goal for 2010. Unlike previous cross-posting Ive done for blogs, where a lot of the discussion happens here, Id like to ask you to take a minute and click through to read the full article.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. Case Study: Continuous deployment makes releases n.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JULY 30, 2009

Brad Feld also had some thoughts on this event on his blog. In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 12, 2010

Beyond my own efforts on this blog ( and more ), there is now an amazing variety of resources for lean startup practitioners. When I first started blogging, the startup blogging mafia immediately came to meet me and find out who I was: Dave McClure , Andrew Chen , Sean Ellis and Venture Hacks. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Case Study: Continuous deployment makes releases n.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

APRIL 29, 2013

Or you could work with the writer to create a blog, see if it can attract a readership, and then test whether those readers will pre-order a book—which you can do before you’ve put ten seconds of effort into creating a print volume. You can give advice about applying Lean Startup ideas to business areas other than product development.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. =) November 4, 2008 10:58 PM IMVU said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 6, 2009

I worry sometimes about making this blog too much into a travelogue or journal of my public events. wow this blog is god awful. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

NOVEMBER 7, 2008

This is one of the blog we posted about how some company is doing SEO to promote the website. 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. This post has been removed by a blog administrator. link] November 8, 2008 7:13 PM Jason said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

AUGUST 26, 2009

Im always excited to see how these ideas are expressed by entrepreneurs in their own words: petewarden : Another blog post, this one on the @ericries Lean Startup Workshop I attended: [link] #leanstartup tmarkiewicz : Notes from the Lean Startup Dinner with @ericries [link] #leanstartup And I can never resist sharing some positive feedback.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. and more ► January (6) Lo, my 18891 subscribers, who are you?

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

FEBRUARY 9, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Please teach kids programming, Mr. President Work in small batches Continuous deployment with downloads What is a market? (a

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. Well done, Brant and Patrick.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 2, 2008

After an hour with a team talking dirty about deployment, youll know. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. A book I am looking forward to read after reading you blog. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 14, 2008

As Seth writes this week in Seths Blog: Listening to the loud people , the most aggressive customers arent necessarily the ones you want to hear from. Thanks Eric, your blog has many golden nuggets!!! Case Study: Continuous deployment makes releases n. September 25, 2009 5:23 PM jchunter said.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

MAY 31, 2010

Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here. You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) Case Study: Continuous deployment makes releases n.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168