Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

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." The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? You can tell a lot about a company from their deployment flow.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Thank you so much!) Take a look and let me know what you think.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, No departments The Five Whys for Startups (for Harvard Business R.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

MAY 27, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, No departments The Five Whys for Startups (for Harvard Business R.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 15, 2009

As a consumer internet company with millions of customers, it may seem to have little relevancy for an enterprise software company with only a handful of potential customers, or a computer security company whose customers demand a rigorous audit before accepting a new release. June 22, 2009 10:07 AM Khris said.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. Labels: five whys root cause analysis , product development 8comments: William Pietri said. December 9, 2008 3:10 AM Amy said.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

AUGUST 1, 2009

And in some cases, they disregard the results of customer focus groups if they sense that the results are incongruous. Not everything has to follow lean startup and customer development principles, and I write that as a devoted practitioner of both. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo (and a call for he.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo (and a call for he.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. However, a commitment to quality alone is not enough.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 2, 2009

Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? I have not read the previous post(s) on 5 why's (about to now though.),

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Having early customers means balancing the needs of your existing customers with the desire to find new ones.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

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

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Nonetheless, I want to talk about a dysfunction Ive seen in several startups: they are literally refactoring themselves to death.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79