Workfront Predecessors & Task Constraints

Understanding Predecessors

Predecessors set the order of tasks

• Chains of predecessors set the length of the project.
• Allows groups of tasks to shift automatically.

Predecessors in Action: Standard

Sets the order in which tasks are to be done.

• Develop Initial Invite Copy must finish before Approve Initial Invite Copy can start.

Predecessors in Action: Lag Time

Add gap days between tasks.

• Present Design Concepts must start 5 days after Create Design Concepts is finished.

Lag Time Uses Cases

• Create additional buffer time between tasks.
  • Account for SME/Partner approval.
• Reschedule late tasks to bring them current.

Predecessors in Action: Negative Lag Time

Sets a task to run before its predecessor.

• Send Attendee/Staff Email must start 3 days before Day of Tradeshow (Task 1) is finished.

Negative Lag Time use case:

• Quickly create a successor relationship to a fixed date.
• Ad-hoc tasks tied directly before the event date.

Predecessors in Action: Multiple Predecessors

Set up multiple tasks to lead up to a single activity.

• Approve Final Copy (Content) and Approve Design Concepts must finish days before Edit Design Concepts can start.

Multiple Predecessor use cases:

• Easier to delete sections without affecting the entire project.
  • Deleting booth tasks or other event materials.
• Set tasks to run parallel to each other.
  • Content & design.

Understanding Dependency Types

Determines when a task should start or finish with relation to other tasks.

• Dependency Types:
  • Finish-Start (fs)
  • Finish-Finish (ff)

Finish-Start (fs)

The default dependency type.

Finish-Finish (ff)

Use to set tasks to run in parallel.

• Even if tasks have different duration days, they will finish at the same time.

Understanding Task Constraints

Task Constraints

• Must Finish On
• Must Start On
• As Soon As Possible
• As Late As Possible

Constraint: Must Finish On

• Assigns a due date regardless of PTO, weekends and holidays.
• Also prevents the task from shifting with the rest of the project.
  • Including if someone adds PTO after the fact.

Two ways to set Must Finish On:

• Set task constraint in the Task Constraint column.
• Manually enter the due date.

The start date is determined by the task’s duration days.

Constraint: Must Start On

• Assigns a start date regardless of PTO, weekends and holidays.
• Also prevents the task from shifting with the rest of the project.
  • Including if someone adds PTO after the fact.

Two ways to set Must Start On:

• Set task constraint in the Task Constraint column.
• Manually enter the start date.

  The due date is determined by the task’s duration days.

Constraint: As Soon As Possible (ASAP)

Default task constraint.

• Tasks will shift automatically based on weekends, holidays and PTO.
• Tasks will also shift based on rescheduled predecessor tasks.

As Soon As Possible (ASAP) in action:

Tasks without a predecessor will start at the Planned Start Date of the project. 

As Soon As Possible (ASAP) in action:

Tasks will move adjacent to their successor task.

Constraint: As Late as Possible (ALAP)

Tasks will shift automatically based on weekends, holidays and PTO. 

• Tasks will also shift based on rescheduled successor tasks.

As Late As Possible (ALAP) in action:

Tasks will move adjacent to their successor task.

As Late As Possible (ALAP) in action:

Tasks without a successor will finish at the Planned Completion Date of the project.

Understanding Default Constraint Preferences

Ever wondered why the system sets the As Late As Possible constraint for a new task?

Answer: Your project may be scheduled from Completion Date.

Click Edit to find out!