A Story Point is a relative unit of measure used in Agile to estimate the overall effort required to fully implement a requirement. Instead of estimating in hours—which can vary based on an individual’s speed—we use points to represent the size of a task relative to others.

Assign story points based on three specific criteria:

1. Complexity: How difficult is the logic? For example, in Appian, a simple CRUD interface might be a 2, while a complex integration with data transformation logic would be a 5 or 8.
2. Repetition (Volume): How much work is there? Even if a task is simple, like mapping 100 fields into a CDT, the sheer volume of work increases the point value.
3. Uncertainty (Risk): Are there unknowns? If we are using a new plugin or a third-party API for the first time, we increase the points to account for the risk and research required.

How we do it:

We usually do story pointing during Sprint Planning. In our project, the final story point is based on the average estimate from both QA and developers, and we adjust it to the closest appropriate value