Skip to content
PMPCAPM

Discretionary Dependencies

Discretionary dependencies are established by the project team based on knowledge of best practices, preferred sequencing, or past experience, even though other sequences are possible.

Explanation

Discretionary dependencies, also called preferred logic, preferential logic, or soft logic, are relationships that the project team chooses to implement but that are not physically or contractually required. They reflect the team's judgment about the best order to perform activities based on experience, industry best practices, or organizational standards.

For example, a team might decide to complete all design work before beginning any development work, even though some development could theoretically start before all designs are finalized. This sequencing preference creates a discretionary dependency. While it may reduce risk or improve quality, it is not an inherent requirement of the work.

Discretionary dependencies are important in schedule optimization because they can be modified or removed during schedule compression. When fast tracking, the project team looks for discretionary dependencies that can be relaxed to allow activities to overlap. However, changing discretionary dependencies increases risk, so the team must carefully evaluate the tradeoffs. All discretionary dependencies should be documented so they can be reviewed later if schedule changes are needed.

Key Points

  • Also called soft logic, preferred logic, or preferential logic
  • Based on best practices, experience, or team preference
  • Can be modified or removed for schedule compression
  • Should be fully documented for future review

Exam Tip

Discretionary dependencies are the ones you can change when fast tracking. They are based on preference, not physical or contractual necessity.

Frequently Asked Questions

Related Topics

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.