Using the chord diagram visualisation below you are able to get a unique insight into how knowledge is spread across your team or if silos of knowledge are developing.
The underlying data is all created PRs within the time range, where there is at least one event type (see below) completed other than authored. The diagram then shows the relationship between the author and the individuals participating in the PR.
As with all our metrics, a full set of filters are available, including; author, the participant (completed any event other than authoring), repository, or any Ticket related field configured for your organisation in Plandek.
Event Type Filtering
As well as the standard list of fields you expect to be able to filter on we also have a bespoke filter on the Event Type.
Event Types depend on the tooling used for the data source for your organisation:
GitHub | Bitbucket | GitLab | Azure DevOps |
Opened | Opened | Opened | Opened |
Commented | Commented | Commented | Commented |
Approved | Approved | Approved | Approved |
Merged | Merged | Merged | Merged |
Closed | Declined | Closed | Closed |
Changes requested | Changed requested | ||
Review requests | Review requests | ||
Dismissed | Unapproved | ||
Pending |
So how do I interpret this metric?
As you start to explore each diagram take a moment to notice the size and direction of each chord to and from each individual.
In the below example we can see that Colin commented on 17 of Mike's PRs, but Mike has only commented on 4 of Colin's PRs.
We can also notice the start of a silo in the bottom right quarter, although it's good to see even thin chords in all directions showing collaboration and knowledge sharing across the full team.
