Hacker News Reader

Months down the line your ideas might not even be relevant anymore. On my team, if you put stuff in the backlog, you're responsible for maintaining it. If you're not prepared to accept that responsibility, it belongs in a notebook or a word doc, not the backlog.

Yeah this suggestion seems like addressing a symptom - a backlog full of useless items - instead of addressing the disease - not having regular backlog grooming sessions where outdated/irrelevant items are either updated/fixed or removed.

The alternative to this that I use is "don't precisely estimate tickets more than a month out" because if something has 6 other tickets between now and it, things will probably change by then, so a precise fully-fleshed-out estimate will probably just wait time and not be any more valid than the "about a week" one anyway.