Abstract
Background: Preventing the occurrence of technical debt (TD) in software projects can be cheaper than its payment. Prevention practices also help in catching inexperienced developers' 'not-so-good' solutions. However, little is known on how to prevent the occurrence of TD. Aims: To investigate, from the point of view of software practitioners, preventive actions that can be used to curb the occurrence of TD and the impediments that hamper the use of those actions. Method: We use data from the InsighTD Project, a family of industrial surveys specifically designed to study software engineering TD. We use a corpus of answers from 207 practitioners across different geographic locations to identify and analyze - both quantitatively and qualitatively - the TD preventive actions most used in practice. Results: We found that project planning, adoption of good practices, well-defined requirements, creating tests, and training are the most cited preventive actions that curb TD in software projects. We also identified seven preventive action categories and defined relationships among them and TD types. On the other hand, the main impediments to prevent TD are related to inappropriate project planning and lack of expertise of the team. Conclusions: Our list of preventive actions and impediments can help practitioners to implement policies for the sector and guide TD researches in a problem-driven way.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
