YDS: How Do You Onboard a New Scrum Team Member?

How Do You Onboard a New Scrum Team Member? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

What do you think? Let us know in the comments!

Take a Professional Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti!

Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -

Join Ryan and Todd in a Professional Scrum Master course:

And make sure you subscribe to the channel!

DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!

FTC DISCLAIMER: This video is not sponsored by anyone.

Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.

#scrum #agile #scrummaster

[tomaszniemiec]

I know this might not be the most Scrumy approach, but what I like is something alike a journey checklist for the first days. We pass it to the new team member and mention to him that this is his quest, his task for the sprint to complete and he can ask anyone he wants, collaborate, do something on his own and so on. We somewhat add a second Sprint Goal to onboard the new team member and on our dailies we discuss how that goal is progressing :)

[mkeesing]

For new SMs, it’s nice to give one sprint to pair and one sprint to shadow if at all possible. If they are replacing someone, set them up for success and make it a smooth transition

[MarkBurville]

Great question, excellent ideas based on getting a new member involved with the team.
I would add another little thing, create that welcoming environment, meet the team and make it a visual exercise.
Having done this for quite some time, I have seen how this has always had a positive impact on all, especially motivating for the new team member.
The closer the team is to self-managing, the quicker the integration and that inclusion.
Thanks RR+TM 🌟
P.S. A new developer is arriving Tuesday next week :D looking forward to it.

[cleonf]

Yup, another great video :) Thank you RR and TM. TM I just loved those human related tips, and as Ryan mentioned I think is really really important that people (mainly the stakeholders) to understand that will take a toll in metric" in the short run. Especially people that still call other people "resources". Just a question for you TM and RR: would make sense to put the accountability of receiving the new Developer in the whole Scrum Team? Shall the Team do the preparation, bring the question the in advance: "Hey guys Tod is joining us in the next month, what can we do as Team to create an awsome 1st day for him and how can we best integrate him? How the 1st Sprint with Tod will look like?". Thank you

[himadridebnath]

How to onboard a New Scrum master when an existing Scrum Master leaving the team or company?

[moroccandoyouknow]

Nice episode as always. We need an episode on how to onboard a new SM. Thanks in advance.

[himadridebnath]

How to on Board a new PO when a PO is leaving the company - whom to involve in getting this done?

[zenexmachina]

I encourage team members to "pair" with the new team member and spend a day with each person. By the end of the Sprint, the new team member knows what everyone does and the way in which the team works from a social as well as task perspective. The associated pattern is reviewed at Retrospective and adjusted to improve the onboarding of the next person.

[franknyantekyi]

This was a valuable topic, thanks for the insights

[abhijitdash]

That was some great tips there. Thank you Ryan and Todd.

[Elmusiico]

Love the videos, you all have been extremely helpful in my journey as a new SM. We will be having a new teammate joining the team on Monday and will take this approach.

[danielkemp]

In your experience, what's the window on that short-term dip in effectiveness when onboarding a team member?

[geetank]

When we want to encourage pair programming when a new developer joins the team sometimes the existing developers are not excited about it as they say this slows them down since it takes up their time to answer questions and explain the work and the code to the new person. Hence, they add more story points to the user story. How to tackle this?