Purpose:
It can supports the development of a normative process framework that systematically incorporates steps for managing technical debt in commercial software production. “The framework integrates processes required for technical debtmanagement with existing software quality management processes prescribed by the project management body of knowledge (PMBOK), and it contributes to the further development of software-specific extensions to the PMBOK.” (Ramasubbu and Kemerer, 2017).
Besides, this technology provides a generalizable and iterative implementation model of the proposed normative process.
How this technology can be used?
The steps proposed by Ramasubbu and Kemerer (2017) should be adopted to develop the proposed framework for technical debt management and implement it in software organizations. In Summary, the proposed normative framework for managing TD includes three-step process as follows:
- Step 1: Make Technical Debt Visible.
- Perform Cost-Benefit Analysis.
- Step 3: Control Technical Debt.
“To enact each of the above three steps, the framework considers specific inputs, tools and techniques, and outputs. This is similar to the organization of the various project management practices for each knowledge area covered by the PMBOK“.(Ramasubbu and Kemerer, 2017).
Detailed instructions for developing this framework, suggested artifacts, and how they can be successfully implemented in software organizations can be found in Ramasubbu and Kemerer (2017).
Prerequisite for use it: None.
Supported TD type(s): It is independent of TD types.
Supported TDM activity (ies): Documentation, Identification, Measurement, Monitoring, Prioritization, and Repayment.
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 Studies.
Reference: