I'm not sure that OP's use of DRY (which seems to be about setting requirements) is the same as is referenced in the CodingHorror article (which is more about coding style and avoiding multiple modules that accomplish the same task)

That's kind of the idea. Reappropriating the coding best practices into higher level project management ideas is the premise of the post.

Ha. I totally missed that. Makes sense.