As a team, I'd like to estimate the effort of a story in Story Points so we can understand the work remaining >> Try setting the Story Points for this story in the "Estimate" field


This story is estimated at 5 Story Points (as shown in the "Estimate" field at the top right of the Detail View).

Try updating the Story Point estimate to 4 by clicking on the "Estimate" then typing.

Estimating using Story Points

Because the traditional process of estimating tasks in weeks or days is often wildly inaccurate, many Scrum teams estimate in Story Points instead. Story Points exist merely as a way to estimate a task's difficulty compared to some other task (for example, a 10-point story would probably take double the effort of a 5-point story). As teams mature with Scrum they tend to achieve a consistent number of Story Points from Sprint to Sprint – this is termed the team's velocity. This allows the Product Owner to use the velocity to predict how many Sprints it will take to deliver parts of the backlog.

Many teams use Planning Poker to achieve consensus on Story Point estimates.

Using Other Estimation Units

You can configure JIRA Software to use time-based estimates if you wish. In the configuration for the board, on the "Estimation" tab, select "Original Time Estimate" as your Estimation Statistic. If you also wish to track the time used during the Sprint, select "Remaining Estimate and Time Spent" to enable Time Tracking in JIRA Software.




Jeffrey Spies



Story Points


Fix versions