Phase 03 · BuildEvent-driven
Cross-team dependency graph
How it works
The dependency graph built from Jira and code surfaces dependencies at planning time instead of in week two – re-planning costs are avoided.
- Builds a cross-project dependency graph
- Trigger: a detected dependency shift
- Reports detected shifts as a note directly in Jira
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiJiraConfluence
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Find all dependencies for story [S].
Which cross-team dependencies does epic [E] have?
Related use cases
Three use cases closely connected to this one.
Estimation with risk driversThe sprint estimate in Build: LOC, complexity and the dependency graph – with the reason behind every number named.View use case Ticket organiserMoves tickets into sprints and assigns them to epics automatically – roadmap and Jira stay in sync.View use case Jira and code, continuously aligned.Continuously compares what is planned in Jira with what is actually happening in the code – and reports the difference.View use case
From the PM Lab
Articles that explore this use case in depth.
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.