I've been in your team and communicate well, you're probably not with the team, but a lot of them and a similar team. The team and I look forward to share their Scrum Master to do six things.
1. Help them understand border duty
Agile teams were told that they are self-organized. However, this does not mean that every enterprise self-organization are exactly the same. For example:
- Whether the team has the right to add to the team's technical requirements in Sprint?
- Whether the team can decide who in this team?
- Whether the team can change their length in Sprint without asking the Scrum Master?
- In the case of unlicensed teams in tools, group activities to build or how much money to spend on anything else?
- 。。。。。。
When the team was first told that they are self-organizing, they usually are struggling because they do not know what that means. As a Scrum Master, you need to help the team understand the responsibilities of the border they are free to operate.
2. Let them feel safe
Scrum Master of an important task is to create a sense of security. For example, Sprint teams to plan without having to worry if they have not completed all their expectations are yelling. Teams need to deliver high-quality results, but if a defect because of negligence led to the production environment, the team honestly admit mistakes, they know that will not be in trouble. When asked how long it takes to complete these functions, the team can answer truthfully without fear of delayed or early completion will have a bad effect.
3. Praise them
Everyone likes to hear, "You have done well, that's great." Before I sat down to write this article, when I walk the dog, and met a lady with a beautiful brown Labrador dog, I said, "your dog is really beautiful ah." Her face shiny, smiling. I guess she must have a lot of effort on the dog's dress, she was obviously very grateful for this praise. Your team is the same. When someone did a great job, let them know. Even a simple "You're great!" Can also help. Of course, the attitude to be honest, once you start looking for opportunities to praise team members, you will find a lot.
4. support them
Team needs your support. Remove obstacles to help the team be part of your duties, but more importantly, you should try before problems become obstacles to remove it. Support team not only deal with obstacles. When you're always honest with them and let them feel fair, the team members will feel the support. What it preaches. When you tell your team members will do something, immediately went to get it done. You help the team and let them accountable for their commitments to use the same or higher standards for yourself. Approachable. If you are a bad temper every day, then you can not expect team members to come to you when you need help. Conversations with team members. Do not say too much, so as not to affect the work of the advance team, but you should be aware of everyone's performance during the Sprint. We know when to help, even if only to listen to, or for someone to bring in a morning cup of his favorite coffee.
5. Let them feel very cattle
The worst Scrum Master I met who have a common characteristic: they think that all this is to make himself look good. In the Sprint review meeting, the Scrum Master will say, "Let me to show you the results of my team." Scrum Master work is to make the team look great. This is not formal, but felt. Excellent Scrum Masters do everything to help the team members. Then they know the team members to ensure the organization is well under way they work.
6. know when to break the rules
Scrum few rules, but the reason they exist is very good. Each team agile and help to increase the likelihood of success. But, as the saying goes, the rules meant to be broken. You want your team can break the rules at the appropriate time. Sometimes common sense prevail, and the rule will hinder common sense. A good Scrum Master will recognize these situations. For example, Sprint is never extended the rules I follow, is usually the case. I had to break it? Yes, occasionally, but always for good reason. 3 hours yes yes Sprint Retrospective maximum duration. 99% of my review is done in a shorter period of time, typically much less time. But I coached the team to break through the three-hour rule? Yes, we occasionally discuss a very hot topic, and it seems to be better to postpone than to continue discussions. You can become a good Scrum Master. Become a good Scrum Master, there is no secret, magical or mysterious things. You need to do a lot of things for the team, all that make you really appreciate what your past leaders and managers do for you.
7, how do you see?
What do you think of my list of missing it? If you are a team member, Scrum Master wanted to get anything from there? If you are a Scrum Master, I have missed something your team want? Please share your thoughts in the comments below.
Author: Mike Cohn
English Original link:
https://www.mountaingoatsoftware.com/blog/six-things-your-team-wants-from-you-as-their-scrum-master