Your initial thought that being “good enough” is the enemy of being great is a natural one. It’s the first thing people hear — they don’t want to work on software / products that are just “good.” They want to build the coolest thing ever!

But, as you point out the fantastic thing about this approach is that you are building something great. It’s just going to happen in the view of a community and over the course of several releases instead of one giant “thing” in the style of Win95 or something of the like.

Attitudes are changing in software product development – and it means great things for organizations that can harness the benefits of agile and really make it work for them.

Everyone forgets that when you are building software, you aren’t doing brain surgery. You ship a release with some bugs or messages out of place, it really doesn’t matter – you can fix those and turn them around in a day or a week.

As you note, “Good Enough” should probably be called something different to qualify it even more and erase some of those concerns of being 1/2-assed or lacking quality. I really like your “Good Enough for Right Now,” or because I love my acronyms – GEfRN =)

Thanks again, Scott! I look forward to more chats / discussions!