Ken Power. Understanding the Impact of Technical Debt on the Capacity and Velocity of Teams and Organizations

Time is of course a very important recourse in software engineering teams and deciding what to do with the developer time there is is a though decision. Ken Power found that just focusing on features was not enough, as sometimes teams were quicker and it was unclear why that happened. Therefore, at Cisco, they started Read more about Ken Power. Understanding the Impact of Technical Debt on the Capacity and Velocity of Teams and Organizations[…]

Johannes Holvitie – DebtFlag: Technical Debt Management with a Development Environment Integrated Tool

After the previous talk on the abstract requirements, now it is time for a real tool, DebtFlag. There are two different approaches to TD information production: Automatic: use predefined models that separate between good and bad pieces of the code. However, often not able to capture entire requirement space Manual: Can capture everything, but is Read more about Johannes Holvitie – DebtFlag: Technical Debt Management with a Development Environment Integrated Tool[…]

Davide Falessi – Practical Considerations, Challenges and Requirements of Tool-support for Managing Technical Debt

Managing TDD consists of three activities according to Davide Falessi: Identify the TD items Estimating the economic consequences Analyzing differences between consequences Davide states that the real challenge is #2, as we need to convince customers that time spent on resolving TD makes sense from a financial perspective. Observations here are that not all TD Read more about Davide Falessi – Practical Considerations, Challenges and Requirements of Tool-support for Managing Technical Debt[…]

Rodrigo Spínola – Investigating Technical Debt Folklore

Rodrigo Spínola is the first presenter of the Workshop on Managing Technical Debt. The idea of his research is that if there are ‘folklore’ statements that are either widely agreed or widely disagreed with, they are interesting directions for research. The authors conducted this study in two phases. Phase 1: searching on websites, blogs and Read more about Rodrigo Spínola – Investigating Technical Debt Folklore[…]

Managing Technical Debt – Keynote by Steve McConnell

Definition according to Steve:  the obligation that a software organization incurs when it chooses a design or construction approach that’s expedient in the short term but that increases complexity and is more costly in the long term. He starts the keynote with some funny examples: 50% of all code in one class One stored procedure 15.000 Read more about Managing Technical Debt – Keynote by Steve McConnell[…]