[matwood]

> planning poker meeting that every dev has 8 hours

You shouldn't be talking about hours at all. Points and team velocity help to account for all the overhead in a sprint. Once a team has a consistent velocity, they can talk about items in retro to speed up that velocity (drop a meeting, etc...).

I once had a manager who tried to break tasks down into 15 minute increments. There was a task that he argued was a 15 minute task. And yes, he was right assuming my computer was open, the right editor was up, the right project was pulled and up to date, the project was properly building, there were no updates to apply, and the list goes on.

Hours is just a bad way to plan. Unfortunately those who bill by hour are forced to plan that way.