April 16, 2021 by Egon Wuchner
How often have you encountered issues with a delivery of your software supplier? It is rather the rule than the exception. Why? Because there are some technical rules or best practices your supplier should definitely comply with, if the supplier wants to be listed as a stress-free supplier in his customer base. We have put these rules as our top 10 best practices when developing software.
March 10, 2021 by Egon Wuchner and Konstantin Sokolov
As a project manager for a software development team
“You don’t have to”, say the advocates of agile development, because “the team organises itself”. And by the way, the principle of “collective code ownership” prevails, i.e. everyone is responsible for everything in the code [1].
With a little thought, one starts to wonder, e.g. because “collective code ownership” contradicts the principle of modularisation and efficient development [2].
But the principle is not only dubious, it also causes harm. Among other things, the “diffusion of responsibility” [7] phenomenon occurs, in which no one really feels responsible any more. Individual developers lose sight of the bigger picture because many of their fellow developers have also changed the same code.
In the process, the different development styles mix into a cacophony of code, and the cognitive effort required to understand the code increases to the point of incomprehensibility.
February 23, 2021 by Egon Wuchner and Konstantin Sokolov
We applied our DETANGLE analysis suite to the Corona-Warn-App for iOS and Android to assess the quality and other risks related to maintainability and extensibility. Up to version 1.11, we determined how features and defects are reflected in the code, measured architecture quality, estimated technical debt and analyzed knowledge distribution risks.
First of all, we would like to express our appreciation in all clarity for what has been achieved with the creation of the Corona-Warn-App. The overall system was developed under high media attention, tight time frames, political pressure and very high data protection requirements. With this blog, we would now like to point out quality aspects and risks that, in our view, should be given attention after an initial development stage.
Although the current code quality metrics from SonarQube, the tool used for code analysis during the development of the Corona-Warn-App, repeatedly show a very good rating for both apps up to version 1.11, there are nevertheless striking findings that contradict this good picture in parts. In this post, we will look at the results for the iOS-version of the app.
January 26, 2021 by Egon Wuchner
In the following second part of the blog series, we are going to discuss the fields of investigation of a software due diligence.
This blog series also appeared as an article in the 11/2020 issue of the German M&A Review magazine. The specific issue of M&A Review can be found here.
In Part 1 we talk about the reasons why software assets present particular valuation risks. The last, third part, deals with the process of a software due diligence and its deliverables.
Recent Comments