Purpose:
To increase technical debt visibility and manageability, Yli-Huumo’s Study provided a report based a action research methodology about how to design processes for identification, documentation, and prioritization of technical debt.
How this tecnology can be used?
The main activities proposed in Yli-Huumo’s Study should be adopted to support the design processes for identification, documentation, and prioritization of technical debt for a project. In summary, five main activities and outcomes are recommended:
- To interview stakeholders related to the development of software products/projects to understand the current issues related to technical debt and its management.
- To develop a process for identification gathering the data from previous knowledge and history of people related to the product.
- To develop a process for documentation. In this context, a single technical debt backlog can be used to make the technical debt more visible to everyone in the product line. A similar template to Guo and Seaman can be adapted to collect all technical debt items. This template can be found in Yli-Huumo’s Study.
- To organize a workshop. A process to prioritize technical debt issues with a simple technical debt evaluation and prioritization template can be adopted. The technical debt evaluation template also can be found in Yli-Huumo’s Study.
- Sorting. By considering as input the evaluation of each technical debt item, which includes their importance. .
More information about these steps and their outcomes can be found in Yli-Huumo’s Study.
Prerequisite for use it: None.
Supported TD type(s): It is independent of TD types.
Supported TDM activity (ies): Identification, Prioritization, and Documentation.
Source/Input Artifact(s): Information about the required tasks and standards for developing a software product.
Project Context, Programming Language or Domain Application: This pratices are independent of project context, programming language and domain application.
Evidence Type(s): Source(s): Case Study.
Reference: