Planual rules regarding revision tags.
6.01-01 Naming Convention
Be consistent with how you name your revisions. It's advised to use a Major.Minor nomenclature (R1.01, R1.02, R2 etc.). Remember, the description is permanent and can't be changed - be careful!
6.01-02 Create a revision tag at least once a day
During periods of intense development, ensure revision tags are created regularly and tested against a "shell" model.
bestPracticesArticles
6.01-03 Revision documentation
If you need a broader description of revisions, create a normal list (non-production data) and then store the revision details in a module with other fields such as Approved date, User story, Developer, Tested date, Sign off date, etc.
6.01-04 Synchronize Production regularly
Minimize the risk of synchronization errors by synchronizing regularly to keep Production and Development aligned.
relatedToRule
bestPracticesArticles
6.01-05 Shell test model
Set up a "shell" model (using create from revision) containing no production list members on which to test revisions and synchronize regularly.
