Aglet

Investigate the root cause of a work dependency cycle

Cycles can arise from a real ordering constraint, mutual assumptions, missing ownership, or work items that should have been split. Investigation should reproduce why each edge blocks the next and distinguish an actual dependency from coordination habit. Test each edge against an actual prerequisite so assumed sequencing does not become permanent blockage.

Build a useful investigation brief

  1. Reconstruct each prerequisite

    For every edge, state the required output, consumer, timing, evidence, and authority. Follow the artifact or decision rather than the work item label, and identify where a dependency is inferred rather than demonstrated.

  2. Test the edge conditions

    Attempt the downstream action with a bounded substitute, current artifact, or explicit assumption. Record what fails, what proceeds, and which condition truly requires upstream work. Keep temporary tests separate from production commitments.

  3. Write the cycle brief

    Describe the first reproducible blocking edge, contributing assumptions, viable break options, and residual risk. Recommend a scope split, ordering change, interface decision, or authority escalation tied to the evidence. Separate a missing interface decision from a prerequisite that truly must occur first.

What to carry forward

A useful brief shows why the cycle exists, which edge can be changed, and what risk remains after the break. Stop when the team can act on a reproducible boundary; keep unresolved authority or interface questions explicit instead of inventing a sequence.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow