I've been working in Scrum projects about two and half years. Scrum and Agile were interesting for me since the beginning so I've been reading about it, watching how it is implemented and discussing it with friends. I thought that I got an idea and CSM training is just a mere formality. I wasn't right...
I thought that the Scrum Master role is to kind of help the Team or the Product Owner to figure out some solution for a certain problem, or even find it for them. This is the point where I misunderstood the role, I went to far. The Scrum Master responsibility is just to make sure that the Scrum is properly implemented. That's all. Scrum Master has to make sure that appropriate tasks are handled by appropriate Scrum roles, that responsibilities are divided in a Scrum way, that all Scrum tools are used when it is necessary and what is the most important that people want to use the Scrum because they understand it and found it useful. In order to achieve that the Scrum Master should react when roles don't follow the process and by asking appropriate questions and using appropriate Scrum tools find a reason and escalate a problem to an appropriate level and let it be handled by an appropriate role - this is one of the main goal of the Scrum. It means that the difficulty is to figure out questions which force people to take the responsibility and help them to find a real cause of a problem or understand the Scrum. I realized that my tendency was to make a decision which were in other roles responsibility.
It actually in a sense simplify a role, since Scrum Master doesn't have to make any decisions, doesn't have to know solutions for the Product Owner or the Team problems, he just have to take care about the Scrum - like actually the Scrum Master title says.
Recommended book: "Agile Project Management with Scrum" Ken Schwaber
I thought that the Scrum Master role is to kind of help the Team or the Product Owner to figure out some solution for a certain problem, or even find it for them. This is the point where I misunderstood the role, I went to far. The Scrum Master responsibility is just to make sure that the Scrum is properly implemented. That's all. Scrum Master has to make sure that appropriate tasks are handled by appropriate Scrum roles, that responsibilities are divided in a Scrum way, that all Scrum tools are used when it is necessary and what is the most important that people want to use the Scrum because they understand it and found it useful. In order to achieve that the Scrum Master should react when roles don't follow the process and by asking appropriate questions and using appropriate Scrum tools find a reason and escalate a problem to an appropriate level and let it be handled by an appropriate role - this is one of the main goal of the Scrum. It means that the difficulty is to figure out questions which force people to take the responsibility and help them to find a real cause of a problem or understand the Scrum. I realized that my tendency was to make a decision which were in other roles responsibility.
It actually in a sense simplify a role, since Scrum Master doesn't have to make any decisions, doesn't have to know solutions for the Product Owner or the Team problems, he just have to take care about the Scrum - like actually the Scrum Master title says.
Recommended book: "Agile Project Management with Scrum" Ken Schwaber
