At my last full time gig, I was basically in charge of R&D, programmer help desk and documentation. When a request for a doc was made, I would sit with the person who wrote the original piece of code and interview them. Then I would look over the code and its results. Next step was to write up a document based on what I heard and saw. I presented it to the original programmer and he would mention any changes needed. After the changes, the final doc was given in. Having a central person to do docs is a must, especially around programmers. Each programmer has his own style of programming, writing, speaking, etc. Having a central voice for the docs, especially one who can write is a must.
>I have said in meeting after meeting that we need to re-structure the >way we handle documentation, to no avail. So, I need evidence in my >favor. I know many of you out there work for development companies that >do it right. I need to know how your chain of command works as far as >management - development - documentation and distribution. I need to >know how much time and money your setup is saving you, so I can show >real-world examples of companies profitting from doing it right. It is >my thinking that we need a document master, with the ultimate authority >over documentation. This person needs to be working in the development >department, know the software, the system, the website, and the >documentation. Is this thinking right? Is there an even better way? > >Help, I am going to go nuts. > >Thanks in advance.... > >Nick > > > ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
