Developers typically assign story points based on their collective knowledge and experience. Each Product Backlog item is given a story point Value that represents the effort required to complete it relative to other items. For example, an item with a story point Value of two is expected to take twice the work or time to complete as an item with a Value of one.
The assignment of story points is not intended to be a precise measure of the actual time required to complete an item. Instead, it serves as a relative measure to help the team estimate effort and complexity. This approach allows the team to maintain a flexible and adaptive planning process, accommodating the inherent uncertainties in software development.
