How it's done
- TAGS:feature, procedure, project
- IT TOPICS:Development
This pilot fish brags that he has worked on a software project that finished on time, on budget and with only "I thought you wanted ..." problems when it was shown to the customer -- and no problems when it was delivered.
"Not possible, you say?" asks fish. "Well, I do grant it was a special case: The app was for the regional president."
There's also a standing procedure for change requests, and this time, it was actually enforced.
The key is the next-to-last step in the change-request procedure: The manager asking for the change has to go to the business sponsor of the project and explain the change, along with why it's important enough to delay delivery of the sponsor's application.
And when the sponsor is the regional president, well ...
"For some reason, almost all of the 'gotta have now' changes got to that point and suddenly became 'next release,'" fish says.
"We just sailed along with the original design and the few changes requested by the president."
Sharky has designs on your true tale of IT life. Send it to me at sharky@computerworld.com. You'll get a beautifully designed Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Now you can post your own stories of IT ridiculousness at Shark Bait. Join today and vent your IT frustrations to people who've been there, done that.
Free Insider Guide
