technical debt

Software Due Diligence sheds a lot of light on the unusual risks associated with tech targets (Part 2)

Software Due Diligence sheds a lot of light on the unusual risks associated with tech targets (Part 2)

January 26, 2021 by Egon Wuchner

Introduction

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.

Continue reading →

Posted by Egon Wuchner in General, 0 comments
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
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, 2 comments