Story points are units of measurement used to determine how much effort is required to complete a product backlog item or any other piece of work. The team assigns story points based on the work's complexity, amount, and uncertainty.
The story point is a unit of measurement used to express an estimation of the effort required to implement an item on the product backlog or any other piece of work. Story points are assigned based on the complexity of the work, the amount of work, and the risk of failure.
Building off the definition of an Agile story, story points are metrics used in Agile product development and management to guess how difficult it will be to implement a user story. Put another way, it’s a numeric value that helps the development team understand how challenging the story is.
Story points in Agile are abstract measurements that developers use instead of hours. Points are relative values, so a story with a value of four is twice as hard as a story with a value of two. The actual numbers don’t matter — you could assign values between 1,000,000 and 5,000,000 if you want. Instead, you want to give the team an idea of the story’s relative difficulty. Story points tell you how much effort a given story will take to resolve.