This is a well known ant-pattern of software development with SCRUM. I call it the backlog refrigerator. I choose that name because of the same behavior of backlogs and refrigerators. Both accumulate old things nobody need and blocks space for more useful things.
Following points that you use your back backlog as refrigerator and not as backlog:
- Backlog counts more then 50 items
- Some items celebrating birthday (are older then one year)
- Multiple duplicates
- Slim description tasks where nobody can't remember the reason creating it
How to solve it
- Remove every task that is older then 4 weeks without inspecting it. Why? It's much easier to recreate a task instead of holding and discussing it.
- Next step is to avoid such kind of backlog refrigerator. Therefore you have to re-thing what should in your backlog. My advise, only user stories and only for two sprints. This keeps the development team focused and keeps your backlog in size.
PS: These advises works for your frige and your backlog.
