A small mix-up

A colleague of mine was reading through Toby's adventures and asked why, in the name of all that is good, did our hero start coding without fully understanding the requirements. It was meant to be a mistake — he's not perfect :) I'm certainly not advocating jumping into object model design without first having a list of user stories.

This series of posts is supposed to illustrate a way of tackling a small project and hopefully demonstrate a few techniques and methodologies at the same time. I figured I might throw in some realism (things rarely go perfectly in the real world) but since it's just a story maybe we'll keep things in fantasy land from now on.

Comments

• Anonymous
  June 21, 2007
  The comment has been removed
• Anonymous
  June 21, 2007
  Perhaps 'fully' was the wrong word to use. How about 'make a good attempt to understand the requirements'?If you scan through the user stories after they've been fleshed out and estimated, it's obvious that the object model Toby so merrily started writing earlier won't be to handle several different things. Even his original list of user stories shows that he hadn't really spent enough time considering what the app needed to handle.