Why SCRUM Backlogs lead to bad Product Decisions
Thomas Schranz

I advise people to drop the term “backlog” unless it’s work they have committed to. The definition of “backlog” is misleading, Oxford dictionaries says “An accumulation of uncompleted work or matters needing to be dealt with”, so it suggests it’s a list of thing that HAVE to be done. But that list of all the things that you could do (Scrum or otherwise) is just that, a list of possibilities.

So I’d rather call the list “options” and only use backlog when it really is something the team have agreed to do.