internal dependencies
Links among two or more project activities inside the project that determine how those activities must be sequenced or coordinated.
Key Points
- They are within the project and generally under the project team's control.
- Often arise from technical workflow, resource constraints, or process order.
- Represent schedule logic (FS, SS, FF, SF) and can influence the critical path.
- Different from external dependencies (outside parties) and from purely discretionary choices.
Example
In a software project, the team must complete the database schema before coding the data access layer. Both are project activities, so this finish-to-start link is an internal dependency.
PMP Example Question
Which scenario best illustrates an internal dependency?
- Waiting for a government license before distribution.
- Completing UI design before developing front-end code.
- Receiving APIs from a third-party partner before integration.
- Corporate budget approval before issuing a purchase order.
Correct Answer: B — Completing UI design before front-end development
Explanation: Both activities occur within the project and their order is controlled by the project team, making this an internal dependency.
