The problem is not agile, it is an all-alige approach. It is at least in our case. Sprints are feature-focused, which leaves little time for software developmen

The problem is not agile, it is an all-alige approach. It is at least in our case. Sprints are feature-focused, which leaves little time for software development craftsmanship: reducing technical debt, updating outdated dependencies etc. To give some context: We have multiple pieces of software we build and maintain for multiple clients. When a client requests some features, they buy some sprints and we do the work and then it's done. During the life cycle of the software there is a maintenance contract for service and support and resolving bugs. This does not have much room for software craftsmanship either. This is just where I work,but I can't imagine we are the only one working like this. This is an implementation problem, not an methodical problem. One of the ultimate causes is that our org is project based, so no project, no work for that client. And the software quality suffers IMHO.