Dependency Definition - A dependency describes the relationship among activities and specifies the particular order in which they need to be performed. Dependencies arise in every decision making, planning and developing process and are ideally predetermined. Tasks can be successors and predecessors to other tasks whereby the instant of each execution may be aligned accordingly.
To configure a dependency the type of reliance between a pair can be further defined by one of following relationship models:
The finish-to-start dependency is the most common relationship between two tasks. The predecessor task must be finished before another task, the successor, can start.
The predecessor must have started before the dependent task can start. The finish of either task is unaffiliated.
The successor can only finish after the predecessor has finished. The successor’s start is doesn’t rely on the predecessor and can begin before, after or at the same time.
The start-to-finish is the least common relationship between two tasks. The successor has already started and cannot finish until the predecessor has started as well.
Common challenges appear when dependencies are connected to external contributors. These so-called risky dependencies may occur e.g. when software from a third-party represents a key component to your product or a task dependency has a constraint and its completion process cannot be forecasted. Another difficulty may be to identify dependencies in the first place. It is important to stay on top of them when a project gains traction and becomes more complex.
Visualizing dependencies asserts the task management and timeline of any project schedule. Especially when managing a cross-functional team it is crucial to substantiate the level of awareness by including dependencies and status reports into e.g. the product’s roadmap. However, there are multiple approaches in doing so. Whether depicting dependencies in a Gantt-Chart, diagram, table or with other means, it will enable the team to reevaluate commitment and to object to impractical measures if necessary.
From product management to prioritization, roadmapping, decision making, and strategy, we’ve got you covered.