Bugs are the same thing. A bug is usually either worth fixing immediately (aka "next") or "never". Many bug trackers get clogged with stuff like "on IE7, the us

Bugs are the same thing. A bug is usually either worth fixing immediately (aka "next") or "never". Many bug trackers get clogged with stuff like "on IE7, the user dialog is 5 px to the right". It's either worth fixing right now or "never". Delete it, and if another user complains and it's recent enough that we remember the other story, then it bumps up the priority. But if it happens long after we all forgot it happened, it's still not important enough to fix. I think this is only really acceptable if you are a very small team with very specific goals. I'm biased, as I work in QA, but these things are necessary because a lot of devs are pretty terrible at reading specs. QA will find scrolls of bugs, and having them all marked as 'next' is useless. You need things like priorities, you need things like Sprints.