Yes we work in scrum. I think maybe the somewhat tolerable sweetspot is limiting libraries to your team and not guaranteeing backwards compatiblity to anybody else that uses it. That way you can somewhat contain the uses to the people that sit in the same room as you.

@IMSoP How would you approach solving this given the info I've given you? Maybe I'm blinded because of things I didn't consider or my own prejudices and inexperience. What questions should I ask myself to approach this correctly?

@IMSoP Because this will require coordinating this change with the "would be" maintainer of the library which is the original team that developed it, having to think on how to not break the already not well written API and behavior of the original version so as to not affect other teams and coordinate with my manager to have enough time to do all of this properly without creating an even larger mess.

@PhilipKendall I am a developer, I don't have a lot of years under the belt but I'm one of the more senior developers on my team.