A project becomes more readable when the expected results have an identity and a person in charge. In Orchestris the deliverable helps connect what needs to be delivered to the work needed to get there.
Create and update a project
- Open Projects and check that the project does not already exist. In the new registry, fill in the name, summary code, status and expected notes.
- Choose a stable code and a name that will be understandable to the people who will use planning, deliverables and reports.
- Save and check the project in the list. Open the general data edit to verify that the values have been preserved.
- Complete budget, users, deliverables and activities separately: creating the master data is not the same as already having an executable plan.
Deliverables: identity and responsibility
- Open Deliverables from the project and identify the deliverable to manage. Use document code, identifiers and name to avoid editing a similar line.
- In the tab, check EDU, PIC manager, category, dates and deadlines present. Distinguish estimated end, actual end and reference deadline.
- Fill in only verified data and save. The association of the activities necessary for the deliverable occurs in the dedicated functions.
- Reopen the result and check the data, related activities and position in the plan. A deliverable lacking the necessary work can give an incomplete reading of the project.
Putting this into practice
Before breaking down a project into tasks, clarify the verifiable outcome and who follows its completion. This choice also makes the subsequent reading of the deadlines more useful.
Learn more about Orchestris.
Comments and questions
Do you have a question about this topic? Open the discussion with a comment.