Need suggestions for tools or (preferably) methods to track revisions made to software documentation, most of which are driven by biweekly updates
( Read more... )
It's really hard to get people to comply with policies, isn't it?dakiwiboidJanuary 14 2008, 17:50:57 UTC
Whatever solution you use, it'll definitely have to do the work for them, or those changes won't be recorded! I had the devil of a time even explaining how to turn on Track Changes in some offices I worked in. Sigh. May I suggest asking ljgenie?
You can check the .doc files into the same source protection environment that they use for code. We created a separate VSS database for documentation, and that's worked just fine.
Well, honestly, unless you use a software package for creating content that enforces "track changes", user behavior is always going to foil you.
You may not remember this, but my job at Sprint was to create a web-based Marketing and Sales Encyclopedia system for Sprint Business. We had over 6000 consumers of information and over 250 content providers from multiple locations and multiple departments. One of the lessons I learned from that experience was that the providers wanted to use a variety of applications to create their content. Now, you might not have that problem, but the point is that they will want to create it the way they want to create it and unless you've got some heavy backing, you'll have a problem enforcing any policy.
Keeping Track Changes turned on is a very simple thing, however. Check out this tip from TechRepublic: How to keep someone from turning off Track ChangesIn any case, no matter what software you use, you probably put together some sort of training session explaining things to your content providers
( ... )
Comments 4
Reply
Reply
Reply
You may not remember this, but my job at Sprint was to create a web-based Marketing and Sales Encyclopedia system for Sprint Business. We had over 6000 consumers of information and over 250 content providers from multiple locations and multiple departments. One of the lessons I learned from that experience was that the providers wanted to use a variety of applications to create their content. Now, you might not have that problem, but the point is that they will want to create it the way they want to create it and unless you've got some heavy backing, you'll have a problem enforcing any policy.
Keeping Track Changes turned on is a very simple thing, however. Check out this tip from TechRepublic: How to keep someone from turning off Track ChangesIn any case, no matter what software you use, you probably put together some sort of training session explaining things to your content providers ( ... )
Reply
Leave a comment