Story Points represent one of the most important sides of Scrum. They are deeply integrated in Scrum along with Planning Poker technology.
The most common problem Scrum Teams stumble upon is the inability to evaluate the difficulty of a task and time cost correctly. The graph from the article about the Burndown Chart clearly shows what will happen if the work the Team has accepted had been evaluated incorrectly.
It is often difficult to learn to evaluate it properly. What is needed is either a vast experience or an inventive approach. In order to implement Story Points in teamwork as fast as possible, it is necessary to perform a deep analysis of the tasks from the previous projects. The names of the tasks and their duration should be analyzed. And all that is left is as easy as a pie: one should arrange these tasks according to their duration, from shortest to the longest, then divide them into separate groups and evaluate them using the Scrum Poker cards.
Sooner or later such an approach will turn you into an effective and progressive Team, which is the only right way to go. Such a Team will always boost its Velocity and please their clients with awesome.
How do Story Points actually work?
If a Scrum Team is able to evaluate its work correctly, if it doesn’t forget the Velocity chart, if it tracks the Burndown Chart, sooner or later the Team will start to use Story Point for evaluation. According to the Velocity graph, for example, we see that the dynamics of the Team goes up each Sprint and the average value for the last two iteration equals 23-30 Story Points. These indicators tell the Product Owner where he can put the available points in order to fill in the Backlog.
A proper evaluation and the usage of Story Points make wonders, as they tie everything together: a Development Team realizes its real potential, a Scrum Master sees if his Team has any problems and what can be improved and a Product Owner gets to know which tasks he should include in the next Sprint.