Reusing standard tasks helps maintain common criteria across projects. However, variations remain necessary when the actual work changes: they must be recognizable and consistent with the deliverable concerned.
Associate standard activities
- From the deliverable open the standard task management. Verify that the result and project displayed are those of the tutorial.
- Select the category consistent with the work required and check the activities proposed by the library.
- Complete the information requested by the form, then save. The availability of the category does not replace the verification of the activities actually necessary.
- Re-read the breakdown in detail and in the Gantt. Check that the sequence is understandable and that no duplicate tasks have been added.
Custom activities and variations
- Open custom task functions on the affected deliverable. Use them when the work is not correctly represented by the standard library.
- Describe the task with a recognizable result and fill in the required parameters. Avoid generic names that hide content or responsibilities.
- Save and check the association with the deliverable. Keep local plan modification separate from standard category maintenance.
- If you remove a task, first check connections, loads and progress. After the change, re-read the consequences on the plan.
Putting this into practice
For a recurring delivery, use a shared basis and see what differs in your specific case. Maintain the readability of the plan when introducing specific activities.
Learn more about Orchestris.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.