Forum Overview :: NetHack :: Re: "We are going to come up with a way to translate story points to hours"

[quote name="Ice Cream Jonsey"][quote name="E. L. Koba"]"But for now you need to fill out this excel spreadsheet with how many hours each person on your team will be spending on each project for the next 3 months" (We don't even use story points, just 'cycle time' - how long it takes tickets to go from "ready for dev" to "deployed" as a rough idea of how we are getting things done) I'm putting in my 2 week notice on the 3rd.[/quote] Oh god. I remember something like this going on at a former company years ago. They eventually had a mass layoff. The only thing I've ever seen work is something like this: you've got developer and QA "units." Everyone's either a full, half or zero unit. (New hires or people mostly on vacation would be a zero. A developer that is a lead and going to meetings most of the day is a half. Normal, experienced employees are a full unit.) You then try to chunk tasks up and each day is considered a day where maybe half your time can be spent coding, the rest bullshit. So if you could do something in one day if everyone left you alone and there were zero distractions and you were in the zone, that would be considered two days. At the midway point of the sprint, everyone gets to re-examine how they are doing. Some stuff will take longer and you announce what you're cutting. (I am sure you could add stuff on if things went amazingly well, but how often does that happen?) As the sprints finish over the course of a year, some manager somewhere can try to understand velocity by looking at what got done. There are probably other systems that work, but that's the only thing I've personally seen work well. :( ICJ[/quote]