Wow wow, you are so good in teaching someone who hasn’t gotten any idea about scrum. You give a day to day life examples and relate to the professional aspects in the field of scrum. Than you very much. I have learned a lot today from you ❤❤❤❤
The content was very informative but how to know if they user story is well pointed is more about understanding if your team is over estimating or underestimating. Mostly when you have a teach lead it make it easier for him to help on estimating since he can help clearing some misunderstandings. But the best way to know that is on the velocity when you estimate and is not able to make the minimum or even is to above the maximum then you did have an estimation problem and then you need to investigate those who over or under estimate. The onboarding part you forgot some part on it: you said presenting the team charter, you said making sure they get all they equipments, process( Jira), but you forget about: walking them through the product( product roadmap and what we are working on) the walk through somehow. And then the observer part( shadowing other team member to get to better understand what is going on for like 3 sprint before starting the work. But for a scrum master he can be doing the job and decide to assign himself most of those task.
By checking their work schedule and having a conversation with them about any planned time off, holidays, sick time off etc. Full capacity just means they will be fully available throughout that Sprint and have no planned time off. Emergencies can however affect full capacity, as these are unplanned. An emergency could be like the team member has a sick family member, bereavement, natural disaster, sudden health issue etc
