...
- The story owner make up his/her mind about what should be done in the sprintfuture. He creates tasks that reflect the results.
- The story owner selects tasks from the backlog to be put in the sprint. By doing so the story owner indicates that those tasks should be worked on in the sprint.
The story owner sets the Fix Version for tasks of which it is know when they will or should be finished. By doing so he indicates that it is planned that the results of the respective tasks will become part of the release indicated by the Fix Version.
Info Note that putting a task in a sprint and setting the Fix Version are two different things: By putting a task in a sprint it is only indicated that work should be done on this task in the sprint. It doesn't mean that the task has to be finished in that sprint. A bigger task might last over several consecutive sprints and might even be paused for a number of sprints in between. But when there is a deadline or it is probable that a task will be finished in a sprint then the Fix Version should be set accordingly so that it becomes clear what will end up in which release. There is no problem if that estimate is not met. The Fix Version has the purpose of giving an overview about what releases will probably include. There is not a contract made by setting the Fix Version and there is no promise broken if it doesn't work out!