Programme Plan Workbook

This page provides a rolled-up view of milestones and allows editing of the workplan at both programme level and for each of the entities in the programme contents.

• The overview tab combines all of the milestones into a single Gantt view. The milestones comprise those defined at programme level and those from entities in the programme contents.

• The first tab after the Overview tab provides a means to edit the programme level workplan.

• There will be a further tab for each entity in the programme contents allowing editing of the workplan for that entity.

• In each workplan, the gantt display defaults to a daily view. Use the drop-down at the top right of the task pane to switch to a weekly, monthly,or yearly view or back to a daily view.

• Adding and Edit tasks: Click on ‘Add Task’ to add a new task to the plan. Click on any of the task cells to highlight it and make changes.

• Deleting tasks: Click on any of the tasks to highlight it and click on ‘Delete Task’ at the top of the task pane to delete it. Deleting a parent task, deletes all tasks beneath it.

• Reordering tasks: Drag and drop tasks up and down to change their order. 

• Effort has no impact on timelines.

• Effort is calculated with the region's working hours * the duration of the task * the number of resources assigned to the task.

• Further to the above effort calculation, if no resource is assigned to the task, it assumes 1 resource.

• If the task’s region does not have any assigned working days, it is given a M-F 8-hour schedule.

• Duration is calculated with region working days and holidays in mind.

• Task scheduling respects its predecessors and its parent's predecessors.

• A task becomes a summary task when another task is indented into it.

• A summary task takes the earliest start date and end date of its children.

• If a child has an MSO constraint and is the earliest start date of its siblings, the summary task takes the MSO constraint as well.

• If a child has an actual start or end date, it uses those dates.

• A summary task’s percent complete is the average of all its children's percent complete.

• A summary task’s effort is the sum of all its children's effort.

• A summary task cannot be a predecessor of any of its children but can be the predecessor for a task or summary task outside of its tree.

• If a milestone is turned into a summary task, it is automatically changed to a task.

• If a summary task is given a predecessor, all its children inherit the predecessor.

• External tasks are tasks that have been added to a task plan from another task plan.

• External tasks are not editable but can be reordered and deleted just like any other task.

• When a task plan is loaded, it checks all external tasks to see if they have been updated in their original plan. If an external task has been updated, a prompt will appear allowing you to update the task if needed.

• When an external task is updated, it triggers a timeline reflow. The reflow will not update any external tasks.

• Giving a task a predecessor means that task cannot have a start date before any of its predecessors unless the task has the MSO constraint.

• A task can have multiple predecessors.

• If it has multiple predecessors, its start date will be the latest end date of its predecessors, unless the task has the MSO constraint.

• MSO - Must Start On. Task dates will not be influenced by any other tasks.

• ASAP - As Soon As Possible. Task dates are set to earliest possible date based on its predecessors.

• Export to MSP: The workplan can be exported to MSP. Click on ‘Export MSP’ at the top of the task pane. An XML file will be placed in your download folder. When opening the file in MSP, be sure to set the file type to XML.

• Import from MSP: Save the file as XML format in MSP. In the PPMAnywhere workplan click on ‘Import MSP’ at the top of the task pane and select the XML file saved in MSP.