I need some help in convincing my boss that it would be a real advantage
to write specifications for projects before starting them. I think he
thinks they are a waste of time but I think they can significantly improve
application quality and time to market.
Are their any resources I can use to prove this to him? What do other
companies consider standard proceedure when it comes to writing
specifications?
I'm at a bit of a disadvantage here because, although I have the more
professional experience than the other programmers on the team I am the
newest member.
Any suggestions and ideas would be greatly appreciated.
Thanks,
Kristine C. Hege [EMAIL PROTECTED]
Database & Applications Specialist Phone: (802) 463-2111
SoVerNet Inc. Ext: 105
5 Rockingham St.
Bellows Falls, VT 05101
--------------------------------------------------------------------------
_ .----. . - .
PROGRAM (PRO'-gram') [n] A magic spell cast over a |C>_.|.:' .:. .
computer allowing it to turn one's input into error __|____|__ `:. O_/
messages. [vi] To engage in a pastime similar to | ______--| \/M
banging one's head against a wall, but, with fewer `-/.::::.\-' _/ \_
opportunities for reward. `--------'
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
