For Project managers

Know your project's dependencies before they know you.

Every project reuses systems, datasets and flows that other teams depend on. Asset Navigator shows your project scope with its upstream and downstream dependencies, so you can see the impact of a delay, a change or a handover before it lands in someone's sprint.

Asset Navigator showing a dataset with its upstream sources and downstream reports and AI agents

Why project managers use it

Your project has an owner. Its dependencies usually don't.

Scope lives in a spreadsheet

You build it by hand at kickoff, and it's out of date by the first sprint review.

Other projects share your data

Two projects reuse the same dataset, and the teams find out during testing.

Projects end. Connections don't.

At closing, nobody can say exactly what stays running and who owns it now.

HOW Project managers USE IT

Start from your project. See everything it touches.

01
Projects

Get your scope in one view
Open your project and see the assets it produces or uses, with the datasets and components behind them. That's your scope, kept current, not rebuilt for every steering meeting.
02
Datasets

Know the data your project touches
Open each dataset your project reads or writes. See its data classification and confidentiality, and who else uses it, so you plan data changes early, not in a late escalation.
03
Components

Spot shared flows and connectors
When your team changes or retires a flow, see which other projects still use it and who to talk to first.
04
Assets

Plan the right reviews early
Run upstream and downstream impact analysis on what's in scope. If an asset is flagged business critical or regulatory critical, bring in compliance and architecture at the start, not a week before go-live.
05
Environments

Know what's live
See what your project already runs in production and what's still in test, so go-live and handover plans start from facts.

FOR SCRUM MASTERS

Bring the map into refinement

Before the team estimates a story, check what it touches. Dependencies on other teams show up as blockers in refinement, not in the middle of the sprint.

STORY Add VAT field to customer_orders

DOWNSTREAM Monthly revenue report · CRM migration

Talk to 2 teams

What you get

Deliver with fewer late surprises.

Clear scope from day one

One view of what your project touches, kept current as the work moves.

Dependencies found in planning

Cross-project conflicts surface at kickoff and refinement, not in testing.

Cleaner handover and closing

Know what stays running after the project ends, and hand it over with its connections.

Fewer alignment meetings

Developers, architects and compliance look at the same map, so status calls get shorter.

Who it's for

Different roles. Same map.

Everyone sees what they need, and acts with confidence.

Developers

Understand dependencies before making changes, and see which applications, APIs, databases, datasets or reports are connected.

IT Architects

See the technical landscape across business units and regions, to spot reuse, avoid duplicate builds and keep new solutions aligned with your architecture.

Business analysts

Understand where information comes from, how it moves through systems, and which reports or processes depend on it.

Risk & Compliance

See which assets and AI agents support your critical functions, with their classification, criticality and providers. Export your AI inventory report, ready for your auditor or regulator.