I work in a maintenance heavy shop. We are a manufacturing support team of 8 devs and a rotating team of 6 troubleshooters that handle 90% of the nuisance issue

I work in a maintenance heavy shop. We are a manufacturing support team of 8 devs and a rotating team of 6 troubleshooters that handle 90% of the nuisance issues. We do support work for our mission critical software as well as most department level software. About a year and a half ago, we switched to Agile methodology with an incoming boss. It was based on complaints about the old info silo style that had dominated our team for decades. The transition has been interesting. "Scrum it" has become a new term for larger projects. We too have found that Agile is a very poor fit for maintenance work. We developed a quick kanban board to address those issues, and to clean up the project tracking board. It is still a work in progress, but so far the chief complaint about it is the lack of maintainable recurring tasks. Things like periodic backup tasks to remind the newbies and the forgetful have to be added by hand or just never placed in the done column.