The Big Data & Software Intelligence Company The Big Data & Software Intelligence Company

On the Risk of Dependingon a Single DeveloperOn the Risk of Dependingon a Single Developer

www.softwarediagnostics.com/en │

On the Risk of Depending on a Single Developer

The application landscape of a large company consists of multiple applications being developed by distributed development teams.

The IT manager plans a re-organization of the development department. Furthermore external contractors shall be removed from the teams. He is expecting a drastic change in responsibilities and code-ownerships.

Main concern is that complex code exists that is known only by a single developer.

After the re-organization these code-experts will be gone – and their knowledge with them.

When new developers will try to understand the complex code, the IT manager is expecting an explosion of “effort bombs” .

Initial Situation and upcoming challengesAbout experts leaving a team & „effort bombs“

2

www.softwarediagnostics.com/en │

On the Risk of Depending on a Single Developer

Step 1 – DETECT COMPLEX CODE and the NUMBER of ACTIVE DEVELOPERS therein

Solution ApproachEnsure a smooth handover of code-ownership

3

The Software Map reveals the code, that is complex and known by either only one, or only two developers. Complexity is signalized by high buildings. A person who have made changes in the code within the last 12 months is assumed to be a “knowing developer”.

Software Map LegendArea: Lines-of-CodeHeight: Complexity

Colors:

- red: CRITCAL code known only by a single developer- yellow: DANGER code known only by two developers- green: OK three or more developers know this code

Step 3 – PAIR PROGRAMMINGTo transfer the code-specific knowledge, the new developers in charge are advised to perform programming task along with the proficient developer as their mentor.

Risky situation: Very complex code known only by a single developer.Costly effort-bombs will explode when the proficient developer leaves the team.

Risk is reduced to a minimum and nothing stands in the way of a smooth re-structuring process.

Step 2 - CLEANUP & DOCUMENTThe proficient developer should be given sufficient time…

…. for cleaning up the code and reduce complexity.… to document the code in a comprehensible way.

Software Diagnostics GmbH Babelsberg StudiosAugust-Bebel-Str. 26-53 14482 Potsdam, Germany

PhoneE-MailWeb

+ 49 331 - 7062 340 mail@softwarediagnostics.comwww.softwarediagnostics.com/en

Thank You for Your AttentionThank You for Your Attention

About Software Diagnostics

Software Diagnostics based in Potsdam, Germany is a spin-off of the Hasso Plattner Institute, the university centre of excellence for software engineering. With Software Diagnostics, software development and software maintenance projects become transparent and can be managed more effectively - based on the real systems’ implementations.

Contact Us