So here are two pieces of advice that I think are pretty useful in nearly all contexts within IT.
1) Don’t schedule a presentation to senior management on the same day you get braces glued to your teeth, unless you want the director of application development to whisper “I tawt I taw a puddy tat” whenever you leave the room. I wish that hadn’t just happened to me YESTERDAY.
2) Don’t use waterfall for software development projects. Unless you want to spend huge amounts of money, deliver nothing, and go down with the ship insisting you would have been successful if only the business hadn’t kept changing requirements. Flippin’ baby.
If you enjoyed this post, make sure you subscribe to my RSS feed!
Stumble it!
2 responses so far ↓
1 David York // Jun 19, 2008 at 9:20 am
Being a Business Analyst, I like requirements just most of the time there is too much or many requirements. The users want to control development. I want development to build something useful. But I still want to be employed. I like agile but like most others trying to understand where that line is between requirements and development.
Love the blog
2 David Christiansen // Jun 19, 2008 at 6:12 pm
I think Mike Cohn drew the line pretty darn well in User Stories Applied, which I recently reviewed. Check it out – requirements that don’t break your back when you lift them or your toes when you drop them.
Leave a Comment