I'd strongly suggest you look at Kanban over sprint for your work, if you deal with a lot of emerging priorities. The value of sprint is the shorter-but-fixed w

I'd strongly suggest you look at Kanban over sprint for your work, if you deal with a lot of emerging priorities. The value of sprint is the shorter-but-fixed work windows. If you need to consistently manage priorities that change work within this timeframe, sprint is a worse approach. You probably have a good idea of how much of your work (over time) is interrupt-driven, so if you need to do some project-oriented work you can split capacity across these streams and then run them differently.