Abstract
Software companies depend heavily on knowledgeable employees. Competenceand skills management are essential instruments to understand how toemploy the available skills in an optimal way. Unfortunately,implementing knowledge management strategies like competence and skillsmanagement is challenging because resources, time and effort arerequired before benefits become visible. This paper shows an approach tocollect noninvasively (i.e., without requiring any effort bydevelopers) data about “who ” is working on “what” during softwareproduction. We present two examples to show how to answer threequestions: “who is the expert of a specific part of the code?”, “whoshould do pair programming with whom?”, and “what knowledge gap arisesif a specific developer leaves?”