What does backlog mean in Scrum?

• A. A backlog is a prioritized list of user stories and tasks for future sprints.
• B. A backlog is a static archive of completed work.
• C. A backlog is an optional summary of project goals.
• D. A backlog is a tool for daily standups only.

Answer: (A)

Backlog in Scrum is a living, prioritized collection of work that could be tackled in upcoming sprints. It typically contains product backlog items such as user stories, features, enhancements, bugs, and tasks. The Product Owner keeps this list ordered by value, risk, and dependencies, and the backlog is continuously refined so items have clear details, acceptance criteria, and rough estimates. Items at the top are the ones most likely to be selected for the next sprint during sprint planning, where the team pulls in work they commit to delivering. Because the backlog is dynamic, priorities can shift as new information comes in, so items move up or down and new items get added. It’s not a static archive of completed work, not a summary of project goals, and not a tool used only for daily standups—the backlog guides future work and planning across sprints.