In major projects with more than a few people, documentation gets a complicated structure. Documentation structure is all important but some lack of tracking document versions may turn all of it into a mess. To avoid this kind of chaos documentation versioning standards should be decided and shared with all project team.
Real life example from my last project; creating document versions while updating them internally before sending to customer is also important though sending the first customer version as v5. or v7.2 is not appropriate. So internal versions may be tracked as v0.1, v0.2 etc and then customer version may start with v1.0.
No comments:
Post a Comment