Note: Dependencies involving phases are not recommended, since unexpected simulation results can occur. In TeamPort dependency is more than sequence, and implies a demand for coordination. A Phase to Phase dependency implies a dependence between every activity upstream with every activity downstream. Everyone coordinating with everyone else! Try to be more precise in representing which activities have need to coordinate with specific other activities.
After drawing a dependency from one activity to another, the dependency will also be shown in the Activity detail pane. The shape of the dependency can be edited by selecting one of the types below, or by customizing a shape with the Dependency editor in the Dependency Detail Pane.
|
Dependency |
Definition |
Example |
Depiction |
Before |
All work must be completed in the source Activity or Phase before the dependent activity or Phase can begin. Similar in schedule to classic Finish to Start constraints, though a demand for coordination of all information and outcomes is also implied. |
A machine must be fully assembled before it can be used |
|
Early |
Work can progress in the source segment earlier than in the dependent segment. Later, as the source segment is nearer to completion, the dependent segment can progress rapidly towards completion. |
Early stages of development can begin based on a preliminary design; however most of the design work must be complete before development can really get under way. |
|
Pace |
Work can progress as long as the upstream activity makes progress in parallel and keeps (at least slightly) ahead so that the downstream activity can proceed smoothly. |
A downstream team is receiving part drawings and can build a part at a time, as long as the drawing are flowing at a regular pace. |
|
Late |
Work can progress in the source segment later than in the dependent segment. Later, as the dependent segment is nearer to completion, the source segment can progress rapidly towards completion. |
Near the end of an development, a team for a different activity needs to check in and receive validation of the outcomes and adherance to an API, but they didnt need any coordination before that point. |
|
After |
Work can only progress in the source segment after the dependent segment is complete |
|
|
Undefined |
Used by the system to describe a dependency type it does not recognize. This type has been included for importing project data from other sources. |
||
None |
No dependency relationship exists between the source and dependent segments. Use this dependency type when you want to have only part of the total dependency relationship defined. |
You may want two activities to start at the same time, implying a dependency for an early stage, ut once they have begun you want them to progress independently of one another. |
|