Why aren’t user stories estimated in man-hours?

One of the most common approaches for evaluating teamwork is to estimate in man-hours. While man-hours are simple to comprehend, they have a number of significant drawbacks:

• Few tasks, such as legacy work, are difficult to accurately estimate.
• If one member of the team delivers the estimate but another completes the task, the estimate is useless.
• The amount of time it takes to finish a task depends on the level of experience of the developer.
• Teams frequently underestimate impediments and consider only the best-case scenario.

The benefits of estimating user stories in points include the following: There is no association between the estimator’s skills and experience, and story points are independent of the story’s author. The team members can estimate more correctly since story points are a measurement of relative sizes, and the size of the tale cannot be changed by external forces. As team behavior takes precedence over individual conduct, Story Points encourages collaboration. The team comes together when they use planning poker to estimate story points. As teams exchange, constructively criticize, argue, and have fun playing poker cards to arrive to a consensus on estimations, it serves as a team building activity.