Example Mandatory dependencies
![Example Mandatory dependencies “I cannot test the software until I code the software.” This expression describes which of the following dependencies? a. Discretionary b. Rational c. Preferential d. Mandatory or hard Answer: d. Mandatory or hard Mandatory dependencies Mandatory dependencies may be required contractually or be inherent in the nature of the project work. They describe a relationship in which the successor activity cannot be started because of physical constraints until the predecessor activity has been finished. For example, software cannot be tested until it has been developed (or coded). They should not be confused with assigning schedule constraints in the scheduling tool. [Planning]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiP2jyZVN9gX77eZGizcvMCIwCJUJnCrDsQTS2TYrbxpEVKFvwxbsIFxjv23PDpG4ZrH3CezWVcxYfdiyRPuxfDWjCw4XSqojgwDlQiWjyecshONbCXfmEd1B7fU1Zt0BV9JUoLwqRLsnwu/s583/images+%252872%2529-01.jpeg "Example Mandatory dependencies “I cannot test the software until I code the software.” This expression describes which of the following dependencies? a. Discretionary b. Rational c. Preferential d. Mandatory or hard Answer: d. Mandatory or hard Mandatory dependencies Mandatory dependencies may be required contractually or be inherent in the nature of the project work. They describe a relationship in which the successor activity cannot be started because of physical constraints until the predecessor activity has been finished. For example, software cannot be tested until it has been developed (or coded). They should not be confused with assigning schedule constraints in the scheduling tool. [Planning]")
“I cannot test the software until I code the software.” This expression describes which of the following dependencies?
a. Discretionary
b. Rational
c. Preferential
d. Mandatory or hard
Answer: d. Mandatory or hard
Mandatory dependencies
Mandatory dependencies may be required contractually or be inherent in the nature of the project work. They describe a relationship in which the successor activity cannot be started because of physical constraints until the predecessor activity has been finished. For example, software cannot be tested until it has been developed (or coded). They should not be confused with assigning schedule constraints in the scheduling tool. [Planning]