With the 8.2 release, we have introduced a new Cross-team dependencies report, which allows you to identify project areas handled by two different teams, where coordination of work may be crucial. 


The Cross-team dependencies report is in the form of a matrix and presents the names of projects or iterations that:

  • are assigned to a given program or project
  • have at least one incoming or outgoing dependency (note - both dependency tasks must be open).

The intersection of the rows and columns of the matrix shows the number of cross-team dependencies in the entire project (including iterations).

The more dependencies, the color changes from green through yellow to red.

If a team is not allocated to the Box or has no dependencies, it will not be shown in the report.

If there are no cross-team dependencies between Boxes, the report will present "No data."


Contrary to the Dependencies report:

  • This report displays parent-child dependencies (marked as CP).
  • This report does not present dependencies between tasks of the same team (in the fields on the diagonal of the matrix).


When you click on the report field, you will see detailed information about each dependency (divided into inbound and outbound dependencies).

The report presents soft dependencies (marked as S) and strong dependencies (marked as SE, EE, ES, SS).

The digits between the team names indicate the number of dependencies.

Status is abbreviated:

Report configuration

In the report configuration, you can rename your report. 

Export

BigTemplate addon is required.

You can export information of a given cell into xlsx.

The file is a flat list (items areng grouped per Team). The following information on both the source and target tasks of a dependency:

  • Team name
  • task key 
  • task status
  • summary
  • dependency type