> The whole team was really just doing hours/days -> points mapping in their heads during estimation anyway. This is a common story. But because of the calcula

> The whole team was really just doing hours/days -> points mapping in their heads during estimation anyway. This is a common story. But because of the calculation step, your PM was still mapping estimated time units to actual time consumed, and using that mapping for predictions. So you were getting some of the benefits of an abstracted unit (accuracy, averaging in unexpected events) without the stress reduction or focus on quality over time. But if it worked for your team, I would advocate to keep it. Human groups are hard enough to coordinate as it is, there's no need to hew to a dogma.