The Daily Scrum event is important to any Scrum team, but it can easily be disrupted if a certified Scrum Master does not monitor the meeting closely.
During the Daily Scrum event, the Development team share their progress and problems while a professional certified Scrum Master monitors without disturbing the participants. However, if the Scrum Master role notices irregularities, it must intervene.
Here are some common sample situations that can be an obstacle for both the Development team and the Certified Scrum Master. The report may also be used for BVOP™ Certified Scrum Master training: https://bvop.org/scrummaster/
The meeting starts and a member of the Development team starts asking questions to the other participants.
Good start. However, it should be noted that this should not be taken as an ‘interrogation’ – the lecture states that no one asks the participants about the work done and the remaining work. Let’s assume that this is just an invitation to the other participants to get involved. Reference: Real Scrum problems of the Scrum Master role during the Daily Scrum meeting
You receive an email from the marketing department upstairs. As they do not know where the place where you hold your Daily Scrum meeting is, they ask you to show it to them in advance so that they are not late.
The way the question is asked sounds like the members of the marketing department is not part of the scrum team. In general, before starting the project, the Scrum Master must make sure that all participants in the Scrum team are informed about the process, how it works and where and how the different meetings take place.
The daily scrum meeting is held at the same time, every day, in the same place. It would be strange, or at least a huge omission on the part of Scrum Master, if team members were not informed about it. Reference: Scrum Master role and issues related to the team and project work
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.
Since a Certified Scrum Master often acts as a coordinator and seeks to facilitate the work process, I will try to satisfy my colleague’s wish – but only if the Product Owner is also present at the meeting. Things get a little complicated, but as stated in one of the previous lectures, the Product Owner is the person who communicates with the customer or customer representatives and he is the person who should try to obtain the information. Developers do not communicate directly with him. Reference: Advanced Certified Scrum Master training course
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.”
Well, if he’s late, then I can’t force him to attend. I can only hope for the information he sent me. Sometimes we are late for work. I will read the email attitude on behalf of the colleague and I hope that there will be no questions from others. However, he did not write that there were any obstacles. Reference: Scrum Master presents themselves to stakeholders and clients
I will hope to share with the rest of the team what obstacles he had – if he thinks they need to know. However, I will make sure that the fact that he is a little behind (it says that he failed yesterday, but he will be ready by the end of the day probably), does not hinder or slow down the work of the rest of the team. But a possible delay of a few hours should not be a problem.
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. “
It is very good that the colleague informs me about the problem. I will monitor how quickly the DevOps will respond and whether they will respond on time because this obviously slows down my team and will eventually contact their Certified Scrum Master (I don’t know if they are part of my team) if there is a need for resource allocation. Reference: Professional Scrum Developer course and Scrum Certification
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.”
I would like to know a few details about what exactly a problem he thinks may arise. Just purely informative, so that I can find out whether he will have this problem or whether it will reflect on the work of others. I will ask him if he will be able to complete his task, despite the problem, in the estimated time and if he needs more time or some help from others in the team.
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 representative of the client who has asked him for an up-to-date development situation.
I think it is generally a good idea (not only in the scrum but also in principle in every managerial/coordinating position) to take notes. Basically, the mistake in Product Owner is that it’s late (considering it knows we only have 15 minutes and everything has to go fast), but let’s just say it couldn’t for some reason. I will offer him my notes and hopefully enough information for the client.
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.”
I am aware that it is explicitly written that no one but the scrum team can attend such a meeting, but let’s say that the organization is new and the teams just want to learn from each other. I would not fail everything just because the bagpipe says that they can not be there – the organization people need to build good relationships and best practices and learn from each other.
I will ask the Product Owner if it is OK to attend and I hope he agrees. However, I will make sure that they do not interfere, comment, and interfere. If they have any questions or suggestions, I will suggest that they meet with me later or another day to tell/explain.
One of the members of the Development team asked your product owner to attend the meeting to share important information, but the others are strongly against, as they believe that your Product Owner will understand important details about how they are implemented and this will disrupt Development. their harmony.
‘Implementation method’ – this is not something that concerns the Product Owner. If the team has decided that this is the best way to implement, then things will be done that way. And if, of course, the final product meets the requirements. The Product Owner should not comment on this and the Product Owner is generally not entitled to be prevented from participating in the Daily Scrum. This is against the rules of Scrum.
The Daily Scrum 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.
Certified Scrum Master should keep an eye out for user stories that take a long time or drag on. It sounds strange if an objective (as far as possible) estimate of the tasks is made and everything goes according to plan, it turns out that the day before the end of the sprint there are several unfinished User stories. But let’s say so. It has happened and we must act quickly. I will immediately take the problem to the Product Owner and ask him, at a meeting with the development team, to remove the parts that will not be completed – just divide these user stories into separate smaller ones so that we can fit in the plan.
A member of the Development team says 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.
A certified Scrum Master should assist in this situation. Simply writing emails is not always enough for people to respond. I will call on the phone and even try to find them physically and ask them to answer as soon as possible. Reference: Certified Scrum Master vs Professional Scrum Master
This is something that happens very often in my organization, and my experience tells me that sometimes people are just overwhelmed with all sorts of tasks and can’t always judge what’s more important than anything else.
I will try to argue why the colleague from the marketing department needs to react quickly. If I happen to come across his boss or manager, I will inform him that our team expects important information from him and I would like the task to be prioritized (yes, I will not be the most important for them always, so they have to drop everything and to help only me, but still I have to protect the interests of my team above all).
Why do you want to be a Scrum Master? That’s what we asked a few Scrum students. Here is one interesting answer…
My name is Linda, I’m 34 years old. I recently started the BVOP Scrum training and I hope to receive my BVOP Senior Scrum Master certificate soon…
Scrum is a popular product development methodology used mainly in software projects and is considered as an alternative to classic…
The article describes real Scrum problems that the Scrum Master role often encounters in their workday during the Daily Scrum meeting…
We present real-life example cases from Scrum teams and projects that can enrich your real-world knowledge of the Scrum framework, Scrum Master, Product Owner, and…
In this article, we present a comparison between Scrum and Kanban methodologies due to the increased interest in new product development models…
In Agile organizations, the role of Scrum Master is accepted as a coach not only of the Development team but also of all other positions and roles in the…
In this short report, you will find information about Waterfall and Agile concepts and their applications in business and project management…
When an organization first introduces Scrum to projects, teams may feel insecure about their work. In this article, we present sample answers to the Scrum Master role to…
Scrum Master is one of the three roles in the Scrum team. He cares for all parties and strives to preserve the order, rules, and principles of Scrum…
The article describes possible situations related to the Scrum Master role which is typical for Scrum teams…
BVOP™ Scrum Master Certification is a certification process for a Scrum Master role created by Business Value-Oriented Principles Ltd. in 2018…