Rod at work (8/20/2015)
Matt Miller (#4) (8/20/2015)
Stephanie J Brown (8/18/2015)
Eric M Russell (8/18/2015)
Like I said earlier, if estimating is part guesswork, then the business should be the one providing the guesses. The business should define what is a Sale and then estimate the number of Sales per year. Then the developer can draft a physical data model and estimate storage required.How can a humble IT developer reliably guess how many sales orders will be entered a year from now, if the VP of Sales wouldn't even care to hazzard a guess?
+ 100!
Separately, I'd like to thank Matt for the Dilbert link (had to copy / paste, but it got me there). One of my teammates suggested we use $3,583,729.28 for every "no requirements" estimate we are asked for. I seconded the motion. :w00t:
Sorry Stephanie - I was trying to recreating the link markup by hand (apparently my work browser security prevents using any of the editing shortcuts already provided on the posting screens here. Let me see if I can fix that for ya.
Here's the link to the Dilbert cartoon. http://dilbert.com/strip/2009-12-07
The copy/paste worked, but thank you for fixing it for everyone else. I left that cartoon up all day - it just made me chuckle every time I saw it. We've been getting a lot of requests for SWAGs (silly or super wild anatomical guesses) lately, so this conversation and the cartoon have been SO appropriate!
Let the insanity continue. :crazy: (Humor helps)
Steph Brown