From bogus@does.not.exist.com Thu May 22 14:36:21 2008 From: bogus@does.not.exist.com () Date: Thu, 22 May 2008 20:36:21 -0000 Subject: No subject Message-ID: in documentation version control, as does any other software version control system. The way you approach this depends on the desires of your work group, so truly you are developing your own process in your own way. Typically version control of documents during development as well as after release follows the versions of the software. Sometimes companies impose version control on the documentation only after a release, but this varies. Responses to this question are very welcome on the list, and if anyone has documents to share we can post them on the QPI SIG website. Ann Ann L. Wiley, Ph.D. Ann L. Wiley Consultants Inc. ann at annlwiley.com From bogus@does.not.exist.com Thu May 22 14:36:21 2008 From: bogus@does.not.exist.com () Date: Thu, 22 May 2008 20:36:21 -0000 Subject: No subject Message-ID: from my colleagues around the world who are also dealing with the "big ship, small rudder" syndrome. I have been a writer, senior writer, editor, help developer, and documentation manager for over 11 years (plus another 11 years of field service), but my most recent appointment presents numerous challenges at once (time zone differences, differing regional regulatory requirements, translation issues, and, of course, political/territorial challenges, among others). I hope to network with others who also feel that they get up each day, throw bricks in the Grand Canyon, and go home to prepare the next day's adventure. :>) Seriously, though, I look forward to participating in this group. Regards, Brian Hayes Quality Mgr. - Tubular Running Services (713) 693-4348 - office (713) 408-6049 - cell brian.hayes at weatherford.com From bogus@does.not.exist.com Thu May 22 14:36:21 2008 From: bogus@does.not.exist.com () Date: Thu, 22 May 2008 20:36:21 -0000 Subject: No subject Message-ID: -- June and July 1999, CIDM conducted a targeted study -- Ten companies and 30 individuals took part in the study. -- All of the participating departments are members of the CIDM -- a "good sample and quite homogeneous" [in their opinion] -- Includes ... additional ratios data gathered from 1993 to 2000 -- The summary contains additional data from 24 companies A critical thinker could question the size of the sample, whether the sample is representative, or the methods. But claiming it is anecdotal is a mischaracterization. In case a reminder is needed, "anecdotal" is a type of fallacy that generalizes about class based on a story about a *single* member of that class. best, --dave J. David Blaine, PMP CSQE San Diego, CA > -----Original Message----- > From: bounce-stcqsig-l-319032 at lists.stc.org [mailto:bounce-stcqsig-l- > 319032 at lists.stc.org] On Behalf Of Bill Swallow > Sent: Tuesday, March 27, 2007 9:16 AM > To: STC Quality and Process Improvement SIG Discussion List > Subject: [stcqsig-l] RE: Explaining the writer:developer ratio > > This is the second time within a working week that I've seen this > paper referenced, and the second time I'll reply that the information > is interesting but anecdotal at best when it comes to properly scoping > staffing needs. >