Dances with Bugs

I just finished reading the following article: http://borisgloger.com/en/2010/11/29/scrum-alliance-and-scrum-org-yesterdays-concepts-do-not-solve-todays-problems/ I was going to comment there, and then decided it was really worth its own blog post.
Full disclosure: I am a CSM and a CSPO, and (while not a CST) have co-taught CSM courses in the past. I firmly believe that good education is essential to getting started well with Scrum, and that having some way to identify baseline knowledge and expertise...

There is a long-standing belief among the planners and architects of the software world that coding is like the work of a brick-layer. Misled, perhaps, by the fact that the elements of computer languages are few and identical, they model the writing...

I propose that the real issue is that design is not really a beneficial activity in software development, and to say "The Source Code Is The Design" is trying to use semantics to gloss over the issue.
I feel this is an important distinction if the goal is to remove the "design" stage from the software development process. Rather than being afraid of being accused of "not doing design", we need to turn the debate around to be "Why should we do design...

Walden Mathews, talking about specifications documents and functional specs and the like, says:
"Specification" is interesting nomenclature, because it's really the lack of specific-ness that keeps it from being the product.
From: http://c2.com/cgi/wiki?TheSourceCodeIsTheProduct, which I got to from http://c2.com/cgi/wiki?TheSourceCodeIsTheDesign....