Why do you want to be a Scrum Master?

Historically, the profession of “scrum master” is undoubtedly new and modern.

Each new field is somewhat incompletely explored and subject to development. Тhere are cases when some people may never understand it because it is not a methodology, there is no ready-made recipe for success.

This makes this profession extremely dependent on the individual qualities, skills, and motivation of the individual. It turns out that then there should not be two identical “scrum masters” simply because there is no such written way or „methodology. This makes things interesting!

The first time I heard the term “Scrum” and tried to google and youtube what it means, I got enough to pique my interest and not enough to satisfy it completely or give a clear and complete picture.

For the above, this seems like a job that requires “creativity.” As you point out, the framework “allows for unique and autonomous thinking”.

I am not among the people who feel completely happy in their comfort zone and once they learn everything in one profession they would stay there for the rest of their lives.

Just when I no longer have anything to provoke myself with and everything is completely predictable, it’s time to leave. Ie besides being creative, this work also turns out to be quite provocative. In this aspect, “scrum” completely wins me over.

The “scrum master” position also seems communicative to me. This is a complete advantage for me. I love teamwork, I find it especially inspiring, productive, and invigorating. Reference: “Kanban vs Scrum product development with Lean”,

I’m not one of those people who would choose to work all day at a desk alone.

What do you expect to be a Scrum Master?

I expect to be someone who is a kind of coach, instructor (“coach”) on all matters relating to the framework for the company in which I work.

This means that I must best understand all the principles and peculiarities so that I can explain them to strangers and convince them of the need to use them, of their usefulness. I like this feature, I would be happy for it to be part of my duties.

A Certified Scrum Master

I want to be a certified Scrum Master. I need my certificate to gain my self-esteem.

I expect to be a kind of facilitator, with my work to promote better communication, to clarify the commonalities of all participants, to resolve conflicts, to keep the focus on the subject of the specific task. I also really like this feature during meetings, but not only that. Read more: “Best Scrum Master certification online in 2022”,

I expect to feel provoked to adapt to companies in different fields, providing radically different services/products. Ie there is no way the work can be monotonous or boring, to put it bluntly. On the contrary, I expect it to be always challenging and different.

What are the things that worry you the most at this stage?

At this point, I have a vague idea of ​​what a “scrum” is. Probably because of this I am very curious how I will deal with the practical aspects of implementing the framework.

Usually, it is only the “work” itself that gives a clear idea of ​​the profession and could even radically change the initial views and impressions of it. I can’t wait to see what ‘scrum’ looks like in practice, congratulations on the idea of ​​’situational training’.

Again, due to the lack of clarity about the functions of the “scrum master”, I have some concerns about whether this position is not too „administrative.

Its essence, I hope, does not only include making excel spreadsheets, tracking deadlines, writing technical emails, and similar (more organizational type) obligations. I imagine her creative and I hope I’m not wrong.

Since my education is humanitarian, not technical, I am hesitant to develop good skills as a “scrum master” without any technical training. I am encouraged by the fact that my acquaintances (programmers) have shared that “scrum masters” are often not programmers at all (or even … people with completely different training – economic for example).

However, it is difficult for me to explain how to get into work and make adequate decisions if you do not have good technical knowledge (especially if you want to be a “product owner”, for example).

The idea of ​​practicing the profession of “scrum master” at this stage is intriguing to me.

However, I am hesitant about the possibilities for finding a job and in what terms. Most of the ads I’ve seen want a popular certificate (from the ones you mention that they only give “various unnecessary terms and a bunch of words you won’t be able to apply in your work”) AND / OR experience in the field…

I experience how could I certify if everyone sets it as a precondition for starting work. It seems a bit contradictory.

In your opinion, is it necessary to obtain such a certificate at any cost, although useless, just to find a job (provided that I have no experience in the field)?

What problems do you think you will have in your work?

I guess there is a chance that I will run into an old-school waterfall supporter in a company who would make the application of the scrum extremely challenging, to put it mildly.

Given the new, revolutionary, unique nature of the framework, I expect that I may need to convince some more skeptical and unacceptable people of its usefulness.

If they have many years of experience in this field, I am prepared that I will probably have to make a “revolution”, but in a foreign field … which does not seem like an easy task.

In addition to what was said in the answer to question 3 (about the lack of technical training), I also find it difficult to adapt one, albeit a good “scrum master”, to the specific product/service that the company offers.

I hope that there is always a period of familiarity with the terms and the product. In other words, when a non-programmer listens to a conversation between programmers, it feels as if they are talking in another language.

Extremely terminological. I guess, depending on the product, this adaptation is not easy every time. I guess it’s not the job of the “scrum master” to solve issues in concreteness and depth, but it’s still good to understand at least what the programmers are talking about.