How are tasks categorized in the Sprint Backlog?

In Scrum, the Sprint Backlog is primarily a subset of Product Backlog items that the team selects for the current Sprint. This selection is based on the team’s capacity and the Sprint Goal. The tasks are categorized in the Sprint Backlog based on what the team commits to completing during the Sprint. These selected Product Backlog items are broken down into actionable tasks that the development team will work on.

This approach ensures that the Sprint Backlog is directly linked to the priorities set in the Product Backlog, allowing the Scrum Team to maintain focus on delivering the most valuable features as determined by the Product Owner. The connection between the Sprint Backlog and the selected Product Backlog items reflects the collaborative nature of Scrum, ensuring that the Development Team is working on the most relevant tasks that contribute to the overall project goals.

The other options suggest alternative categorization methods which do not align with the core principles of Scrum. Prioritizing by urgency or team preference could lead to a misalignment with the agreed-upon value and objectives, while separating tasks into functional and non-functional requirements does not capture the essence of how tasks are organized within the framework of the Sprint Backlog.