zlacker

> and people tend not to be overly optimistic and forget to account for things like sickness, meetings, etc.

> people seem to be more realistic about the variance in actual delivered points per sprint, as opposed to when you try to measure things in hours or days

Okay I think I'm with you. In my team, the PM pre-calculates the number of available days in the sprint per developer before taking any estimates, factoring in planned holidays and estimates of sickness and meeting time, and adjusting for seniority. I guess points are kind of a crude way of doing the same thing.

>>n4r9+(OP)
> I guess points are kind of a crude way of doing the same thing.

Right. But you sound awfully judgmental in saying "crude". I'd call it robust, and not trying to produce some kind of false over-precision. In other words, appropriate to the task at hand.

>>crazyg+Ca2
So how does your team adjust capacity planning in case of disruptions like annual leave, company all-hands days, public holidays etc... ? How do you figure out how many points to reduce by?