Does anyone have a nice one-hour-ish exercise (ideally described in a blog post or something) for a team that wants to talk about prioritizing and planning re technical debt in their web app, at a high level? For example: list of aspects to consider (like: deployment reliability, adequacy of tests, matching environments, hardcoded stuff, dependency upgrades), formulas for evaluating impact of potential tasks, etc. I’m making an exercise but am curious if you have a thing you’ve used and like.