Internal Dependencies
Internal dependencies involve a relationship between project activities that are within the project team's control.
Explanation
Internal dependencies exist between activities that are both within the scope and control of the project team. Unlike external dependencies, the project team has direct authority over both the predecessor and successor activities. This means internal dependencies are generally more predictable and manageable than external ones.
Examples of internal dependencies include the requirement to complete design before coding begins, or the need to finish unit testing before integration testing starts. In both cases, the project team controls both activities and can manage the relationship directly. Internal dependencies can be either mandatory or discretionary.
An internal mandatory dependency reflects the inherent nature of the work (e.g., you must assemble a machine before testing it). An internal discretionary dependency reflects the team's preferred approach (e.g., choosing to complete all documentation before starting training development, even though some training materials could be created in parallel). Understanding whether a dependency is internal helps the project manager assess how much control the team has over the schedule.
Key Points
- •Both predecessor and successor activities are within the project team's control
- •More predictable and manageable than external dependencies
- •Can be mandatory or discretionary
- •Project team has direct authority to manage these relationships
Exam Tip
Internal dependencies are within your control. Combined with the mandatory/discretionary classification, this creates a 2x2 matrix: internal mandatory, internal discretionary, external mandatory, and external discretionary.
Frequently Asked Questions
Related Topics
External Dependencies
External dependencies involve a relationship between project activities and non-project activities that are outside the project team's control.
Mandatory Dependencies
Mandatory dependencies are those that are legally or contractually required or inherent in the nature of the work, often involving physical limitations.
Discretionary Dependencies
Discretionary dependencies are established by the project team based on knowledge of best practices, preferred sequencing, or past experience, even though other sequences are possible.
Sequence Activities
Sequence Activities is the process of identifying and documenting relationships among the project activities.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Resource Smoothing
Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Part of
Schedule Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.