Tl;dr any tips for new scrum team ? How to start with story points with people that dont know eachother?

More:
Its for our team project at uni ( 8 people 1 year). Yesterday we had our first meeting and the hardest part was asigning story points. Or asigning some benchmark value for story point.
Looking for some practicall tips since uni gives us all the theory we need. ( Does not mean I know all the theory :D )

📍

So... Generally your story points are:

1- quick, you know what to do and its simple
2- you know what to do but theres a bit of work.
3- some knowledge of what to do, but there might be some minor unknowns.
5- not sure what to do and there are some unknowns -- feels like theres more work then a 3.
8- lots of work to do. Might have some unknowns
13- loads of work or loads of unknowns.
20- this is not a story to do work. But a story to make more stories.
40- you've failed at making stories.

So, its generally about taking your smallest task. Assigning a story point to it, and working from relativity.

With so many people in your team. I suggest having physical cards, having a set of numbers for each person.

Then all at once reveal what you think the story point should be. Then highest argues why, then lowest argues why, then revote.

Start with @D--M as a baseline. Most important part is always just doing and dont be afraid misjudging stories because exactly those stories will add value to the points you give later.

Scrum is about being transparent and always try to inspect what you do and adapt to it to improve. So JUST DO IT!

Scrum takes time. So your estimations will only be meaningful after a few sprints and your velocity will emerge in the process. Your first sprints will be chaotic and most likely fail. That's ok. The storming (team building phase) is one of the hardest first challenge.

That being said: estimations are still estimations. You still will highly over and underestimate. Key is discovering the reasons for having done so in the retrospective and avoiding them in the next sprints.

Thank you all. @D--M that scale is exactly what i was hoping for to find here. As starting point its perfect. And yes ... we are expected to fail on first few sprints, to be honest .. i dont think we will be fully operational scrum team even at the end of the year, (too little time for that with all other classes) but as experience I am really curious for this, as i only worked alone fullstack so far.
And also, they gave us those cards, there is even "100" :D and "?" card.
I am still on the "yeeey new project optimism phase"

@Chill
I've been doing this for awhile... Our team still fucks it up so hard. Just less often :P

As the others said. Its okay to get it wrong, just on next sprint, go through the stories and figure out what blew up and why. Then apply that going forward.