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
Mandatory Dependencies
Mandatory dependencies are those that are legally or contractually required or inherent in the nature of the work, often involving physical limitations.
Fast Tracking
Fast tracking is a schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration.
Sequence Activities
Sequence Activities is the process of identifying and documenting relationships among the project activities.
Schedule Compression
Schedule compression is a technique used to shorten or accelerate the project schedule duration without reducing the project scope.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Resource Smoothing
Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Part of
Schedule Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.