You want to be a good Scrum Master it? I think so, unless you are a product manager or other roles. I, as a Scrum Master has more than 20 years, all these years, I have given a lot of advice, but also received a lot of advice. I think I have a selection of the best ten suggestions for everyone.
1. If the team did not discuss, please do not make any commitments on behalf of the team.
As a Scrum Master, you have no right to accept on behalf of the team needs to change, no matter how small it is. Even if you can completely determine the teams to get it. So you can answer: "I need to communicate and then confirm whether the team can accept." Of course not promise any delivery dates and the team in the absence of deliberation, deliverables, or any other thing. Of course, you may not always have full convene meetings to communicate with everyone, in some cases, part of the relevant members of the team after the communication is also possible to make a decision. However, this is still a team decision, not your decision.
2. Remember, your goal is to make the team look great.
As a Scrum Master is not to make them look great. When the team looks great, you naturally look great. When the team does well, then they look great. When people outside the team began to wonder if needed you, you know you did a good job. Yes, if your boss wonder if needed you, it was horrible. However, a good boss will know your skills and expertise to make you seem unnecessary, and in fact you are indispensable. I believe the difference between your manager may seem unnecessary and need not actually understand.
3. Do not use agile team rulebook to hate
Scrum and agile are not included with the rulebook (although some people attempt to create a rulebook). If your product users, please consider writing user stories. But the story is not necessary agility. If anyone needs to know when you deliver: Please estimate, if nobody wants to know, maybe you can not estimate. If you think you do at the end of Sprint Review Sprint, receive feedback too late, please review the complete development of each function. Remain agile agility refers to respect for creation principles and values. If you just mechanically these rules, you probably will not go too far.
4. Nothing is eternal, so please verify your process
Respect for the principle of agile One aspect is to verify your process. Encourage the team to try new things. Whether your team like a two-week Sprint, and they think perfect running? If yes, then great. Now let them try to sprint for a week or three weeks and observe the results. Experiments may not always be popular, but they are the best way to ensure that you continue to find new and better ways of working.
5. Make sure team members and stakeholders are depending on each other as peers
Fangli Yi team members and business stakeholders who each bring an important perspective to the product development plan. Therefore, everyone needs to be treated equally. If the gap between both sides, the entire organization will be compromised. Development teams need to understand the unique perspective of stakeholders are brought stakeholders need to respect the development team, including listening to the developer, he said: "This deadline is unrealistic."
6. Protection team, with more ways than you think
Scrum Master team needs to be protected to avoid being too harsh effects of the product owner or the interests of stakeholders, it is recommended to Scum Master, we often hear, this is a good suggestion. Sometimes, the person in charge of the product is very strong, but simply require faster, more. This will force the team to sacrifice quality in the end plagued the project. Therefore, a good Scrum Master can protect the team not affected by this. However, you may not know, a good Scrum Master should also guard against the team fall into complacency. Excellent Scrum team will continue to seek improvements. Some teams may not consciously consider themselves good enough, they really can be agile than before have been significantly improved. But even the best team, but also often have the opportunity to get better. Excellent Scrum Master Protection Team, will not let them feel no need to learn anything.
7. The failure to remove from your vocabulary
I occasionally encounter some teams, if they failed to deliver at the end of the Sprint All contents of their plans, they will be called the Sprint, "Sprint failed." I do not think this is a failure, especially if the team completed most of the planned entry, or they skillfully deal with emergency situations. When a basketball player the ball toward the basket and score, it is called Goal (Field Goals). If a player did not vote, which is called the shooting attempt (Field Goals Attempt). Not a failure but a try. Excellent Scrum Master to help teams adjust their thinking so that they realize that Sprint and functional properties failed to meet expectations is not failure but a try.
8. regularly praise, but always sincere
One day, I told my teenage daughter, I am proud of her, she was elated at once. This should not surprise me. Who would not want to know a person very proud of them? But the way she reacted made me realize that I can not always tell her that. I think I told her that it is equivalent to some obvious things, such as "You're high." But I know that is not true. Never provide false praise. No one wants to hear this. But when you find a good job your team members to do the time, tell them. They probably will not often hear.
9. Encourages the team to take over your job
Agile unfamiliar team will be heavily dependent on their Scrum Master or coach. Team may not know how to make daily station will be completed in fifteen minutes. Or they may not know how to work staggered, and the importance of cross-functional teams. An inexperienced team as well. Child learning to play the coaches need to teach them everything. When my 6-year-old daughters, their coach will be on the sidelines running the whole game shouting "kick, run!" If he does not do so, so young players will forget. Even if he shouted, occasionally there are some children sitting on the grass in a daze. The coach of young children compared with the World Cup team coach. In the World Cup team, the players have learned what to do. If the training time, late coach, the players know what kind of drills or training exercises to start the day. World Cup coach does not need to remind the players to play and run. But the World Cup team will never tell you they do not need coaches. No matter how good agile team, I think they can still benefit from counseling or coaching in Scrum Master. However, the team will be more agile excellent initiative to learn to mastery of skills needed for product development.
10. Shut up listen
Many times, listening, silence is the best coaching, let the team find their own answers. This may be difficult. When you see your team is trying to figure out what to do, it is natural to want to chipped and provide recommendations. But if you solve the problem, or easily provided advice, team members will be waiting for you to solve every problem for them. I do not want to imply that you can not offer any advice. You're a smart man, otherwise you would not have served as a role now. But as a good Scrum Master, to help the team learn how to solve their own problems. If you solve every problem faced by team members, they have no opportunity to know themselves okay, I can get themselves these questions. Above, that I give to you ten suggestions that you think something is missing in this list of suggestions it? I'm sure I must have missed some good ideas. What is the best advice that you received or given as a Scrum Master that? Please share your thoughts in the comments below.
Author: Mike Cohn
English Original link:
https://www.mountaingoatsoftware.com/blog/ten-sentences-with-all-the-scrum-master-advice-youll-ever-need#comments