The Project Schedule list allows you to quickly and easily create a hierarchical (phases, milestones, iterations, summary tasks and project tasks) work breakdown structure (WBS) that allows values (% Complete, Late flag, Planned and Actual Durations, Costs and Dates etc) to be propagated, aggregated and auto-calculated up the hierarchy as the project progresses.
The Project Schedule list maintains consistency between dependent items in the hierarchy. Changes to a parent or child item can be made to roll up or down the hierarchy. Summary Items display aggregated information about their immediate child items. For a full description of the columns and how they might be automatically updated, please see Project Schedule Columns.
|
Note: |
Microsoft Project is not required to use the Project Schedule list. You can manually populate the Project Schedule using the supplied views. Whilst the Project Schedule is based on Microsoft Project, you should be aware that they do not have the same scheduling engine. |
The project schedule list can be created just like any other BrightWork list and includes a number of views designed to support managing single projects. Some of the views include title bolding and indenting to aid with visualizing the project hierarchy. The Project Schedule list also includes structured Gantt views generated with the List Gantt View web part.
With the Project Schedule list, you can schedule your project tasks in Microsoft Project, import the project file and the structure is automatically recreated in the Project Schedule list. From there on in, you manage and update the project in the Project Schedule list (with team members being responsible for maintaining their own work items). Project structures can also be created from scratch.
One key benefit of the Project Schedule is that, when the project is recalculated or rescheduled, consistency is maintained between dependent items in the hierarchy. A simple example of this would be that if the planned finish date or due date if an item was earlier than today, the item would automatically have its status updated to (2) Late. This status change would also happen in all parent items. For a full description of the columns and how they might be automatically updated, please see Project Schedule Columns.
The Project Schedule list contains 7 content types . These content types are designed to represent a level in a project hierarchy.
The BrightWork Project Schedule uses quite generic titles to describe elements in the hierarchy . These can be renamed to suit local practices. Whilst the Project Schedule list contains 7 content types, there are really 3 list types that you need to be aware of:
Project Schedule Summary is where all the data in the project rolls up to. It is automatically created and can only exist once in the Project Schedule list.
Project Schedule Summary Task (Layers 1 to 4 in the hierarchy diagram) display roll-up data from their immediate child items (which can be other Project Schedule Summary items or Project Schedule Task items). This data is system generated and is displayed in an uneditable section on the item form.
The Project Schedule Phase; Project Schedule Milestone; Project Schedule Iteration; and Project Schedule Summary Task content types are summary items and all have the same columns and layout. The summary information displayed is an aggregation of the information displayed in certain columns in the immediate child items (which may also be summary items).
Project Schedule summary tasks include a Child View web part that displays and links to the immediate child items.
Project Schedule Task are the actual units of work in the project. The information entered into a Project Schedule Task is extremely important as it rolled up to the immediate parent. There are two types of Project Schedule Task:
Project Schedule Tasks
Project Schedule Document Tasks
