%0 Book Section %1 noKey %A Yli-Huumo, Jesse %A Maglyas, Andrey %A Smolander, Kari %B Product-Focused Software Process Improvement %D 2014 %E Jedlitschka, Andreas %E Kuvaja, Pasi %E Kuhrmann, Marco %E Männistö, Tomi %E Münch, Jürgen %E Raatikainen, Mikko %I Springer International Publishing %K engineering engineering.management orchestration %P 93-107 %R 10.1007/978-3-319-13835-0_7 %T The Sources and Approaches to Management of Technical Debt: A Case Study of Two Product Lines in a Middle-Size Finnish Software Company %U http://dx.doi.org/10.1007/978-3-319-13835-0_7 %V 8892 %X Fierce competition in the software market forces companies to release their product under tough time constraints. The competition makes companies reactive and they need to release new versions often. To achieve this need for speed, companies take shortcuts to reach deadlines. These shortcuts and resulting omitted quality are called technical debt. We investigated one middle-size Finnish software company with two independent product lines and interviewed 12 persons in different positions to understand the causes and effects of technical debt. We were also interested in specific strategies and practices for managing technical debt. The results showed that technical debt is mostly formed as a result of intentional decisions made during the project to reach deadlines. Customer satisfaction was identified as the main reason for taking technical debt in short-term but it turned to economic consequences and quality issues in the longer perspective. Interestingly, neither of the product lines had any specific management plan for reducing technical debt but several practices have been identified. %@ 978-3-319-13834-3

@incollection{noKey, abstract = {Fierce competition in the software market forces companies to release their product under tough time constraints. The competition makes companies reactive and they need to release new versions often. To achieve this need for speed, companies take shortcuts to reach deadlines. These shortcuts and resulting omitted quality are called technical debt. We investigated one middle-size Finnish software company with two independent product lines and interviewed 12 persons in different positions to understand the causes and effects of technical debt. We were also interested in specific strategies and practices for managing technical debt. The results showed that technical debt is mostly formed as a result of intentional decisions made during the project to reach deadlines. Customer satisfaction was identified as the main reason for taking technical debt in short-term but it turned to economic consequences and quality issues in the longer perspective. Interestingly, neither of the product lines had any specific management plan for reducing technical debt but several practices have been identified.}, added-at = {2015-04-20T14:26:54.000+0200}, author = {Yli-Huumo, Jesse and Maglyas, Andrey and Smolander, Kari}, biburl = {https://www.bibsonomy.org/bibtex/2d9258a4d7f894c5f898df4a9cfd39c64/ispma}, booktitle = {Product-Focused Software Process Improvement}, doi = {10.1007/978-3-319-13835-0_7}, editor = {Jedlitschka, Andreas and Kuvaja, Pasi and Kuhrmann, Marco and Männistö, Tomi and Münch, Jürgen and Raatikainen, Mikko}, interhash = {1e70d05fcbcc7d90e4ed62de9de08a26}, intrahash = {d9258a4d7f894c5f898df4a9cfd39c64}, isbn = {978-3-319-13834-3}, keywords = {engineering engineering.management orchestration}, language = {English}, pages = {93-107}, publisher = {Springer International Publishing}, series = {Lecture Notes in Computer Science}, timestamp = {2015-04-20T14:26:54.000+0200}, title = {The Sources and Approaches to Management of Technical Debt: A Case Study of Two Product Lines in a Middle-Size Finnish Software Company}, url = {http://dx.doi.org/10.1007/978-3-319-13835-0_7}, volume = 8892, year = 2014 }