Hi there,
So, Story points are units of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any other piece of work.
Teams assign story points to work, relative to work complexity, the amount of work, and risk or uncertainty. Values are assigned to more effectively break down work into smaller pieces, so they can address uncertainty. Over time, this helps teams understand how much they can achieve in a period of time and builds consensus and commitment to the solution. Story points are generally credited to XP (Extreme Programming).
If you would like to go deeper in this topic, I strongly recommend checking the post below:
Hope it helps.
Regards,
Carlos
Hi @AM ,
Story Points are a way to estimate the complexity of an issue. They are reletaive to each other and often some like Planning Poker is used for estimation.
You can read more here https://www.atlassian.com/agile/project-management/estimation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.