SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Business analysis glossary

Dependency

What it is

A dependency is a relationship where one piece of work cannot start or finish until another piece of work, team, supplier or decision is ready. Dependencies can be inside the project or external, such as waiting for a vendor API or a regulatory approval. They are tracked so the team can plan around them.

Why it matters

A project can be perfectly managed and still stop because of something outside it. Listing dependencies with owners and dates exposes these risks early, so the team can chase them, change the order of work or prepare a fallback. Missed dependencies are a frequent reason for slipping release dates.

Example

The new tracking page at Riverbend Logistics depends on the courier partner releasing its status API and on the security team approving the integration. The analyst records both in the RAID log with dates. When the API slips by two weeks, the team builds the page against a mock and loses no time.

CHECK BEFORE CONTINUING

Keep your work safe