The Backlog holds everything agreed but not yet scheduled. Each item has an ID and a priority, so nothing is lost and the next round is never assembled from memory.
Why it is worth keeping tidy
A clean backlog means sprint planning is a matter of choosing, not remembering. A neglected one means every planning session starts with an argument about what exists.
The habit that keeps it clean is small: when something is agreed but not now, put it in the backlog immediately rather than leaving it in a chat message.
Pulling work into a sprint
Open a backlog item to see its priority and detail, then move it into the sprint from its actions. It leaves the backlog and appears on the board.
Pull deliberately rather than optimistically. A sprint that consistently carries work over is telling you the commitment was too large, and velocity will show you by how much.
Setting the goal
A sprint goal is a short statement of what the round should achieve. Write it before the work is chosen, not after, or it becomes a description of whatever happened to be pulled in.
The test of a good goal: somebody outside the team can read it and say whether the sprint succeeded.
Did this answer your question?
No, ask a person