Preparing for the Certified Scrum Master exam takes time. However, in addition to diligence and patience, you also need understandable learning materials. We present you with detailed topics.
Certified Scrum Master professionals with a lot of experience share their knowledge. Use the texts below to prepare for your exam. You can check the real mock questions for the BVOP Senior Scrum Master exam here.
The focus of the topics is the Daily Scrum event. We cannot cover all the topics about the Scrum exam in one article. That is why we share the main topic as a start.
Sample topics for exam preparation for Scrum Master
The Daily Scrum meeting begins and a member of the Development team begins to ask questions of the other participants.
If this team member is chosen as the facilitator and asks the questions, then there is no problem. Because if he at the Daily Scrum meeting starts asking questions on his initiative and they are different from: What did I do yesterday that helps the Development team achieve the goal of the sprint? What will I do today to help the Development team achieve the goal of the sprint? Do I see any obstacles that prevent me or the Development team from achieving the goal of the sprint? This means that this team member does not understand exactly how the Daily Scrum meeting should be held and what the purpose of this meeting is. The task of the Scrum Master is to explain all the unclear details, to encourage the team, to help the team learn how to effectively, observing the fixed time of the meeting (15 minutes), to conduct this meeting. Reference: “Free training to prepare for the Scrum Master Certification exam”, https://www.islandjournal.net/scrum-master-certification-exam/
The Daily Scrum meeting begins by appointment. To dilute a tense moment, the Scrum Master can suggest to the team to use a soft toy or ball. After a team member answers his questions, he throws the ball to any participant who has not yet answered. In this way, everyone will be focused during the meeting and watch what happens, because everyone can be next and he will also follow those who have already presented themselves and who are not yet, so as not to throw the ball to those who have already reported today. Concentration is very important, each performance should not exceed a few minutes, in the process, it will teach people brevity and conciseness.
External stakeholders and the Scrum team
You receive an email from the marketing department upstairs. As they do not know where you are holding your Daily Scrum meeting, they ask you to show it to them in advance so that they are not late.
In this situation, the Scrum Master should ask the marketing department what questions, problems, or obstacles they have and why they want to attend the Daily Scrum meeting. His task is to explain to the marketing department the purpose of this meeting and that it is held only for members of the Development team, where each member presents very briefly what he did the day before, what he will do today and what problems and obstacles he encountered or anticipated. This meeting has a very short fixed time (15 minutes), the presence of outsiders carries the risk of the team losing focus, anxiety, opacity, non-compliance with time frames may occur, and as a result, the goal of the Daily Scrum meeting is not achieved. Reference: “Free preparation for the Scrum Master certification exam (CSM, PSMI, PSMII, BVOP)”, https://brightonbot.com/preparation-scrum-master-certification-exam/
The scrum master should suggest and assist the marketing department to discuss with the team all issues outside the Daily Scrum meeting. In this way, the Scrum principles and way of working will be observed and there will be order.
A representative of your client is on a business trip to your office, but only for a very short time. He will leave early in the morning tomorrow. 15 minutes before your meeting, a team member asks you to call him so that he can provide as much important information as possible while he is here.
The Scrum Master must explain to the colleague that the Daily Scrum meeting is held for the Development team, that it is very short (15 min). Likely, a team member has not yet fully understood the purpose of the daily meetings. One of the responsibilities of the Scrum Master role: supporting meetings and Scrum events, training and guiding all those involved in the product on Scrum practices and concepts. It is commendable that the colleague is interested in product development and is enthusiastic, yet receiving important information brings business value to the product. The team also has a Product Owner who works with stakeholders. Reference: “Product Owner role in Scrum and real problem situations”, www.vbprojects.org, 2020 The scrum master can contact him to have a conversation with the client’s representative. Daily Scrum meeting has a maximum time of 15 minutes, The Scrum Master can ask the client’s representative to wait until this meeting is over to discuss the details, in the end, both parties should be interested in achieving a good result.
The Scrum Master must insist that the Daily Scrum meeting be held properly, on the other hand, he must assist the team in terms of important information, for this, he should include the Product Owner role. Also, in addition to personal meetings, information can be exchanged by phone, email, etc. Reference: “Professional Scrum Training training and certificate from BVOP.org or Scrum.org? Which one to choose for Scrum Master Certification?”, https://medfd.org/professional-scrum-training/
From one point of view, it is very important to strive for a fast and quality result, on the other hand, the rules and the way of working of Scrum must be observed, every event is important, violations of the way of Scrum events can lead to many negative consequences.
Just before your Daily Scrum meeting, your director sent you the following email:
“Hello! Can colleagues from another department come to your daily team meeting to observe how your Scrum events are going? I promise they won’t interfere in any way.”
According to the Scrum Guide Daily Scrum meeting is held only for members of the Development team, nothing and no one should interfere, the team should not lose focus, should not feel discomfort or anxiety. The scrum master must try to avoid situations where outsiders attend a daily meeting. Reference: “Advanced Certified Scrum Master training course. Free, online and modern”, https://pgov.org/advanced-certified-scrum-master-training-course-free-online/ On the other hand, as an exception, colleagues from another department may be present. The Scrum Master should ask for complete silence from colleagues from another department, and should also ask team members if they mind because if it turns out that people do not want anyone else to attend the meeting, the Scrum Master should reply to the director that it is not a very good idea that we strive to develop a fast and quality product, and this is achieved if the team is cohesive, self-organized, has transparency and a calm comfortable atmosphere.
Product Owner and Daily Scrum Meeting
Your Product Owner comes to your Daily Scrum meeting just before it ends and politely asks everyone to repeat what they have shared because after a while he will meet with a client representative who has asked him for an up-to-date development situation.
The Scrum Master must help and facilitate every event in Scrum to take place by the Scrum rules. Perhaps the Product Owner role does not fully understand the purpose of the Daily Scrum meeting, how and for whom it is held. Reference: “Advanced Certified Scrum Master Certification Training” by Ashton Williams, Scrum Time, ISSN 2652-5445, https://scrumtime.org/advanced-certified-scrum-master-certification-training/ The Scrum Master must ask the Product Owner to wait for the meeting to end, and then all the issues can be discussed. The scrum master should explain to the colleague that there is no point in the team members repeating what they shared because Daily Scrum is a meeting where each member of the Development team presents to the others very briefly what he did the day before, what he will do today and what problems and obstacles encountered or anticipated. The current development situation would be good to discuss after the Daily Scrum meeting. And the team members should not feel discomfort, these meetings are just for them, it depends on them how the team will work on the product.
Daily Scrum your meeting is running. Tomorrow is the last day of the sprint. A few User Stories remain unfinished, which are certain that they cannot be completed by tomorrow.
Here it is already clear that the team will not end on time, such situations happen, especially given the flexible work models. Stakeholders will not be happy, because everyone prefers to get a ready-made increment at the end of the Sprint. In my opinion, the Scrum Master should notify the Product Owner or management to contact the customer. Also, the Scrum Master should analyze the situation and help the team understand where the problem is, why it happened, to draw conclusions that will help avoid mistakes in the future. Reference: “Certified Scrum Master vs Professional Scrum Master”, https://wikipedia-lab.org/certified-scrum-master-vs-professional-scrum-master/
In this situation, not only the Development team can be blamed. Perhaps the Scrum Master also failed to motivate the team to be self-organized and proactive or failed to explain the purpose of each event in Scrum. However, we have a situation where the team is working on the increment and only on the last day announces that it will not end on time. Daily Scrum meetings make it easy to inspect work, find any problems and find appropriate solutions. After discussing all the issues and problems, the team reviews its progress in its sprint to see how it is doing. Burndown Chart is a popular graphic diagram that shows the progress of the work, visualizing the work done and the remaining work. Reference: “Problems of the Scrum Master role with the Sprint Review and Scrum Sprint Retrospective meetings”, https://www.nebraskasocialstudies.org/problems-of-the-scrum-master-role-with-the-sprint-review-and-scrum-sprint-retrospective-meetings/
According to the results in the progress chart, the plans are changed, if necessary, to fulfill the goal of the sprint.
The Scrum Master needs to consider why the team that has the Burndown Chart has not taken any action to speed up the process, where the source of the errors is. More on the topic: “Why do you want to be a certified Scrum Master?” by Rita Gavelis, https://www.mmrls.org/why-certified-scrummaster/
There are other reasons: the team did not understand User Stories, the team’s speed was inaccurate, the Product Owner role did not provide accurate enough information, the Scrum Master failed to perform its functions, the team failed to be self-organized, there was no transparency and work inspection. it may even need additional resources.
The Scrum Master needs to encourage each team member to analyze the situation, to be honest, and proactive, to assist if the team does not fully understand the Scrum way of working and Scrum principles, to protect the team if something or someone interferes. Reference: “Best Scrum Master Certifications for 2021 and 2022”, 2020, (EduWiki.me), https://eduwiki.me/best-scrum-master-certifications-for-2021-and-2022/
Members of the Development team
One of the Development team members asked your product owner to attend the meeting to share important information, but the others are strongly against it, as they believe that your Product Owner will understand important details about how they are implemented.
The scrum master must take care of the team to have harmony, calm and comfortable atmosphere. In this situation, he should explain to the colleague that the daily meetings have a certain format and purpose, he should offer him to organize the meeting with the Product Owner after the Daily Scrum meeting. In this way, all parties will be satisfied: team members will not feel discomfort, the Product Owner will receive important information, the Daily Scrum meeting will be held in compliance with the time limit because it is not known how long the discussion will take. this information. Reference: Be a Product Owner, PMI.org
A member of the Development team said that he tried all day yesterday to speed up the responses of your client’s marketing department. They take too long to answer and do not send him the information he needs to complete his work.
One of the tasks of the Scrum Master role is to help the team when problems arise, something or someone interferes with the work process. A member of the Development team of the Daily Scrum meeting said that the marketing department of the client is slow and does not send the necessary information. The scrum master should point out this problem and suggest to the team members to continue the meeting, they should not delve into the discussion of this information, because the Daily Scrum meeting has another purpose. After the meeting, the scrum master (alone or through the Product Owner role) should contact the customer’s marketing department to ask them to send the necessary information faster, he should remind them that any delay hinders the product development process.
Your colleague is late for your Daily Scrum meeting and has sent the following email with answers to the usual team questions:
“Hello! Yesterday I was working on recovering the user password. It’s not ready yet and I’m continuing today. I think I will succeed by the end of the day. I encountered several problems, but I got around them quite flexibly.”
First, the Scrum Master must do everything necessary to prevent similar situations in the future. The colleague is late and sends an e-mail, but personal presence is more important. He wrote in the e-mail that yesterday he was working on recovering the user password and will continue today. It would be better for him to formulate his answers in another way, for example: “From what I planned yesterday, I did the following … (it is important what he did to achieve the goal of the Sprint), I failed to do because … ., I encountered several problems (it would be good to briefly share them with other team members, this information can be useful).
Personal presence is very important because team members are united by a common goal, area of work, tasks, and if there are people on the team who work together with a late team member, this delay can lead to a lack of detail or ambiguity.
The scrum master should encourage team members to respect each other and remind them that the Daily Scrum meeting is held so that participants can communicate with others what they are working on and so their work becomes transparent to others. This makes it easier to inspect the work, detect any problems and find appropriate solutions with the help of other members of the Development team.
For example, to avoid such situations (delays or absences) a common chat group can be useful. If a colleague does not come to the Daily Scrum meeting for one reason or another, he should notify in the chat that he is late today or will be absent in principle (this will be useful information for anyone who has had joint plans with this person), also briefly you need to outline the answers to the main questions. At the same time, other team members unobtrusively, as if hinting, should indicate in the chat that delays are not welcome and will not be encouraged. Personal presence is more important. In this way, people who are often late or miss the Daily Scrum meeting will be “noticeable”, which will be unpleasant for the latecomer and it will be uncomfortable for him to be late often.
During your Daily Scrum meeting, a colleague tells the others:
“Yesterday I was working on uploading the profile picture for users. Today I will create several automated tests with different common situations to make sure there will be no shoots. It turned out that the test server does not have libraries installed for all supported photo file formats. I will go down to the Development Operation colleagues today and ask them to put them on, and then I will tell you. In the meantime, know that you may encounter this problem as well. ”
In my opinion, the colleague gives clear answers to all three questions of the Daily Scrum meeting in this situation. He explains what the problem is and how he intends to solve it. At the same time, he did not go into details and said he would provide the information after going down to Development Operation colleagues. He can share it with other team members after the Daily Scrum meeting. The Scrum Master should ask the colleague if he needs help communicating with Development Operation colleagues because one of the tasks of the Scrum Master role is to monitor and remove obstacles from the work process, it acts as a buffer between the team and all external influences, problems, personalities, and phenomena.
During your Daily Scrum meeting, a colleague tells the others:
“Yesterday I was in the designers’ room to discuss the graphics for the next sprint. Today I will integrate all the icons in the registration form. I think there will be a small problem, but I will manage.”
In this situation, a question arises as to why the colleague discussed with the designers the graphic elements for the next sprint, it is more effective if work is done on the current sprint than to deal with work that is planned in the future. The colleague also answers: “What you did yesterday, what I will do today, there is almost no problem.” Such answers can be demotivating. It would be better to formulate the answer, for example, as: “From the work planned yesterday, I managed to finish this …. I failed to finish that, because …. I had such obstacles and problems ….”. In this situation, the colleague says that there will be a problem, but does not even briefly share any, not a single comment. Perhaps other team members will face this type of problem. There must be transparency, this is very important. In my opinion, after the meeting, it makes sense for the Scrum Master to hold a meeting with the team to explain, advise how to conduct daily meetings to have transparency, efficiency, a better inspection of the work, which will allow easier solutions to possible problems.