As a scrummaster, I have already observed such type of behaviour in my team in different scrum events. So ideally I put question over table so that becomes motivation to get discuss further more around this topic. It becomes very effective in Daily standup where team understand overall with respect to our sprint commitments where we are. Even for Retrospective meetings, also that question becomes point where team do more brainstorming. It's all about facilitation skills as you mentioned
This video contains some good advice but leaves out some that might be relevant. Sometimes you have to consider should you re-launch the team or dismantle the team all together. Sometimes the quietness and not collaborating is a facilitation thing, sometimes people are shy, sometimes there is something that you can actually fix - even if it would take time. But sometimes your team has hit that point-of-no-return where trust is lost and individuals are acting in such a manner that is cannot be fixed. Then, as a scrum master, you have to act and seriously consider the option that the team might not be vital. I know a case where a very good developer (with all soft skills needed) joined up in a "quiet team". Even though he tried his best with the scrum master, he eventually was swallowed by the team anti-collaboration mentality. After 6 months, he left the company because he was afraid that the team spirit would ruin his career (in the company but also with the new job if he kept with the teams mentality).
SM across time zones - what do you do differently when working with remote teams, where there is a time difference? Not related to facilitation necessarily, although there may be a second question there - tips for increasing engagement & collaboration when there are time zone and cultural differences.
My scrum master always do that. Keep quiet after asked question.. and most of us then start talking. But the one who start talking then is the same guy everytime... hmmm
Then a good Scrum Master would know to approach that individual, on the side, and make them cognizant that they are always the first to speak. I have dealt with this issue quite a bit in my time.
I was appointed to act as scrum master because they noticed my great facilitation and organizing skills. Most of the time my team is too quiet and it is challenging to get their engagement.
Right or wrong, I'll ask the team to promote another backlog item into the sprint. I don't want a process (scrum) to get in the way of delivering value to the customer. :) I don't care so much about planning mistakes like this and fortunately work for an organization that would prefer we focus on delivery over following rigid protocols.
Excellent view both! The Scrum Master filling the space instead of the team is so true in this.
As a scrummaster, I have already observed such type of behaviour in my team in different scrum events. So ideally I put question over table so that becomes motivation to get discuss further more around this topic. It becomes very effective in Daily standup where team understand overall with respect to our sprint commitments where we are. Even for Retrospective meetings, also that question becomes point where team do more brainstorming. It's all about facilitation skills as you mentioned
I loved this segment. It resonated with me and gave me several takeaways in which I can take action for myself. Thank you very much!!
This video contains some good advice but leaves out some that might be relevant. Sometimes you have to consider should you re-launch the team or dismantle the team all together. Sometimes the quietness and not collaborating is a facilitation thing, sometimes people are shy, sometimes there is something that you can actually fix - even if it would take time. But sometimes your team has hit that point-of-no-return where trust is lost and individuals are acting in such a manner that is cannot be fixed. Then, as a scrum master, you have to act and seriously consider the option that the team might not be vital.
I know a case where a very good developer (with all soft skills needed) joined up in a "quiet team". Even though he tried his best with the scrum master, he eventually was swallowed by the team anti-collaboration mentality. After 6 months, he left the company because he was afraid that the team spirit would ruin his career (in the company but also with the new job if he kept with the teams mentality).
Love your videos. I plan to make them part of my daily life at work. Thanks for the great content!
SM across time zones - what do you do differently when working with remote teams, where there is a time difference? Not related to facilitation necessarily, although there may be a second question there - tips for increasing engagement & collaboration when there are time zone and cultural differences.
Sooooper funny! I constantly struggle with "talking too much!" Blabber mouth I am, but always working on it. Thanks!
Love this video! However would love to hear some insight for those of us who are 100% remote teams
My scrum master always do that. Keep quiet after asked question.. and most of us then start talking. But the one who start talking then is the same guy everytime... hmmm
Then a good Scrum Master would know to approach that individual, on the side, and make them cognizant that they are always the first to speak. I have dealt with this issue quite a bit in my time.
Hey folks,
Can you please make a video on how agile teams should handle risks.. or how is risk management done in agile.
Best,
Dushyanth.
You may also think of using icebreaker to get the team out of their cold 🥶
I was appointed to act as scrum master because they noticed my great facilitation and organizing skills. Most of the time my team is too quiet and it is challenging to get their engagement.
what did you do to make team more engaging?
@@navneetsinghvi363 We are in a virtual setup. So I tried various formats of meetings that promote ownership.
@@visionedison pls can u give an example
Ryan, you are okay.🙏
Q: What does the team do if they finish all of the Sprint Backlog items before the end of the sprint?
Right or wrong, I'll ask the team to promote another backlog item into the sprint. I don't want a process (scrum) to get in the way of delivering value to the customer. :) I don't care so much about planning mistakes like this and fortunately work for an organization that would prefer we focus on delivery over following rigid protocols.
Pull an appropriate size item from the prioritized backlog!
Man great vid
Ryan does talk much more than Todd..
Very true. :-) --Ryan