Dependencies
When a phase moves, sometimes more than that one phase moves with it. The question isn't whether that happens, but whether you see it in time — with a reason attached, rather than just a red flag.
Where a dependency actually sits
Dependencies in Migreat! are recorded between phases, not between whole projects. That's deliberate: in practice a dependency lives at the level of "this deliverable has to finish before that one can start", and that's a phase-level statement even when the two phases sit in different projects.
What happens when a phase moves
When a phase that other things depend on moves, Migreat! opens an impact panel: a list of everything further down the line that's affected, with the specific reason for each affected item — not just that there's impact, but what's causing it. Alongside that sits a chain list: a rundown of the phases that follow one another, so you can walk the whole sequence instead of only seeing the next link.
If you'd rather have a plain-language explanation instead of a list of items, Migreat! can summarise that impact for you — including advice on how you might limit the damage. That explanation is always advisory: it explains what's going on but doesn't take anything over itself.
What Migreat! does not do
- No network diagram of dependencies between projects. What you get is an impact panel and a chain list, not a graphical view with nodes and lines.
- No dependencies between whole projects. The link always sits at phase level, even when the two phases are in different projects.
Which plan holds this
Dependencies are in every plan, same as projects and timelines themselves.
Current prices per plan are on the pricing page.
Further reading
How dependencies fit into the rest of portfolio governance is on the portfolio management page. How phases look inside a timeline is on the timelines page. Every part is listed on what Migreat! does.