A project dependency is a condition that must be met before an activity can be started or completed. These are tasks, activities, subprojects, deliverables or events that lay the groundwork for further work. The following are common examples of dependencies.
Architectural designs
Audits
Budget approvals
Bug fixes
Checks and validations
Communications
Analysis
Configuration
Delivering code
Delivery of a supply
Deploying software
Designs
Developing a budget
Developing cost estimates
Documentation
Employee training and development
Feasibility studies
Foundations in construction
Stages of construction such as framing
Hiring an employee
Inspections
Installations
Integration
Legal agreements and contracts
Market research
Meetings and communications
Events
Planning
Prototypes
Purchasing and procurement
Regulatory approvals such as permits
Requirements
Specifications
Research and development
Risk assessments
Scripts
Securing resources
Setting up a facility
Setting up or cleansing data
Stakeholder feedback
Strategy
Testing
Types
There are four common types of project dependency as follows.
Finish to Start
Task A must be completed before Task B can begin. In this case, tasks must be completed sequentially.
Finish to Finish
Task A must be completed before Task B can be completed.
Cookies help us deliver our services. You have choices regarding these cookies. Please visit our privacy policy, cookie policy and consent tool to learn more.
Copyright 2002-2026 Simplicable. All rights reserved. This material may not be published, broadcast, rewritten, redistributed or translated. Report violations here.