3 ms·

I use Halo difficulty levels: easy, normal, heroic, legendary. They're basically t shirt sizes but I think they better convey the size of work to be done. Fro

I use Halo difficulty levels: easy, normal, heroic, legendary. They're basically t shirt sizes but I think they better convey the size of work to be done. From there, you haggle around how many you can do in a given sprint, knowing that a legendary one is basically high risk and could take more than one sprint. For level of urgency, I have another system for that, using Cold stone creamery sizes: Gotta have it (must ship this sprint), love it (should ship this sprint), like it (stretch goal). Anything that doesn't get done gets bumped to the next level of urgency for the next sprint.

byoung2 5y ago
I like this system and most companies I've worked for use a variation of it (with different names). The OP is probably suffering from undersized tickets, adding tickets after the fact, and marking everything urgent.
kthejoker2 5y ago
Your urgency system is very similar to the MoSCOW method, if anyone's looking for some historical legitimacy for a (very valid) prioritization technique: https://en.wikipedia.org/wiki/MoSCoW_method https://en.wikipedia.org/wiki/MoSCoW_method