FreeLists / webproducers / [webproducers] deliverables and documentation

[Morry Galonoy <galonoym@xxxxxxxxxxxxx>]

Need some feedback on how people deal with deliverables and documentation
especially in terms of keeping them updated throughout the process.

I've seen/heard of so many ways to handle deliverables and I'm trying to
organized things for my jobs.  I've heard some people say that each
department should own their documents (e.g. design the design doc; IA the
site maps, use cases, requirements docs, technical the tech specs, etc.)
thus they should update and that makes sense to me. The bigger question is
during the dev. process invariably things change and it wouldn't make sense
to re do the entire site map once the site is 1/2 way through development.
So what do people out there do? Do you just append a change form to any
documentation?  

I think this can become a big issue when a third party is brought in for
testing and evaluation, usability testing, or as I've recently seen, an
internal department discovered their IT department would not approve a
project because they did not comply with internal standards.

Thanks in advance for the feedback.

Morry
__________________________________________________________________________
Too Many Messages? Try Digest Mode! simply send a message with "set digest" in 
the subject to webproducers-request@xxxxxxxxxxxxx

To subscribe or unsubscrbe to the webproducers list send a message with either 
"subscribe" or "unsubscribe" in the subject to 
webproducers-request@xxxxxxxxxxxxx

Questions and comments are welcome just e-mail me,
webproducers-admins@xxxxxxxxxxxxx   -Morry