I propose the following scheme for estimating user stories in a scrum process:
A good programmer might cost 80000$ a year, so per hour this is 80000$/52 weeks/40 hours per week = 40$ per hour. In a two week sprint, a single programmer can work for 80 hours, which would cost 3200$. So the maximum size of a story for a two week sprint should be 3200$ . So instead of using story points to estimate stories/tickets, one could use the following schema to estimate tickets from lowest to highest complexity
50$, 100$, 200$, 400$, 800$, 1600$, 3200$
One could also add that bugs cannot be estimated, so we might give them always a cost in the middle of the scheme of 400$.
What would be the disadvantage of using such a scheme for estimating tickets? Has anyone tried estimating tickets based on costs within scrum?