The DETANGLE® metrics about Team Collaboration make up an “atomic model” of Team Collaboration illustrated by the following picture:

Consequences, Team KPIs and Health Factors for Team Collaboration

Team Collaboration has many aspects which are interrelated to each other. It manifests itself in two opposite directions as indicated by the the most inner and the most outer red circles above.  It affects two different sets of stakeholders

• the business side like product managers, product owners or project managers and
• the engineering side like software developers, testers and architects

The business side has to deal with the business consequences like

• Unhappy employees
• Bad reputation
• Budget overrun
• Long time-to-market

whereas the engineering side has to cope with the following aspects of the technical work and processes:

• Efficient work split
• Knowledge sharing and
• Team healthiness.

DETANGLE® aims at bridging the gap between these two circles by introducing two intermediate circles.

First, DETANGLE® measures Team Collaboration on the technical side by using its own Team Health Factor metrics. This measurement relationship is captured by the two inner circles of the “atomic model”.

Furthermore, the two outer circles represent a similar relationship. The consequences of bad Team Collaboration (i.e. budget overrun or unhappy employees) are measured by DETANGLE® Team KPIs like team fluctuation and the ratio of maintenance effort (compared to the whole system development effort). The following table includes the two measurement relationships:

Finally, DETANGLE® fills in the missing link by deriving Team KPIs based on Team Health Factors. And it identifies hot-spots of both, people and system, which need to be taken action upon like:

• contributors being a Bus Factor Island member who should be accompanied by another contributor to share knowledge
• contributors being a Bus Factor Balance member who should pass over some of the knowledge sharing to a colleague
• contributors with alarming Burnout Indicators who might need to take a break
• new developers with a low contribution to Team Efficiency who need some training
• developers with permanently low contribution to Team Efficiency who need to be coached with respect to goal settings and achievement monitoring.

The sections on

• DETANGLE® Metric Categories lists all metric  categories and
• DETANGLE® Metrics at a Glance provides an overview of all metrics in detail.