YDS: What Does a Scrum Master Do with a Quiet Team?

(United States)

February 12, 2021

Today’s episode of YOUR DAILY SCRUM: What Does a Scrum Master Do with a Quiet Team? Another day, another YouTube viewer question. This time a fellow Scrum Master wants to know what to do when working with a quiet Scrum Team. Todd and Ryan have been in this situation many times. Something to consider is whether or not you actually have a team??? Check out the rest of the video for more suggestions and Ryan's thoughts about the 90's era Chicago Bulls.

Ryan Ripley and Todd Miller are the author of Fixing Your Scrum: Practical Solutions to Common Scrum Problems. They are the co-founders of Agile for Humans, the premiere Scrum and Kanban training organization.

What did you think about this post?

Share with your network

Comments (5)

05:09 am February 12, 2021

Could this not be a red flag that the team does not feel that they have a safe place to talk? Perhaps including the team health practice as part of a daily scrum or as part of a sprint retrospective may help? In fact, would this even need to wait for a scrum event, as could this not simply be added to the teams board so that they could populate it during their own time when no one else is looking, especially if they do indeed not feel safe?

BTW, Todd is a great listener. ;-)

Irena Pavlovska Krivosheeva

11:35 am February 13, 2021

Have an other external person (or a scrum master) joining your daily. See what happens. Have on on 1 with all team members and try to build trust.

Irena Pavlovska Krivosheeva

11:39 am February 13, 2021

And Yess, Ryan is a good speaker, Todd as well. Ryan, try a role play with your buddy if you can :). Try to be quiet on the next episode, and let Todd to run a whole podcast. See what happens..

Smart

11:03 pm February 13, 2021

What to do when you have someone in a scrum team who dominates the team as team boss or manager?

02:15 am February 14, 2021

The SM should coach that person so that they understand that there are no bosses or managers within Scrum, and that it is the whole team who decides how to do things via collaboration.