Example 1: Resolving dependencies
The dependent tasks have overlapping schedule dates. The "Create test plan" task has a slack or scheduling flexibility of one day, with relation to the project start date. Both tasks have the default constraint, As soon as possible. See Table 1 for the original schedule and the changes to the schedule when the project dependencies are resolved.
Elements | Before resolving dependency | After resolving dependency | ||||
---|---|---|---|---|---|---|
Start date | Finish date | Duration | Start date | Finish date | Duration | |
Project - Test plan | June 1 | June 5 | 5 days | June 1 | June 5 | 5 days |
Task - Create test plan (predecessor) | June 2 | June 4 | 3 days | June 1 | June 3 | 3 days |
Task - Verify test plan (successor) | June 3 | June 4 | 2 days | June 4 | June 5 | 2 days |
Add a new task to the project with a start date that is earlier than the project start date. The project start date changes to accommodate the new task. See Table 2 for the differences in schedule before and after you resolve the dependencies.
Elements | Before resolving dependency | After resolving dependency | ||||
---|---|---|---|---|---|---|
Start date | Finish date | Duration | Start date | Finish date | Duration | |
Project - Test planning | May 31 | June 5 | 6 days | May 31 | June 4 | 5 days |
Task - Create test plan (predecessor) | June 1 | June 3 | 3 days | May 31 | June 2 | 3 days |
Task - Verify test plan (successor) | June 4 | June 5 | 2 days | June 3 | June 4 | 2 days |
Task - New | May 31 | June 3 | 4 days | May 31 | June 3 | 4 days |
Example 2: Resolving dependencies on tasks with "Finish no later than" constraints
If a dependent task has a "Finish no later than" constraint, resolving dependencies might cause the constraint to break. See the scenario in Table 3.
Elements | Before resolving dependency | |||
---|---|---|---|---|
Start date | Finish date | Duration | Constraint | |
Project - test plan | June 1 | June 5 | 5 days | |
Task - Create test plan (predecessor) | June 1 | June 3 | 3 days | As soon as possible |
Task - Verify test plan (successor) | June 2 | June 3 | 2 days | Finish no later than - June 3 |
Example 3: Effect of resolving dependencies on tasks with no dependency
If tasks do not have dependencies, then resolving dependencies has no impact on the schedule of those tasks. In Table 4, see the schedules for "Other task 1" and "Other task 2" are unchanged before and after resolving dependencies.
Elements | Before resolving dependency | After resolving dependency | ||||
---|---|---|---|---|---|---|
Start date | Finish date | Duration | Start date | Finish date | Duration | |
Project - Test plan | June 1 | June 5 | 5 days | June 1 | June 5 | 5 days |
Task - Create test plan (predecessor) | June 2 | June 4 | 3 days | June 1 | June 3 | 3 days |
Task - Verify test plan (successor) | June 3 | June 4 | 2 days | June 4 | June 5 | 2 days |
Other task 1 (no dependency) | June 2 | June 4 | 3 days | June 2 | June 4 | 3 days |
Other task 2 (no dependency) | June 3 | June 5 | 3 days | June 3 | June 5 | 3 days |