What Does a Scrum Master Do All Day – Role & Responsibilities | Will Jeffrey | Skillshare

What Does a Scrum Master Do All Day – Role & Responsibilities

Will Jeffrey, Professional Agile Trainer

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
6 Lessons (13m)
    • 1. Welcome

      1:09
    • 2. Why is he here

      1:35
    • 3. Typical tasks

      1:57
    • 4. How Scrum helps

      4:46
    • 5. Responsibilities during the sprint

      2:38
    • 6. Conclusion

      0:41

About This Class

The ScrumMaster is one of the most undervalued roles in Scrum and Agile. Most teams that are just starting out don’t see the value of having a full-time ScrumMaster, and they try to combine this position with that of a developer or tester so that the ScrumMaster is “working.”

It’s one of the most common misunderstandings of the ScrumMaster’s role, and the majority of novice groups struggle with it. They say, “We understand that team members have to produce the software product; they are working hard. They have to learn cross-functionality and help each other. They have to cooperate. We also feel good about the Product Owner’s role because that person has to define a vision and negotiate requirements with customers.

But what about the ScrumMaster? What does he do?”

What are his responsibilities? What is supposed to do during the sprint? How Scrum helps to fulfil his role?

All these questions will be answered in this course. I hope you will enjoy it!

References:

  • The Great ScrumMaster #ScrumMasterWay - Zuzana Šochová
  • Scrum shortcuts without cutting corners agile tactics, tools, & tips - Ilan Goldstein

Transcripts

1. Welcome: the scrum master is one of the most undervalued roles and scrum and agile. Most teams that are just starting out don't see the value of having a full time scrum master and they try to combine this position without of a developer or tester so that the scrum master is working. It's one of the most common misunderstandings of the scrum master's role, and the majority of novice groups struggle with it, they say. We understand that team members have to produce the software product. They're working hard. They have to learn cross functionality and help each other. They have to cooperate. We also feel good about the product owners role because that person has to define a vision and negotiate requirements with customers. But what about this room? Mestre? What does he do? What are his responsibilities? What is supposed to do during the sprint and how scrum helps to fulfill his role? All these questions will be answered in this course. I hope you will enjoy it 2. Why is he here: the scrum master might end up. Is the secretary of the team quite a boring position? Right? Such a scrum master takes care of the cards on the scrum board, removes every obstacle himself right away and is close to making coffee for the team so they can focus solely on work. Sound familiar? Another common misinterpretation of the role occurs in an environment where someone assumes the scrum master roll just because the company must implement scrum. Usually in a big corporation, people often say we have to have a scroll master to do from right but we can't use a good developer or Q A because they have to do programming are testing. So the scrum master in such an environment is often a wimpy, quiet person. Who's qualifications for being promoted to scrum master are that he is not a good developer . Bearing this in mind, the good scrum master can't be seen as an additional expense. As someone who is not doing anything useful, he needs to be seen as the way to skyrocket the team's performance. A scrum master rains to have not just a good team but ah, high performing team and in such a team, a scrum master more than pays off. Remember that the scrum master is an expert on the agile and scrum mindset and a true believer that agile and scrum are the right ways to be successful. 3. Typical tasks: Here are a few examples of what scrum masters do. Watch the team and detect problems. Process personal organisational example. A team member works alone on tasks and doesn't collaborate with a team. This can lead to problems like knowledge silos, hard to maintain products, finger pointing, no shared responsibility, undone work, omitted integration or decreased team motivation. A scrum master needs to put this problem on the table on earth, the underlying reasons, and then work towards solving the issue with the whole team. Conduct regular meetings to find sources for pressing problems and help the team to come up with actionable solutions. Example. In a retrospective every two weeks, the Scrum master uses established methods to unearth and identify important problems hindering the work of a team. He coaches the team towards coming up with solutions and sees that the team implements these solutions during the next two weeks, educate product owner and development team and their roles. Example. The product owner wrongly tries to estimate efforts without the development demand and pushes thes estimations upon the engineers. This is a bad practice. A good scrum master will make clear to all parties that the role of the product owner is to say what needs to be done, and the role of the development team is to say how to do it and how long it takes. Of course, these are just a few examples, but by now you should get an idea of what a scroll master does, and you should also begin to see that a scrum master is not just the person scheduling meetings or fetching coffee. 4. How Scrum helps: Although almost everything in the scrum framework helps the scrum master to do his job, there are a few things that can be particularly helpful for him. Retrospective. This meeting is conducted after each sprint. Its sole purpose is continuous process improvement. The focus is on work, process and collaboration, not on the product here, the team on air. It's what goes well and what doesn't and it comes up with actionable solutions and improvements that can be implemented right away. Think of the retrospectives like a lessons learned, but in time to really learn and change something. The scrum Mestre moderates this meeting and helps the team to stay focused and keep improving impediment backlog. The team or the scrum master can collect obstacles so called impediments in a simple list called the impediment backlog. This can help to keep track of issues in the work process and prioritize the most pressing obstacles to be tackled. Retro action items, the result of any retrospective meeting or a handful of very specific and actionable tasks to be implemented. To improve the process, the scrum master makes sure that each were introspective. Yields about 1 to 5 improvements to be done in the next sprint keep the number of action item small. Tackling too many impediments at once will lead to paralysis into no improvements at all. Sprint sprint is the time when the team works on the product. It takes up 90% of the projects. Time a scrum master needs to watch the team and communicate with them all the time to detect and remove impediments. Daily Scrum This short daily meeting is for the development team to coordinate. This is an awesome opportunity for any scrum master to pick up possible issues that need to be resolved. Sprint Wall All work a team needs to do during a sprint is in the Sprint backlog, most commonly in form of index cards on a wall. Looking at this wall in how cards move or not move can give this grandmaster hints towards possible impediments. Definition of done. Many problems in the work process of a team are resolved by improving the definition of done. If, for example, feature development is slow and the team found this to be caused by bad code quality, a possible solution could be to expect a code reviews automated tests and re factoring to be done on every feature before marking it done. One of the key phrases of scrum is the self organized team. Everybody talks about it, but it's difficult to understand it and hard to develop it. The self organized team is an entity that can decide how to handle day to day tasks in scrum. It's limited to how should we organize ourselves so we can deliver the sprint goal in sprint backlog to an agreed upon quality specified by the definition of done. In other words, the team should be able to decide who is going to work on which task, how team members can help each other when they need to learn something new and how they prioritize their daily work. In the absence of external authority, some teams believe that self organization grants them unlimited power to decide anything on the planet. That isn't what is meant by the self organized team. In scrum, every self organized team is self organized only inside the given boundaries, scrum boundaries, air determined by the process limited by sprint goals, backlog and delivering working product. At the end. If some team members are not happy with something, everyone on the team has to discuss it, understand each other and, as a result, changed their ways of collaborating and helping each other. The most important characteristic is the mindset of every individual. The good team has an attitude of we instead of I. How can I help the team to solve it? What can I do for the others instead of I don't know anything about it? This is not my problem. The self organized team is a living organism, and every team member effects how strong or weak this organism will be. Team members who take responsibility and start to be accountable for the self organized team entity instead of themselves as individuals or one step closer to being part of a great team. The scrum master's role is to support team rather than individual behavior. He must create such a team from individuals by reminding them that the team is an entity and is more important than individuals. He must always encourage team members to help others rather than hide behind their own tasks. 5. Responsibilities during the sprint: the scrum Master's responsibilities include the following. Encourages the team to take responsibility and supports the team. Single identity and goals. Enables transparency and collaboration. Removes impediments by encouraging the team to take over the activity. Understands the agile and scrum mindsets and continuously educates himself. Maintains agile and scrum values, Helps others to understand and follow Scrum. Protects the development team when needed, facilitates scrum meetings and helps the team to become more efficient. Most scrum masters have trouble with the question What does a scrum master do during a sprint scrum master is a leadership role. One of the aims of the scrum master is to make others work better by focusing not only on one scrum team but on the overall organization. Are you surprised that the scrum master must be a leader? So here it is The scrum master is not just someone who understands scrum He is much more than that The scrum master cares more about long term goals and strategy than a short term hard metrics Leaders air not driven by time sheets, they have a vision and their self driven and creative You can call the scrum master a servant leader which actually refers to ancient Chinese philosophy. It's about putting your team first and yourself second and about improving yourself in the following areas, listening to others. Empathy, healing of relationships, awareness and self awareness as a leader. Use of persuasion rather than relying on positional authority. Conceptualization the ability to keep the bigger picture in mind and think beyond day to day realities and short term goals. Four. Side intuition that enables you to link lessons from the past with the current state and future decisions. Stewardship being open and serving others commitment to the growth of others. Building a community is a viable life form. Remember, Scrum master is a leadership position. It requires creativity, vision and intuition to succeed. Good scrum masters are empathetic good listeners and ready to heal relationships. 6. Conclusion: remember, Scrum Master is a leadership position. It requires creativity, vision and intuition to succeed Good scrum masters are empathetic good listeners and ready to heal relationships. I hope you enjoyed this course. You're now all set for being a good scrum master.