February 14, 2005
"Don't solve problems as stated" for developers

Don Normans "Never solve the problem as stated" rule has a corollary for software development: Don't write functional specification documents. Clearly, the functional spefication document is just the kind of problem statement Norman wants you to discard. So if you shouldn't solve the problem like that, you probably shouldn't write the specification in the first place.
This argument obviously is also expressed in various XP practices.

Posted by Claus at February 14, 2005 05:37 PM | TrackBack (0)
Comments (post your own)
Help the campaign to stomp out Warnock's Dilemma. Post a comment.

Email Address:


Type the characters you see in the picture above.

(note to spammers: Comments are audited as well. Your spam will never make it onto my weblog, no need to automate against this form)


Remember info?