Carregando...
Logo isTDMFramework

TD Prioritization

It provides information to support the evaluation and ranking of each known TD item. The information also considers specific criteria for supporting decision-making related to prioritizing TD items.
Some terms are highlighted in italics. You can access definitions for these terms by clicking on them.

Activity PRI_1: Define and use specific criteria to prioritize TD

Criteria can be defined and used to support prioritizing TD items.

Task PRI_T1.

Define which criteria should be used to support the prioritization and the decision-making about the payment of TD items.

Status

Recommendations

R1_PRI_T1.

When applicable, one or more criteria can be defined to support the prioritization of TD items. Such criteria include business values, the impact on internal quality, and the costs of TD items. See the list of some of such criteria here.

Status
Task PRI_T2.

Adopt the defined criteria in the context of the TD prioritization strategy.

Status

Activity PRI_2.: Define and use specific SE technologies to prioritize TD items

Project members can define and adopt technologies to adequate order prioritization of repayment of TD items.

Task PRI_T3.

Design a strategy to prioritize TD items by considering specific scenarios, prioritization criteria, and SE technologies.

Status

Recommendations

R1_PRI_T3.

Define the main scenario that will be used to drive the prioritization and payment strategies of TD items in the project. To do it, consider the following scenarios:

The scenario of TD Prioritization 1:  Consider the end of one iteration/release and the beginning of another. Important features are planned for the software product or one of its components in the next iteration/release. Then, the existing TD items that may impact the development or maintenance of such features must be paid down simultaneously. So, define which and how many items should be paid for. To do it, use the specified criteria and/or strategy for ranking and repayment of TD items.

The scenario of TD Prioritization 2: TD items are increasing or decreasing for a software product or one of its components, and there are enough TD items to justify devoting resources to paying it down (perhaps a percentual of the project’s iterations or an entire iteration/release. So, define which and how many items should be paid for. To do it, use the specified criteria and/or strategy for ranking and repayment of TD items.

Status

R2_PRI_T3.

Define how the established criteria should be used and assessed. It includes defining a scale to represent (quantitatively or qualitatively) the TD items against such criteria as Radio Scale, Likert Scale, and Visual Analogue Scale.

Status

R3_PRI_T3.

Identify the dependencies if the dependence among TD items or the dependence between TD items and features were defined as criteria to be considered in the prioritization of TD items. A traceability matrix can be used to identify and track such dependences. If relevant, use the proposed Artifact 5 (Documentation of TD items – Related Features and Dependence on other TD items) to record information about such dependences.

Status

R4_PRI_T3.

Some prioritization strategies’ characteristics regarding criteria assessment can be used as a base to design a TD prioritization strategy. Some examples of prioritization strategies, but not limited to, are Risk and Impact Matrix, Multicriteria analysis, MOSCOW, RICE, BASICO, GUT, WSJF, Technical Certainty x Business Agreement, and agile prioritization techniques.

Status

R5_PRI_T3.

If relevant, define the proper moments (milestones) in which the TD items should be prioritized. For instance, the (re)prioritization of TD items can be performed at the end or beginning of each project iteration.

Status
Task PRI_T4.
Identify and define technologies that can be used to support the prioritization of TD items.
Status

Recommendations

R1_PRI_T4.

Look for specific technologies proposed for TD prioritization or traditional prioritization strategies that can be used to support the prioritizing of TD items. See the list of some such technologies for TD prioritization here. Besides, establish how and when such technologies will be used.

Status
Task PRI_T5.
Evaluate (qualitatively or quantitatively) each TD item from the TD backlog according to the defined scenario, technologies, and/or strategy for TD prioritization. Besides, this evaluation should be performed in the defined milestones, according to team members’ decisions.
Status

Recommendations

R1_PRI_T5.

If the Scenario of TD Prioritization 1 was defined as relevant to the moment, select only those TD items associated with the features planned for the next iteration/release to be evaluated. If applicable, identify the relationship between TD items from backlog vs. features from the previous iteration and features from the last iteration vs. the features planned for the next iteration to support the selection of TD items to be evaluated.

Status

R2_PRI_T5.

Suppose the Scenario of TD Prioritization 2 was defined as relevant to the moment. In that case, all TD items from the backlog should be (re) assessed.

Status

R3_PRI_T5.

Identify and consider the dependence among the TD selected for prioritization if appropriate.

Status

R4_PRI_T5.

The main output of this activity should be a list of prioritized TD items to be paid.

Status

Activity PRI_1: Define and use specific criteria to prioritize TD

Criteria can be defined and used to support prioritizing TD items.

Task PRI_T1.

Define which criteria should be used to support the prioritization and the decision-making about the payment of TD items.

Status

Recommendations

R1_PRI_T1.

When applicable, one or more criteria can be defined to support the prioritization of TD items. Such criteria include business values, the impact on internal quality, and the costs of TD items. See the list of some of such criteria here.

Status

Activity PRI_2.: Define and use specific SE technologies to prioritize TD items

Project members can define and adopt technologies to adequate order prioritization of repayment of TD items.

Task PRI_T3.

Design a strategy to prioritize TD items by considering specific scenarios, prioritization criteria, and SE technologies.

Status

Recommendations

R1_PRI_T3.

Define the main scenario that will be used to drive the prioritization and payment strategies of TD items in the project. To do it, consider the following scenarios:

The scenario of TD Prioritization 1:  Consider the end of one iteration/release and the beginning of another. Important features are planned for the software product or one of its components in the next iteration/release. Then, the existing TD items that may impact the development or maintenance of such features must be paid down simultaneously. So, define which and how many items should be paid for. To do it, use the specified criteria and/or strategy for ranking and repayment of TD items.

The scenario of TD Prioritization 2: TD items are increasing or decreasing for a software product or one of its components, and there are enough TD items to justify devoting resources to paying it down (perhaps a percentual of the project’s iterations or an entire iteration/release. So, define which and how many items should be paid for. To do it, use the specified criteria and/or strategy for ranking and repayment of TD items.

Status

R2_PRI_T3.

Define how the established criteria should be used and assessed. It includes defining a scale to represent (quantitatively or qualitatively) the TD items against such criteria as Radio Scale, Likert Scale, and Visual Analogue Scale.

Status

R3_PRI_T3.

Identify the dependencies if the dependence among TD items or the dependence between TD items and features were defined as criteria to be considered in the prioritization of TD items. A traceability matrix can be used to identify and track such dependences. If relevant, use the proposed Artifact 5 (Documentation of TD items – Related Features and Dependence on other TD items) to record information about such dependences.

Status

R4_PRI_T3.

Some prioritization strategies’ characteristics regarding criteria assessment can be used as a base to design a TD prioritization strategy. Some examples of prioritization strategies, but not limited to, are Risk and Impact Matrix, Multicriteria analysis, MOSCOW, RICE, BASICO, GUT, WSJF, Technical Certainty x Business Agreement, and agile prioritization techniques.

Status

R5_PRI_T3.

If relevant, define the proper moments (milestones) in which the TD items should be prioritized. For instance, the (re)prioritization of TD items can be performed at the end or beginning of each project iteration.

Status
Task PRI_T4.
Identify and define technologies that can be used to support the prioritization of TD items.
Status

Recommendations

R1_PRI_T4.

Look for specific technologies proposed for TD prioritization or traditional prioritization strategies that can be used to support the prioritizing of TD items. See the list of some such technologies for TD prioritization here. Besides, establish how and when such technologies will be used.

Status

Activity PRI_1: Define and use specific criteria to prioritize TD

Criteria can be defined and used to support prioritizing TD items.

Task PRI_T2.

Adopt the defined criteria in the context of the TD prioritization strategy.

Status

Activity PRI_2.: Define and use specific SE technologies to prioritize TD items

Project members can define and adopt technologies to adequate order prioritization of repayment of TD items.

Task PRI_T5.
Evaluate (qualitatively or quantitatively) each TD item from the TD backlog according to the defined scenario, technologies, and/or strategy for TD prioritization. Besides, this evaluation should be performed in the defined milestones, according to team members’ decisions.
Status

Recommendations

R1_PRI_T5.

If the Scenario of TD Prioritization 1 was defined as relevant to the moment, select only those TD items associated with the features planned for the next iteration/release to be evaluated. If applicable, identify the relationship between TD items from backlog vs. features from the previous iteration and features from the last iteration vs. the features planned for the next iteration to support the selection of TD items to be evaluated.

Status

R2_PRI_T5.

Suppose the Scenario of TD Prioritization 2 was defined as relevant to the moment. In that case, all TD items from the backlog should be (re) assessed.

Status

R3_PRI_T5.

Identify and consider the dependence among the TD selected for prioritization if appropriate.

Status

R4_PRI_T5.

The main output of this activity should be a list of prioritized TD items to be paid.

Status

TDM Guidelines