Project Dependencies on the Gantt Chart
TL;DR
Project dependencies on the Gantt chart link projects and help define how their dates relate to one another. Wrike supports four dependency types: Finish to Start, Start to Start, Finish to Finish, and Start to Finish. Project dependencies are independent of task dependencies.
Table 9. Availability - Legacy plans
| Availability: Legacy Professional, Legacy Business, Legacy Enterprise.; Unavailability: Legacy Free.; |
| Availability: Team, Business, Pinnacle, Apex. ; Unavailability: Free; |
Overview
Project dependencies specify relationships between projects. Use them to indicate when one project should begin or end in relation to another project.
On the Gantt chart, project dependencies appear as lines connecting project bars. You can create project-to-project dependencies directly on the Gantt chart.
When working with project dependencies in the Gantt view, projects and their milestones are displayed by default, while tasks are collapsed. All milestones within a project appear on the project bar. Expand a project to view the tasks and milestones within it.
Note
Project dependencies are independent of task dependencies. Creating a dependency between two projects doesn't create or modify dependencies between the tasks within those projects.
Types of Project Dependencies
There are four types of project dependencies you can create in Wrike:
Finish to Start
Project B can't start before Project A is finished.
This type of dependency occurs when the initial project must be completed before the next project can begin. If Project A is completed behind schedule, Project B can't start before Project A is finished.
Start to Start
Project B can't start before Project A starts.
A Start-to-Start dependency occurs when a secondary project can't begin until the initial project begins. The two projects don't have to begin at the same time. Project B can begin after Project A, as long as Project A has started.
Finish to Finish
Project B can't finish before Project A is finished.
A Finish-to-Finish dependency means the initial project must be completed before the following project can be completed. Project A and Project B may take place at the same time, but Project B can't finish before Project A.
Start to Finish
Project A can't finish before Project B starts.
In a Start-to-Finish dependency, the initial project can't be completed until the secondary project has begun. However, Project B doesn't have to finish at the same time that Project A begins.
Rescheduling Projects with Dependencies
When you change the dates of a project that is a predecessor in a dependency chain, the dependent project is not automatically rescheduled. Instead, the downstream project shows the impact of the date change so you can review and adjust its dates as needed.
Reschedule Nested Subprojects
If the project you're rescheduling contains subprojects, you are prompted to choose whether to reschedule the subprojects. In the prompt that appears, choose one of the following:
-
Apply to shift the nested subprojects by the same amount as the parent project. If you select Apply, review the confirmation showing the number of projects that were rescheduled.
Note
Rescheduling a project only changes project dates. Tasks within nested subprojects aren't automatically rescheduled. Similarly, changing the dates of a project doesn't automatically reschedule projects that depend on it.
What's Next?
Was this article helpful?
Thank you for your feedback.
Thank you for your feedback.
Please sign in to leave a comment.