In Team Estimation, how do teams typically assign sizes to stories?

In Team Estimation, assigning sizes to stories is typically done through a relative sizing approach, which is accurately reflected in the selected answer. This method allows teams to compare the complexity or effort required for different user stories against one another rather than estimating them in absolute terms.

By first estimating the relative sizes of all stories, teams can develop a shared understanding of the challenges each story presents. This group dynamic fosters discussion, engagement, and collaborative decision-making, leading to a more accurate estimation process. Once the relative sizes are established based on their complexity or effort, numerical values are assigned to these sizes, often using techniques like Fibonacci sequences, T-shirt sizing, or other scales. This process helps the team to prioritize work, allocate resources more effectively, and manage expectations related to delivery timelines.

The other options do not accurately describe the standard practice of team estimation in Agile methodologies. For instance, ranking teams by importance for completing tasks does not help in understanding the complexity of individual user stories. Defining criteria for a "Definition of Done" is more about quality assurance than estimating story sizes. Similarly, estimating roles required to complete user stories is not a method for sizing stories; instead, it focuses on resource management, which is separate from the estimation process.