Software Due Diligence Sheds a Lot of Light on the Unusual Risks Associated With Tech Targets (Part 1)

Software Due Diligence Sheds a Lot of Light on the Unusual Risks Associated With Tech Targets (Part 1)

December 16, 2020 by Egon Wuchner

Introduction

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.

The blog series addresses the following aspects of software due diligence:

  1. the reasons why software targets present particular valuation risks. And why a focused software due diligence is a prerequisite for assessing technological risks in the acquisition of software companies, 
  2. the fields of investigation of software due diligence and why a mix of tools and experience is necessary for this, and
  3. the process of software due diligence and its deliverables.

In the following 1st part of the three-part series, we are going to discuss the first point about the particular valuation risks of software targets.

Continue reading →

Posted by Egon Wuchner in General, 0 comments
Architecture Hotspots – Despite Good Dependency Structures

Architecture Hotspots – Despite Good Dependency Structures

October 29, 2020 by Konstantin Sokolov and Ural Sezer

This topic has been published as “Architektur-Hotspots aufspüren” in the 01/2020 edition of JAVAPRO.
The complete article in German is available here as PDF.

Introduction

Structural dependency analyses are of limited significance. In some cases they do not capture the essential architecture hotspots, as we will show by means of a code example. The feature modularity concepts presented here are a new way of understanding system complexity. They aim at identifying architecture hotspots that increase the (maintenance) effort for new features.

Continue reading →

Posted by Konstantin Sokolov in General, 0 comments
Cooperation and Knowledge Sharing for Remote Agile Development

Cooperation and Knowledge Sharing for Remote Agile Development

June 01, 2020 by Egon Wuchner

Introduction

Remote work and remote agile development have been one of the remedies in this day and age of the Corona consequences. During the last weeks, I have come across several articles, posts and blogs about the pitfalls of remote working teams and recommendations on how to take countermeasures against missing collaboration.

I think the McKinsey article on “Revisiting agile teams after an abrupt shift to remote” [1] is an interesting contribution worth considering. I am going to refer to some other sources, but do not claim any completeness with respect to the topic. But across all articles, I have been missing some simple but effective means of not only promoting a more collaborative mindset but making cooperation actually happen.

Continue reading →

Posted by Egon Wuchner in General, 0 comments
Improving Software Quality by Choosing Reasonable Issue Types

Improving Software Quality by Choosing Reasonable Issue Types

May 02, 2020 by Konstantin Sokolov

Introduction in a Nutshell

Do you exactly know which issues types to use for your issue tracker and when to use which? Does everyone in your project know about your approach? Are issue types always used consistently in your project? Should  you use Technical User Stories or not? Do you use issue types at all? Do you find it reasonable that different issue trackers have such different default issue types? Have you ever thought about issue types at all?

If your answer to one or more of the questions above is “no”, or “don’t know” or “I don’t care”,  you are not alone, and this post might be of interest to you. It reveals the chaos behind the often mindless, uncertain and inconsistent usage of issue types in many software projects. It shows why a conscious and purposeful application of issue types can lead to better code comprehensibility as well as better quality monitoring and decision making in projects. It suggests a minimal set of reasonable issue types along with understandable rules for their usage. In particular, it reasons why a separate issue type is needed to deal with technical debt.

Continue reading →

Posted by Konstantin Sokolov in General, 0 comments