@polotek@social.polotek.net Yes on having conversations, no on training. The better teams used points or shirt size; those close to the project understood their imprecise nature. I read widely. no. 1: you can only estimate something you've done before, as another comment mentioning Steve McConnell says. Look back is important. Retrospectives and velocity aren't enough. Individual programmers need to be taught how to record their work and compare results with estimates.