How should we relate user story points in hours in Agile?

Question

As we know that in Agile each user story has points or size in fibonacci sequence 1,2,3,5,8,13,21 etc.My question is how should we relate user story in hours ?

Dinesh Kushwaha · Answer

I have been working as an agile scrum development team member last five years in two different companies they are very mature in agile software development. In both companies how they have been relating the story point with hours as below : 1 story point = 6.0 to 6.5 hours The fact behind this is almost every company works for 8 hours per day. Many companies believe that only 6.0 to 6.5 hours is productive hours out of 8 hours because we have to exclude lunchtime, email, meeting, and others unproductive hours from total working hours. What are the benefits to relate story point in hours are as below : You can get a better idea how much user stories you can take in the sprint. You can get better & realistic prediction of sprint user story test release date. After product backlog grooming, you can get a better & realistic prediction of software release date. Please suggest if you have the better idea.

Sathiamoorthy Ramadoss · Answer

This is also purely based on the previous history of time log against the completed user stories. How much hours spent to complete a story points will give you rough idea on hours for each story points.

Suraj Pant · Answer

Hours per user story is different from technology to technology, and change with teams as well. Based on history, team understanding, by taking values from simmilar project you can calculate SP relationship with hours. And make them standard for your project. One example could be as below: 1 SP = 2-4 hours 3 SP = 4-8 hours 5 SP = 8-16 hours 7 SP = 16-24 hours etc...

Nanddeep Nachan · Answer

Story points and hours cannot be related to each other. By translating Story Points to hours you stop benefiting from the speed of relative estimation.