Hacker News new | ask | show | jobs
by jsploit 884 days ago
> estimate in points (relative size to something you've already done), emphasis on consistent estimates for each dev.

> capture total velocity every 2 weeks and eventually use the avg for future planning

This aspect of scrum has never made sense to me. Planning with average velocity turns points into an obfuscated time estimate - why use points at all?

1 comments

It's a psychological trick to counter our bias toward scheduling optimism.