Carregando...
Logo isTDMFramework

TD Prevention

It provides information for supporting the prevention of unintentional TD items as well as the mitigation of the risks associated with existing debts.
Some terms are highlighted in italics. You can access definitions for these terms by clicking on them.

Activity PREV_1: Understand the TD phenomenon

Team members need to be aware of what is Technical Debt (TD), as well as its main types, causes, and impacts .

 

Task PREV_T1.

Plan and promote meetings, training, or workshops to team members about the occurrence of TD in software projects, such as its main types, causes, and impacts.

Status

Recommendations

R1_PREV_T1

Define adequate moments to do it. These events can be conducted at the beginning of the project or when they are required by the teams. Besides, create or select adequate materials to be used in this event. These materials should make explicit that TD is related to internal quality software. See here an example of material that can be used as a base.

Status
Task PREV_T2

Identify and communicate to team members about the project’s circumstances that may lead them to assume TD items intentionally. It includes making the TD’s benefits explicit for a long time and the most suitable times to accept intentional TD items.

Status

Activity PREV_2: Define and use adequate SE technologies to prevent TD.

Project ‘ members can define and adopt technologies to prevent the occurrence of TD items as well as to minimize their risks.

Task PREV_T3.

Identify and define adequate Software Engineering (SE) technologies that can be adopted by project members to avoid or reduce the occurrence of issues related to internal software quality. It should consider the project’s context, such as the adopted software development process and technologies.

Status

Recommendations

R1_PREV_T3.

The proposed Artifact 1 (Mapping of useful actions, artifacts, and technologies) can be used for support in identifying and defining which and how SE actions, artifacts, and technologies can be adopted to avoid or reduce the occurrence of unintentional issues related to the internal quality software product. The information mapped can be registered in proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items). Besides, see here the list of some technologies to prevent TD items.

Status
Task PREV_T4.

Adopt the defined SE technologies in the project to avoid or reduce the emergence of internal software quality issues.

Status

Activity PREV_1: Understand the TD phenomenon

Team members need to be aware of what is Technical Debt (TD), as well as its main types, causes, and impacts .

 

Task PREV_T1.

Plan and promote meetings, training, or workshops to team members about the occurrence of TD in software projects, such as its main types, causes, and impacts.

Status

Recommendations

R1_PREV_T1

Define adequate moments to do it. These events can be conducted at the beginning of the project or when they are required by the teams. Besides, create or select adequate materials to be used in this event. These materials should make explicit that TD is related to internal quality software. See here an example of material that can be used as a base.

Status

Activity PREV_2: Define and use adequate SE technologies to prevent TD.

Project ‘ members can define and adopt technologies to prevent the occurrence of TD items as well as to minimize their risks.

Task PREV_T3.

Identify and define adequate Software Engineering (SE) technologies that can be adopted by project members to avoid or reduce the occurrence of issues related to internal software quality. It should consider the project’s context, such as the adopted software development process and technologies.

Status

Recommendations

R1_PREV_T3.

The proposed Artifact 1 (Mapping of useful actions, artifacts, and technologies) can be used for support in identifying and defining which and how SE actions, artifacts, and technologies can be adopted to avoid or reduce the occurrence of unintentional issues related to the internal quality software product. The information mapped can be registered in proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items). Besides, see here the list of some technologies to prevent TD items.

Status

Activity PREV_1: Understand the TD phenomenon

Team members need to be aware of what is Technical Debt (TD), as well as its main types, causes, and impacts .

 

Task PREV_T2

Identify and communicate to team members about the project’s circumstances that may lead them to assume TD items intentionally. It includes making the TD’s benefits explicit for a long time and the most suitable times to accept intentional TD items.

Status

Activity PREV_2: Define and use adequate SE technologies to prevent TD.

Project ‘ members can define and adopt technologies to prevent the occurrence of TD items as well as to minimize their risks.

Task PREV_T4.

Adopt the defined SE technologies in the project to avoid or reduce the emergence of internal software quality issues.

Status

TDM Guidelines