[UK-AL]

At our company, story point method is very accurate, so most of the tasks are completed at the end of sprint except maybe 1 or 2 at the end(out of 30) which normally caused by something outside of our control.

At previous companies I used time based 'guess' methods, which were all over the place most of the time. I don't think i've ever been at a company that could actually get it right.

Honestly this way of estimating really suits my team. I don't want go back to a company that picks time based estimates out of thin air then expects you to meet them. I was really bad at that, but so is everyone else.

We don't expect to developers to have committed to complete stories mid-sprint or anything. But we have generally come to expect all items to be completed at the end of sprint, simply because our capacity planning is very good at the moment. Everyones happy with estimates at the moment. We do slight adjustments based on previous velocities. When we don't complete stories at the end of the sprint, we change the capacity for next sprint rather than blame developers.

It's a lot more collaborative, rather than a hostile blame game.