Microsoft Project Plan Templates Best Practices

Note:  Accolade's integration with Microsoft Project is an optional Accolade component that you may not have access to. To implement this solution, contact Sopheon Customer Support.

Keep the following set of best practice recommendations in mind when using Microsoft Project files as templates for deliverables and activities within a model:

• Add Models to New Project Plans - Add models to new Microsoft Project files only. If you insert a model into an Microsoft Project plan that already contains data, the model completely replaces the existing plan.
• Use Descriptive and Unique Template Names - Users need to be able to clearly distinguish between the different project plans and their uses within a model. For example, Process Designers building models need to distinguish between templates used for particular stages or gates, if you choose to make project plans more granular than for an entire project.
• Have Plan Owners Refresh Project Plans - When Process Designers update a model to contain new deliverables or activities, project plans based on the model are updated when refreshed if the plan contains the Stage summary tasks that contain the new deliverables or activities. Deliverables and activities that are moved to a different stage are moved within the project plan as well, as long as the plan contains the Stage summary tasks.
• Create New Project Plan Templates if Duplicating Models - After a model is saved and in use, you can no longer add stages or gates to the model. Duplicate the model to add stages and gates, and create new Microsoft Project plan templates to include the model changes.