Estimates in Scrum are a crucial element for planning and managing work. In the context of Scrum, estimates are used to assess the complexity and effort required to complete a specific work item, often represented by user stories or development tasks.

A common practice for estimating work in Scrum is the use of story points. These points represent a relative measure of the complexity and effort needed for a particular task. The development team assigns story points collaboratively, considering various factors such as technical difficulty, required knowledge, and dependencies on other tasks.

A widely used approach to assigning story points in Scrum is the technique of Planning Poker. In this practice, team members receive cards with numerical values representing story points. During the estimation session, each member expresses their assessment by choosing a card. This process encourages discussion and sharing of different perspectives within the team.

It’s important to note that estimates in Scrum are not focused on absolute accuracy but rather on achieving a shared understanding of the work within the team. On one side, story points help make planning more effective, since the team already has an idea of the effort and resources needed; from the other side, analysing the number of story points completed in the previous sprint(s) helps the team have a better idea of the amount of work that can be expected to be completed in the following sprint(s). This concept is referred to as team velocity.

During development, estimates are regularly reviewed and updated. This review process helps the team refine their understanding of the work and adapt to new information or changes in project conditions.

A significant advantage of estimates in Scrum is their flexibility. Since estimates are based on relative assessments rather than fixed times, the team can respond more adaptively to emerging challenges without being bound to rigid estimates.

In conclusion, estimates in Scrum are a crucial tool for planning and managing work. Using story points and practices like Planning Poker, Scrum teams can gain a shared understanding of the work and flexibly adapt to challenges that arise during project development.