YDS: Do Developers Have to be Full-Time Scrum Team Members?

Today's question asks if Developers on a Scrum must be full-time Scrum Team Members. Check out today's video as Todd and Ryan discuss the pros and cons of part-time and full-time Scrum Teams members. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

How does your Scrum Team handle the team membership? Let us know in the comments!

This is one of those Scrum Master interview questions about Scrum that can throw you off. Do you understand how the focus is impacted when people are on multiple teams? These Scrum Master day in the life questions can be tricky. Perhaps some Scrum Master training could help? Want to learn more about Scrum?

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 #professional scrum

[vkxcqsn]

Definitely agree. We didn’t have a say, in a previous organization. Having the core team split across two teams created a lot of stress for everyone. We even had a developer who was a ScrumMaster and developer split across 2 teams. In taking a deeper dive into Scrum, I see people were not able to fulfill their accountabilities to the fullest extent. The larger issue was the organization had taken on too much work for the number of people available, and we couldn’t expand the workforce. Strategy was needed at the higher levels.

That said, 90% of the time we had no issue sharing specialists who worked on the infrastructure (except cyber) - i.e. System Admins, Network Engineers, HW. Although there were System Admins that had specialized knowledge of systems. So, we had to be a little more careful in making sure they were available for major testing events.

It will be interesting to see how this plays out in my new organization as I don’t think we have dedicated developers. I think Work Item Aging could become my friend.

[MichaelBacarella]

Great topic and something I need to address with my team. Thank you.

[supergirls]

Agree what DJ RR said lol. Context switching will decrease the quality of the product or lose time for developers. I like the term of the core people of the team. If that architecture specialist is the core people of the team, I think PO should think about how to make her as the full time developer. Agree with me? DJ RR and Todd (should have a nick name for you too...coming up soon..or DJ RR can say something about Todd for me to think about one lol)
--Junlong.

[satishmlg]

Its a great topic.
I have a Question.
How do u describe Servant Leader relationship between Scrum Master and Squad?
I am not comfortable using - Servant in the modren just world

[amandalewis]

We have some part-time team members (like our DBA) who float in and out as needed. But we have some other part-time team members like BAs and PM who are on all of our daily scrum calls but who are also on the other teams in the company. When you have part-time team members like that, should they be part of the sprint retrospective as well? Or should only the core team members be part of that? How is psychological safety in a retrospective impacted? And how do you weigh that against the benefits of bringing in more perspectives on improving process?