The task schedule contains information about the start and
finish dates and duration of project tasks. Typically, a project manager creates a schedule in two steps: first adding tasks without assignments, and then assigning team members (resources) to those tasks. Note: The first step can be accomplished using a template or by importing a schedule as well.
Each step has specific impacts to how tasks are scheduled. Initially, tasks without assignments are scheduled based on provided task information: planned start and finish dates, duration, and any constraints or dependencies with other tasks. At this stage the scheduling is relatively straightforward and predictable.
Once you begin assigning tasks to team members, the schedule can change in ways you may not anticipate because various aspects of tasks are interrelated and a number of factors contribute to how tasks are adjusted from their initial state. These factors include task type, number of assignees, and assignee calendars and related calendar exceptions. Note: An edit to a task can result in schedule adjustments. See (popup).
Here is how the various aspects of a task impact the task schedule:
- On Creation—When tasks are first created, basic scheduling is based on information provided by the project manager, including planned start and end dates, duration of the tasks, and any task dependencies or constraints. For more information, see Adding a Task.
- On Assignment—As team members are assigned to a task, scheduling is adjusted, based on a number of factors including:
- Task Type
Task type determines which task property (duration, resource allocation units,
or planned work) remains fixed when another property changes. For more
information, see Task Types - Overview.
- Workweek Calendar
The Workweek Calendar defines the days and hours task work can be performed. For scheduling purposes, the days/hours of work that a team member can perform on a task are determined by the
workweek calendar and are used for task duration calculations. For more details, see Workweek
Calendar
- Nonworking Time
Nonworking time is a calendar exception designed to adjust the hours team members can be assigned to tasks due to specific events or
occurrences. If you assign a task to a resource during a period when they have nonworking time scheduled, the task is adjusted based on their available working hours. For more details, see Nonworking Time Overview.
- Dependencies
Some tasks cannot start until other, related tasks have started
or finished. Successor tasks are scheduled based on
the start or finish dates of their predecessors. Lag or lead time can be
built into the dependency to specify an overlap or delay between predecessor
and successor tasks. For more details,
see Task Dependencies Overview and About
Lag and Lead Time.
- Constraints
Constraints can be applied to tasks to force them to start
or end on a particular date. Constraints can override normal task scheduling. For more information, see Task
Constraints.
- Effort Driven
With effort-driven tasks, duration is automatically reduced or increased as
team members are assigned or removed from the task. For more information,
see Assignments and Effort Driven Tasks.
An exception is fixed duration, effort driven tasks. With these, duration remains constant and resource allocation units change as team members are assigned or removed. For details, see Assignments and Fixed Duration - Effort Driven Tasks.
Related
Topics: