Tell Technical Debt Prevention Through Feature RejectionAbstract:The unstated assumption in development is that our code is always ready to accommodate any feature. Ideally, we’ve refactored continuously and there are no areas of code with so much disorder that they would interfere with proposed features. However, this is rarely this case. We should assess technical debt and use it as feedback in planning. When we do, we have to admit the possibility that some proposed features should be delayed or rejected in order to sustain development. In this workshop we will examine practices around making these assessments, and options we have as developers to propose feature modifications and seek alternatives that respect the health of the system.people more about this item. What's it about and what makes it interesting? Give people the info they need to go ahead and take the action you want. To make this item your own, click here > Add & Manage Items.