Analyzing software with DETANGLE® focuses on important aspects of software engineering such as Technical Debt and Team Collaboration.
Technical Debt Analysis
Basically, analyzing Technical Debt based on DETANGLE® consists of the following steps:
- It starts with the symptoms as Effort KPIs indicating the development slow down and it identifies the respective hotspots of the code base.
- It continues with an extensive analysis of the root causes of these hotspots, investigates several Technical Health Factors and drills down the recommendations to the level of source files.
- It predicts the remediation effort to address the root causes of Technical Debt
- It compares the remediation effort to the current level of maintenance effort to decide on the right Technical Debt priorities and possible delays.
Team Collaboration Analysis
In addition, analyzing Team Collaboration based on the DETANGLE® findings is done along the following lines:
- Investigating Team KPIs like team effectiveness with respect to implementing new functionality efficiently by splitting work without neglecting knowledge sharing within the team
- Evaluating Team Health Factors like team resilience by:
- looking how individual work and team knowledge sharing get balanced
- resolving the numbers of bus factor contributors representing critical system knowledge islands, valuable system knowledge balances or reviewers of code
- identifying the number of technical coordinators
- looking at how new developers get familiar with the system
- Estimating team healthiness as another Team Health Factor by
- identifying burnout indicators per engineers like the unbalanced work on maintenance only or high levels of work context switches between bugs and features
- quantifying the stress-causing parts of the code with high technical debt, engineers have to work with
- Coming up with recommendations on which parts of the code base to increase knowledge sharing, to split work more efficiently and whether to build up additional technical coordinators.