How to Account for Dependencies in Software Project Estimates

If an estimate depends on another team's work, record what must happen first, who owns it, and the evidence for its expected date. Separate your implementation effort from waiting time. Check the dependency's current state before treating it as a blocker.

By The Quely Team, Quely editorial team

Published . Last updated .

How do you account for dependencies in software project estimates?

A feature is ready for estimation, but it depends on another team's API change. The work is described in a ticket. The date and constraints sit in a separate discussion. Before the team commits, someone needs to check both.

To account for dependencies, record what must happen first, who owns it, and what evidence supports the expected date. Separate the effort to build your part from the time spent waiting. Then review the order of work with the teams involved.

Check a dependency before you estimate

A dependency is not automatically a blocker. The other team may already have delivered what you need. Check its current state before adding delay to the plan.

  • Required outcome: What must be available before your team can start or finish?
  • Owner: Who can confirm its status and answer questions?
  • Source: Which work item, document, or discussion explains the dependency?
  • Timing: Is the expected date confirmed, an estimate, or still unknown?
  • Fallback: Can you change the order, use a temporary interface, or deliver a smaller part?

Keep the answers with the estimate. Review them again when the source work changes. An extra number in the estimate does not resolve an unknown owner or date.

How Quely Helps Teams Identify Dependencies Before Estimating

Bring selected work items into a Space. Work with the team through documents, discussions, meetings, and updates. Ask Orbit which available information explains a dependency or blocker. Use Lenses to view decisions, risks, or open questions separately.

For example, the team can ask which decision affects the API work and what still needs confirmation. Check the answer against its source material. People still supply missing information, confirm dates, and decide what to commit to.

The Agile Coaches Report explores why the conversation behind an estimate matters. Its interview themes are not a benchmark for how much time dependencies add.

Methods for Handling Dependencies

Choose a method that fits the question. A team effort estimate and a release schedule answer different questions. Record the assumptions each method uses.

A. Tactical Methods: Estimating with Dependencies Built In

  1. Separate shared work from downstream work. If two features need the same infrastructure change, show that change once in the plan. State which feature depends on it. Do not count the same delivery effort twice.

    If the team keeps the shared work inside one feature instead, record that choice and the assumed order. Revisit the other estimate if the order changes.

  2. Keep effort and waiting time separate. Mike Cohn describes story points as relative effort, including work, complexity, and uncertainty. A wait for another team is also a scheduling constraint. Record it explicitly rather than treating a point value as a promised completion date.

  3. Three-Point Estimates & Buffers

    • Capture Optimistic (O), Most Likely (M), and Pessimistic (P) durations for any task with significant dependencies.

    • For a PERT weighted mean, use (O + 4 × M + P) ÷ 6. Keep the same time unit for all three inputs. This is a model of the activity duration, not a guaranteed completion date.

    • Model schedule risk instead of applying a universal buffer. Estimate the likelihood and impact of specific dependencies, then derive contingency from that analysis. The U.S. GAO Schedule Assessment Guide explains how schedule risk analysis supports realistic completion dates and the cost effects of slippage.

  4. Model the sequence for a larger schedule. Show the activities and their dependencies, then examine which sequence determines completion. Test what happens if a critical input is late. The GAO guide covers schedule logic, critical paths, and uncertainty. A detailed model is useful only if its activity dates and relationships are maintained.

B. Strategic Methods: Eliminating Dependencies at the Source

Some dependencies can be reduced. Others, such as a required external approval, still need an owner and a plan.

  1. Review team boundaries. Ilia Pavlichenko argues for broader team skills and simpler organization where repeated handoffs create dependencies. This is an organizational option to assess, not a reason to reorganize for every delayed task.

  2. Review the technical boundary. Ask whether the teams can agree a stable interface, reduce coupling, or deliver a smaller independent change. Moving to microservices does not automatically remove coordination.

  3. Check approval requirements. Automate repeatable evidence collection or checks where appropriate. Keep required human security and compliance decisions. Measure the actual wait before promising a reduction.

  4. Review repeated waits. If the same dependency delays several items, compare changing the sequence, assigning capacity, and removing the dependency. Record the trade-off the team chooses.

Conclusion

Before committing to an estimate, check the dependency's state, owner, expected date, and source. Discuss uncertainty with the teams involved. Keep the assumptions available when the work changes.

In a Space, the team can keep work and relevant context together, ask Orbit a focused question, and review open questions through a Lens. The answer depends on the material available. The team still chooses the estimate and next action.

What changed (October 2026): Added a dependency review checklist. Separated effort from waiting time, corrected the PERT formula, replaced unsupported outcome claims, and linked the research behind estimation discussions.

Related reading: Build more defensible sprint estimates.

Find more Quely articles

Choose Quely as a preferred source in Google Search.

Prefer Quely on Google