The Scrum Guide is a small book. The BVOP Agile Guide is larger. But if you memorize both books, this does not guarantee a successful Scrum Master certification exam.
Preparation for Scrum Master (BVOSM, PSMI, PSMII, CSM) certification exam: example questions and answers
Scrum Master is the man between the Development Team and the Product Owner. The reason for having such a buffer role is very simple.
As you know, the development team is responsible for making the product and that is its main goal. Product Owner, on the other hand, must set clear and precise conditions for the team to make this product, which it has learned from its interactions with stakeholders.
He is also in constant communication with stakeholders to keep up with their requirements, changing decisions and ideas. As you can see, the two countries (Scrum Development Team and Product Owner) are quite different positions that do not have much in common, except for the idea that is being developed. Reference: "Preparation for the Scrum Master certification exam (BVOSM, CSM, PSM)", https://mstsnl.net/preparation-for-the-scrum-master-certification-exam-bvosm-csm-psm/
The sponsor is a very busy person who does not have time to spend constant time with the teams and discuss their progress.
And in most cases, the development team consists of highly specialized professionals who are focused mainly on their part and have no understanding of other factors influencing the process as a whole. → It is here that the Scrum Master intervenes - the bond between these two worlds.
He has the necessary soft skills to make the team understand the essence of the product, to understand the practices of Scrum, to use them for the benefit of all, and at the same time is in direct contact with the Product Owner - discussing more in-depth than purely technical formalities of product stuff, and scrupulous principles. Reference: “Quick and easy preparation for the Scrum Master certification exam“, https://www.businesspad.org/quick-and-easy-preparation-for-the-scrum-master-certification-exam/
I intentionally started it from afar so that the analogy could be made. Because in most cases, when we simply say: the scrum master makes sure that the team understands and implements the scrum methods, removing obstacles between teams, establishing a solid human relationship, and at the same time the team's connection with the product owner may sound confusing.
You may be wondering if it would be needed in an environment that has followed some principles since the world began - namely the banking system - but, as you can see, the world has changed a lot and continues to do so more and more diligently.
What does this show us? The world is changing (it has always done so, but only now with globalization at a very fast and visible pace) and if people, organizations, companies, countries, and institutions do not adapt to these changes, they will sooner or later disappear. I'm not saying that - Darwin discovered it many years ago and called it Evolution.
So, sitting on some old laurels and denying what is new and real is not going to help. On the contrary, we need to accept it, realize it, and see where we are in the process and what we can change to be successful in the future.
Agile teaches us exactly that - it gives us the foundations of an abstract and open to innovative thinking that is flexible and adaptable to change.
And for this process (transition) to be painless, unobtrusive, natural and at a much lower cost - companies need Scrum Master - the person who will try to make employees understand the above. Reference: “Preparation for the Scrum Master certification exam (PSM, CSM, BVOSM) with sample questions“, https://www.libraryofmu.org/preparation-for-scrum-master-certification-exam/
The Development Team and Scrum events
The Development Team shares your idea that they want to nominate you for a Product Owner appointment and take over its functions, and for the Product Owner assigned to your team to go to another team and have no contact with it.
First of all, there is no way they can make that decision. Unless he has had some serious conflict, dispute, or massive problem, reflected even by the management, which is even familiar to HR, and has escalated to a large level, the team can not just make such a decision.
If this idea is actively discussed and there are real examples and evidence of why this change should happen - then it is discussed with the ENTIRE Scrum team (including the Product Owner and Scrum Master). (More Scrum framework articles…)
If there is agreement from all sides and the Scrum Master has the specific knowledge and experience in the field of the owner and feels confident in the position - then it can happen.
But again, a rather "IF-situation". If there is a problem (personal) with him, then talking and sharing leads to consensus.
In 2 days you have a meeting to present the current progress of the product. Your Product Owner role and most of the Development team are on leave for another 5 days.
The meeting will be canceled when the whole team is together. Of course, this does not mean that meetings cannot be held (or in this case the product presentation) if one person is missing, but it is not generally the task of the scrum master to present product details and progress.
That is why there is a product owner and in general a team of specialists who have created this product and can adequately and specialized answer questions from the other side. Reference: “Certified Scrum Master exam preparation: CSM, PSM, BVOSM sample questions“, https://scrumtime.org/certified-scrum-master-exam-preparation-questions/
You notice that the team spends more and more time in the games and entertainment hall in your office.
Quite a common situation, which is not only found in this type of team - but in general.
If the people in the teams have done their job, done what is required of them, and are currently waiting for a phase or approval, and therefore come to such games and entertainment - there is nothing wrong. On the contrary, they get closer to each other, establish relationships and build trust, which leads to their good knowledge of each other and will help the team in the future.
However, if there is work and tasks to the ears and instead of productivity, time is wasted on the side and non-work related things, this is already a problem that must be addressed and clarified at all costs. (in most cases it is the first option, but there are exceptions). However, he has a goal and some optimal work-life balance and does not want people to feel like robots working on a production line, waiting for the "bell to ring" and get out of this hell called work.
Stakeholders and Scrum
Business stakeholders share the view that the product is not progressing as expected.
This is something that should be discussed with the product owner. He needs to rethink their priorities, expectations, and main ideas. To restructure the product backlog and if you need to clarify with them, what exactly has changed or they do not like. Reference: “Preparation for CMS and PSM Certified Scrum Master exam with sample questions“, https://phron.org/preparation-for-cms-and-psm-certified-scrum-master-exam-with-sample-questions/
This is not the task of the scrum master. He just needs to inform and explain the situation (again with the principles of scrum) to the team - namely that these things are normal and do not mean that they have not done their job - just the requirements change, ideas change, priorities too - so we must be ready for change.
Product Owner role
The Product Owner role in your team goes on a business trip for 2 months to one of your customer support centers. No one has made any plans, no comments. The client has not shared anything more, the Development team does not know what it will work on and your colleagues are worried about the future of the project.
An immediate connection with the owner is sought. Communication, communication, sharing, transparency. (Club of the 7 master's universities)
These are the basics of Scrum. There is nothing right or wrong. If everything is discussed and there are no hidden things, there are no problems. He can go abroad for half a year, if we have previously agreed, clarified, and discussed options and ways of working.
Secrecy and hidden things are not part of the scrum - they do not help, but harm. Therefore, seeing such a situation - we immediately contact the person and discuss what is happening.
One of the programmers in the team asks the designer for regular adjustments to the visual concepts he offers.
If the designer makes basic and constant mistakes regularly, then you need to see what the reason is - lack of skills, knowledge, distraction, some personal breakdown, or similar things. They are addressed and discussed with him and it is understood why this is so. Reference: “Certified Scrum Master exam preparation with sample questions“, https://customessaysonline.net/certified-scrum-master-exam-preparation-with-sample-questions/
There is some personal enmity between them and corresponding nagging. Such things are also part of the duties of the scrum master - he must take care that the team is in good and healthy relations with each other, that there are no quarrels, quarrels, and negativities. Problems are smoothed out. If nothing helps - HR intervenes (in principle it does not get there, but there are always exceptions).
The QA specialists on your product testing team plan to integrate additional technologies, tools, and testing procedures. This will slow down the Product Owner role and reduce post-sprint progress.
This is something they need to discuss with each other. The scrum wizard is not interested in the technical details and how to do things - he does not command which software and which program to use. Professionals decide for themselves. Reference: “Preparation for Scrum Master certification exam on Sprint event“, https://medfd.org/preparation-for-scrum-master-certification-exam-on-sprint-event/
On the other hand, the owner is supposed to have some knowledge in the field and has decided that he will not contribute as much as he will slow down and share his opinion. However, if it is an Owner product that does not have a large technical background, it is good to talk to the developers and they will explain to them with examples and facts what is an advantage and what is a disadvantage.
Designers and programmers
The designer and the programmer have decided to exchange part of their work on their initiative. The designer will take on some of the easy programming tasks, and the programmer will make parts of the interface.
As long as it doesn’t hurt the process - it’s fine. As we have already said, the master does not interfere in the work of his colleagues. Reference: “Preparation for Scrum Master certification and tips for Scrum professionals”, https://www.kievpress.info/preparation-for-scrum-master-certification/
They are experts in their field, they know best what works and what doesn't. Like him, no one bothers to tell him how to hold rallies. It is important to discuss this decision and at least share it with the team so that everyone is aware in the future that obviously, both colleagues know other areas. If the results are positive - everything is correct. If there is a decline in success - it is right to return as it was.
QA specialists want you to assign them good testing tools for the next sprints, as you will already be developing new components that require a different type of test.
It is not my job to assign them tools and tools. They know best what works and what doesn't. The scrum master consults the product owner about the situation and, if necessary, discusses the specific reason with technicians who are familiar with it. The scrum master does not fulfill these wishes - he shares the concerns and thoughts of the team with the Product Owner and from there decides what to do. Read more: “Preparation with sample questions for Scrum Master certification exam CSM & PSMI”, https://wikipedia-lab.org/preparation-sample-questions-scrummaster-certification-exam/
The development team wants to replace the main software part of your product. We currently use the paid Enterprise popular environment. The license is paid by your customer, who does not think that the cost is a problem.
Again, a situation in which the opinion of the product owner should be consulted - as he is responsible and aware of budgets, funds, details, and more. If there is no problem on the part of the client and the cost is not a problem - there should be no obstacles. But this is not something that the master can approve or reject.
The Product Owner role wants the designer to increase communication with the product testing team.
The Scrum Master appears in this case as a mediator of this message. He must submit this request to the designer in a businesslike manner with an approach and understanding. Even in some cases, if it is a very delicate and technical reason why there is such an explicit request, it is possible to arrange a short meeting so that the owner can explain the real reasons directly to the designer. In most cases, however, this is not necessary. Reference: “Free preparation for the Scrum Master certification exam (CSM, PSMI, PSMII, BVOP)”, https://brightonbot.com/preparation-scrum-master-certification-exam/
The client and software tests
Your client is not happy with the tests and wants to urgently increase the number of QA specialists in your team, with an additional 6 people as soon as possible. He wants three more senior programmers to join the team by the end of the week. The project budget has been increased accordingly.
These things are coordinated with the product owner. It is assumed that he is familiar with the scrum principles and that he knows that the team should not (optimally) exceed 9 people.
If it is a really big project and a serious client, where there is no way to deliver it with the current resources, then the idea of a second team is being discussed. But no radical changes are being made to the scrum organization. Reference: Original Website publication
An entire system cannot be changed because of one example or case. The system works and is successful when its basic rules are followed.
One such rule is the size of the team. With a large team of more than 10 people, transparency and a sense of unity are lost. Therefore, it is better to make 2 teams (even if the scrum master is responsible for the 2nd), but not to expand one.
Your director wants you to move temporarily, for about a month, to another team. He has discussed moving your role with the Product Owner, who will take over the Scrum Master function in a month, as he said he has time for that.
In general, this is not a problem, but it is important that the master first of all has reached a level where he has established a stable relationship with the team and has some already established workflow. Read more: “Free training to prepare for the Scrum Master Certification exam”, https://www.islandjournal.net/scrum-master-certification-exam/
Then a temporary change or taking on another team is not a problem (unless, of course, the scrum master does not share that he does not feel mentally and physically ready for such a change).
There are cases where the scrum master simply can not be divided into several places at once and can be successful with only 1 team.
There are also people (Scrum Masters) who do not have a problem with such things and are multifunctional. Here we are talking about the personal reasons, characters, and qualities of the individual. Read more: “Best Scrum Master Certifications for 2022 and 2023“, https://eduwiki.me/best-scrum-master-certifications-for-2021-and-2022/
However, if the team has just started to get used to their current scrum master and they have just grasped the idea of Scrum, it would not be good to change the rhythm of work at this very moment. → depends on the situation. Reference: “Preparation for the certification exam for CSM and PSM I (BVOSM) Scrum Master”, https://www.mu7club.com/preparation-for-certification-exam-scrum-master/
Why become a Certified Scrum Master?
Maybe I should clarify what is the reason for enrolling in a course and getting a certificate. Of course, I have a desire to become a good Scrum Master and at some stage start implementing new products from the very beginning of the idea for such.
At this stage, however, I already work for a company in the field of electronic services. The product we offer has reached its growth stage. In two words - the foundations are laid, we have a considerable market share and from now on, all that remains is to improve and launch new functionalities that will facilitate the work of our customers.
In general, my most positive qualities are upbringing, organizational and communication skills, and determination. I also know the basics of marketing (I am well aware that marketing and product management are separate things), which will also be useful to me. I also learned to prioritize tasks - which are urgent, important, medium, or low priority.
This way, the whole team knows where to focus their efforts. Often, when I have a task set, I cannot sleep until I am sure that I have completed it to the best of my ability. In particular, the biggest plus in the particular company is that I know the product very well and can almost always offer users a solution to a given problem. I have always had good, even excellent relations, both with colleagues and management, as well as with clients, regardless of the field of work.
What will prevent me from being an adequate Certified Scrum Master?
As negative qualities, I would point out that it is very difficult for me to say "No" and that I tend to compromise. As I already mentioned in a previous assignment, I hold the position of Technical Support Expert.
When I communicate with a client who wants something that is not legally justified or desired only by him, I used always agree. Now I have learned to argue, offer possible options and refuse. It is still quite difficult for me, but I am working hard in this direction. When I correct this shortcoming of mine, I will become an excellent Certified Scrum Master.
Another disadvantage of mine, specifically in the field of electronic services, is that I have no idea about programming, and how much time it takes to program something.
Here, of course, comes the communication with my colleagues, as based on their feedback, I will be able to estimate how much time and what resources will be needed to develop a new or improve an old functionality.
- Previous article Strong managers know the value of difficult conversations