> And at the end of it, the estimate has to be thrown out anyway because the devs who picked up the story didn’t have the same experience as the devs estimating

> And at the end of it, the estimate has to be thrown out anyway because the devs who picked up the story didn’t have the same experience as the devs estimating. I thought the "rule" was a single core team, not multiple sub-teams of devs. If devs with less experience are also at the planning poking table to voice their concerns; the more experienced devs can take that feedback on board to come to a consensus estimate. Individual tasks may be over or under depending on which dev picks it up but the idea is to get the average as close as possible to being accurate.