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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. Very well stated!

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. This workshop brings together leading thinkers from Lean Production and Lean software.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: Expo San Francisco 2009 The current macroeconomic climate presents unparalleled opportunities for those that can thrive with constrained resources.

Lean 68

Lean San Francisco Web Advisory Board 68

ctotodevelopers.blogspot.com

JULY 11, 2012

I cover several topics including agile software development, software startups, web 2.0, Labels: about me , agile planning , agile software development , cio , innovation , it management , organizational change , product management , project management , software development , software qa.

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. It uses principles of agile software development, open source and web 2.0, Thanks, Alexandre Gomes May 28, 2009 8:59 AM Eric Overton said. Thanks for an enjoyable evening.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 260

Lean Silicon Valley Startup RSS 260

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

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. August 1, 2009 7:39 AM Ravi Mohan said. August 1, 2009 8:11 AM Michael said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

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?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 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. Longtime readers will recall how I first met him.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Software By Rob

NOVEMBER 16, 2009

That’s when you find one or more (future) customers that help fund your product development in exchange for input into the process and free or highly discounted use of the software. Selling is hard and most people (especially developers) don’t want to do it. Check out my book Like this post?

Equity 42

Equity Software Review RSS Widget 42

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Software By Rob

AUGUST 18, 2010

CrazyEgg decided to drop its free plan in Jan of 2009 and they haven’t looked back. But a more important question to which I don’t have a good answer is whether the Free/Premium strategy leads to better or worse product development. If they do then the free offering is a mistake even in terms of product development.

Software Review 78

Software Review Software Revenue Cofounder 78

Software By Rob

NOVEMBER 18, 2008

It may wind up for sale on SitePoint , or it may be relegated to the bone yard of failed software products. The Upside The flip side to all of this is what you’ve already heard on the blogs of successful product developers. Once a product hits critical mass you’ve conquered the hardest part of the equation.

Software Review 42

Software Review Software Product Salary 42

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. Its an essential discipline of good software development, especially in startups.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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 243

Restful Silicon Valley Puerto Rico San Jose 243