Dependency Map
Map the delivery dependencies of a project across teams, systems, vendors, and decision points, then call out the critical path. Inventories every input a deliverable needs, classifies each link (finish-to-start, data, access, decision, external), assigns a provider owner and a needed-by date, computes earliest and latest dates and float, finds the critical and near-critical chains, flags uncommitted and cyclic dependencies, and ranks them by how much a slip would move the end date. Use when someone asks what depends on what, who is blocking whom, what the critical path is, which handoffs or decisions put a date at risk, or for a dependency map before planning or a launch review. Do not use for scoring uncertain events as risks (use risk-register), for pricing a requested change (use scope-change-brief), or for diagnosing a sprint burndown (use burndown-diagnosis).