I use senior here also to point out - we had a team composed of people who had literally built a similar/same system elsewhere, and kids who are working for a l

I use senior here also to point out - we had a team composed of people who had literally built a similar/same system elsewhere, and kids who are working for a living for the first time in their lives for a few weeks. The idea that everyone gets a vote on story points & planning meetings in a conference room for hours&hours, while democratic, is counterproductive. Further, as it turns out, the dev who has done the thing 2-3 times before knows all the mistakes not to make, and move onto make new & unique mistakes (joking, sometimes) whereas the junior gets to make all the mistakes all over again. The senior is always going to give a higher effort estimate, but will generally be able to accomplish the task within that estimate more often. A junior has no ideas what they don't know, and can often be off by orders of magnitude on their estimates. Usually because they consider only what is required for the "happy path" of the code to work as expected when used as expected, with no bad data/etc. Further they will include the time it takes them to get the first cut of the code working on their box, undocumented, uncommented, not in git, not tested, and not ready for release.