Cape of Good Code Team

digiweek M&A 2021 – 18.06.2021

digiweek M&A 2021 – 18.06.2021

Technical Debt as Risk for Software-centric M&A Targets

We are going to give a talk and present our latest software analysis insights to predict technology risks in software investments.

Software-centric business models pose a challenge for any potential investor. Bad code quality, an outdated code architecture or serious dependencies on people are not obvious but they accumulate to so-called Technical Debt.

While the software seems fit for purpose at first sight, maintenance- and development cost, as a symptom of Technical Debt, may escalate soon and puts the future business success at risk.

The technology risks of software targets and their technical debt can be analyzed deeply with the appropriate tools in the short time period of a due diligence.

Where and When?

Posted by Cape of Good Code Team in Events, 0 comments
Informatik Aktuell: Rethinking (Collective) Code Ownership – Knowledge Distribution Risks Demonstrated With the German Corona-Warn-App

Informatik Aktuell: Rethinking (Collective) Code Ownership – Knowledge Distribution Risks Demonstrated With the German Corona-Warn-App

Our article at Informatik Aktuell (in German) about knowledge distribution patterns such as Knowledge Balances, Knowledge Islands and Knowledge Tangles by the example of the German Corona-Warn-App has been published on  March 9, 2021.

As a project manager for a software development team

  • Do you know the team structure?
  • Do you know who is working on what?
  • Do you know whether the respective developer has the best knowledge prerequisites?

“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.

With a little thought, one starts to wonder, e.g. because “collective code ownership” contradicts the principle of modularisation and efficient development.

But the principle is not only dubious, it also causes harm…

Click here for the English translation of the article. For more on the Corona-Warn-App, check out our blog: Corona-Warn-App – On the Way To Critical Technical Debt?

Posted by Cape of Good Code Team in Press About Us, 0 comments
JAVAPRO 01/2020: Detect Architecture Hotspots

JAVAPRO 01/2020: Detect Architecture Hotspots

Our article “Detect Architecture Hotspots” has been published  in the 01/2020 edition of JAVAPRO.

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…

The complete article in German is available here as PDF.

An English translation is available in our blog: Architecture Hotspots – Despite Good Dependency Structures.

Posted by Cape of Good Code Team in Press About Us, 0 comments
Talk JCON 2020 conference – 27.10.2020

Feature- and time-based software analysis – Balancing features, effort & quality

Egon Wuchner and Konstantin Sokolov are giving a talk on the following topic:

Digitalization drives the requirements for software development to the top. In an increasingly digitalized world, software projects are characterized by an uncertain feature set making R&D hardly planable and software maintainability a high-end goal. How to achieve a high business value of software without wasting a lot of development effort?

This talk shows how to create the balance between focusing on the development of business-relevant features and effective quality improvements of these features. Value, effort and code quality has to be measured, monitored and estimated along the axis of features. We introduce new concepts and analysis methods to focus all efforts and quality improvements along features. We will talk about feature modularity instead of code modularity only and the concept of feature quality debt. And show how it helps to align business with quality goals, by turning heated subjective discussions into data-driven, fact-based collaboration.

We are going to show how managers, product owners and engineers are able to answer the following questions in order to deal with the unknown variables of projects today.

  1. What is the effort distribution along features/functionality? Is it supposed to be this way? Is the main effort spent on features with high business value? Do current features have a high business value?
  2. How well can you extend existent features? How well can you add new features to your system? Which parts of your system are not well suited? Which of these parts are worth improving at all?
  3. Where is it possible to predict upcoming errors and high maintenance efforts based on previous feature implementations? Where is it a necessity to act proactively to avoid exponential maintenance effort later?
  4. How can you reliably estimate the effort it takes to address the aforementioned hot spots?
  5. What are the risks of knowledge distribution in your team(s)? Where are the knowledge islands and knowledge tangles (with the latter leading to bugs later)?

Where and When?

  • Tuesday, 27.10.2020
  • 4 pm
  • Stream 4 (Testing Day)

More Information

Posted by Cape of Good Code Team in Events, 0 comments