So how do we do this for software developers? It's very difficult to gauge how much effort a project or bug or story will take. Without that being highly accura

So how do we do this for software developers? It's very difficult to gauge how much effort a project or bug or story will take. Without that being highly accurate, some people will finish in a few minutes then chill out while others will feel oppressed and be scrambling trying to finish their unrealistic deadlines. Even letting the team estimate stories then assigning them randomly is difficult, some members are more skilled than others. What Jim could do in an hour will take Bill a week. One thought would be to track everyone's velocity as an individual all the time and ensure all stories are small, like under a few hours. Then you'd have a small enough cycle that it should be possible to get a lot more accurate with estimating and making sure people produce similarly.