1. Home
  2. Docs
  3. DETANGLE® Knowledge Base
  4. DETANGLE® Metrics
  5. Team Effectiveness

Team Effectiveness

The Team Effectiveness % (TE) is a DETANGLE® Team Collaboration metric based on issues selected by the “Features” filter.

This filter is normally used to select the issue types which capture the functionality (e.g. user stories or features) as “functional” issues of your system in your issue tracker.

Team Effectiveness is a combination of two metrics:

  • Team efficiency and
  • Team knowledge sharing

Team efficiency measures how the team efficiently works together by splitting the work effort on realizing features. In contrast, team knowledge sharing measures how the team manages to share knowledge by collaborating in teams-of-two.

Ideally,  each contributor spends 50% of her effort by working on “Features” on one’s own. Additionally, each contributor ideally spends the other 50% of her effort on “Features” by practicing knowledge sharing in teams-of-two. This way the work gets split efficiently across contributors without neglecting knowledge sharing and knowledge ramp-up.

Contributor Effectiveness is computed by combining contributor efficiency and contributor knowledge sharing. It represents the distance of the contributors’ effort on work done alone (on separate code parts) and her work in teams-of-two to the ideal two-dimensional value of (50%, 50%).

Team Effectiveness sums up these contributor values by weighting them according to the contributor’s feature effort compared to the whole primary effort across all contributors per time period.

This team metric ranges from 0 to 100% and the higher the value the better. The icons in the diagrams comply to certain thresholds:

  • 👎 Team Effectiveness is below 25%, i.e. the team collaboration has reached a low critical level and definitely needs to be improved.
  • ⚠️ Team Effectiveness is below the value of 50% but above 25%, i.e. the team collaboration has reached a warning level and needs to be kept an eye on.
  • 👍 Team Effectiveness is above 50% and is in a good state. We consider a value above 50% as already acceptable, since 100% represents a really ideal and unachievable state of software development regarding the time and budget pressures put on software projects.

Team Effectiveness is calculated along the code structure of the code base, for files, folders, the whole system and for each time period:

Granularity/
Health Factors
per 

bug

per

“functional” issue

per

contri-

butor

per 

file

per

folder

per

entire

system

Feature Debt Index x x x x
Contributor Friction Index x x x x
Defect Impact x x x x
Defect Density x x x x
Team Effectiveness x x x x
Bus Factor

Islands

x x x x
Bus Factor Balances x x x x

Take a look at DETANGLE® Metrics at a Glance for an overview of all metrics.

Was this article helpful to you? Yes No

How can we help?