Project 2000. Moving From Microsoft Project, страница 6

Split In-Progress Tasks – Select the Split in-progress tasks check box to allow rescheduling of remaining duration and work when a task slips. If you select this check box, when you update task-tracking information, you can enter the date you stopped work on the task and the date you resumed work. Microsoft Project reschedules the remaining duration and work. If the check box is cleared, you cannot edit the Stop and Resume fields when you update task-tracking information. This is a local setting saved with the active project.

Leveling calculations – This option delays or splits tasks or assignments to eliminate resource conflicts. The Automatic option causes leveling to occur whenever you make changes to your schedule. The manual option levels whenever you click Level Now.

Updating task status updates resource status – Select this option to have Microsoft Project automatically calculate the actual and remaining work for resources assigned to the task as you enter task percent complete information in your schedule. If you select this check box, Microsoft Project recalculates the actual work whenever you enter information into the Percent Complete, Actual Duration, or Remaining Duration fields. If you don't select this check box, you must manually enter values in the Actual Work field for resources. This is a local setting saved with the active project. (See also Percent Complete and Actual Start.)

Tasks will always honor their constraint dates – When this option is selected, two things occur. First, leveling cannot make adjustments to tasks that would violate their constraints. Second, a successor task must honor its constraint even if it means violating a relationship with a predecessor. When this option is not selected, leveling can adjust tasks regardless of their constraints. Also, a successor can be scheduled as its predecessors dictate, even if it means that the successor constraint will be violated.

Calendars

Project Calendar – The project calendar is used to schedule summary tasks, fixed duration tasks, tasks with no task calendar, and tasks with no assignments.

Task Calendars – Task calendars impact the dates that a task is scheduled for. For example, setting Wednesday as a non-working in a task calendar day will cause a 5-day duration task that starts on Monday to finish the following Monday. This is true even on a fixed duration task. Task calendars are covered in more detail later in this course.

Resource Calendars – Resource calendars impact the dates of fixed units and fixed work tasks. For example, you cannot edit time-phased work for days specified as non-working in these calendars. (Note: You can, of course, edit actual work on these non-working days.)

Tasks

Dependencies – Dependencies specify the manner in which two tasks are linked. Because Microsoft Project must maintain the manner in which tasks are linked, dependencies can affect the way a task is scheduled. In a scenario where there are two tasks, the following dependencies exist:

n  Finish to Start – Task 2 cannot start until task 1 finishes.

n  Start to Finish – Task 2 cannot finish until task 1 starts.

n  Start to Start – Task 2 cannot start until task 1 starts.

n  Finish to Finish – Task 2 cannot finish until task 1 finishes.

Dependencies may also include lag. This value may insert time into the relationships above.

Constraints – (see also, tasks will always honor their constraints.)  Constraints allow you to set the way you want to constrain the start or finish date of a task. The following constraints can be set on tasks:

n  As Late As Possible – Sets the start date of your task as late in the Project as possible, without pushing out the Project finish date.