• Scrum - the bright light of scrutiny on your organization’s processes and methods
• Pitfalls when trying to adopt agile development
  
• An interesting technique for refactoring convoluted legacy code (hat tip: Kevin Rutherford)

Another recent article (which I can’t find right now) talked about how problems with adopting agile suggest problems with the organizational structure more than with agile development.  That is, of course, a variation on the “No True Scotsman” argument, but even so, I can say that in my experience, it is true - the two organizations where agile has failed has done so because of deep organizational flaws.   I can say this because these experiences were several years ago, and both of these organizations have failed to deliver the software they promised, or even an acceptable subset.

This is the epitaph to my old artile: How Agile Software Development Ruined My Career (Sort of)

Seth wonders if ‘Good enough will be the next big idea‘.   This aligns well with Kathy Sierra’s writings on featuritis, and the general agile principle of “Good Enough” software.

I would say that this will only be true if “good enough” sells to the general public, and they buy “good enough” merchandise on a satisfyingly regular basis.  Because one of the ways that salespeople make money is by convincing potential buyers that what they have is not “good enough”.