If we don't have specs, then the client can drag the project beyond what we think the limits are.
If there are specs in writing that both parties agree on, then changes cost more money. At 12:04 PM 1/11/2002 -0500, you wrote: >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. `--------' > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
