4 ms·
>Toad reviewed his team’s backlog and marked 80% of the open tickets as CRITICAL or BLOCKER. Ouch.
by haikuginger 11y ago
>Toad reviewed his team’s backlog and marked 80% of the open tickets as CRITICAL or BLOCKER.
Ouch.
- BinaryIdiot 11y agoIf I had a dollar for every ticket this was done to on any project I've worked before...well I'd probably own a couple of sports teams by now.
- overgard 11y agoI'm not sure I've ever seen a story marked "minor". Generaly the "priority" of these things is just based on how annoyed the person filing the story was at the time.
- GabrielF00 11y agoWhen management starts tracking metrics on how fast major or higher bugs are resolved, most of your issues will magically become minor.
- MaulingMonkey 11y agoI've seen them! Just don't mandate priorities, or be willing to ruthlessly change them as the implementer. Some starting points: Anything which merely means the publisher won't pay us because it was a milestone deliverable, but which I could see us technically shipping without, is "wontfix." Anything which will get me fired for not implementing gets to be "minor." Anything which I will quit over before I can be fired gets to be "major." Anything which will lead to mass resignations of the entire engineering team gets to be "blocker", but only if it's actually blocking someone else from doing any work whatsoever.
- simula67 11y agoDid he mean that the tickets so marked excluded the technical debt reduction ones ?