[et_pb_section fb_built=”1″ fullwidth=”on” admin_label=”Hero Section” _builder_version=”4.22.0″ background_color=”#00A4E8″ background_image=”https:\/\/opinity.nl\/wp-content\/uploads\/2023\/07\/Opinity_header-2000×1400-1.webp” background_position=”bottom_right” background_blend=”luminosity” custom_padding=”|||” global_colors_info=”{}”][et_pb_fullwidth_header title=”Help, my teams want a Scrum Master! ” button_one_url=”#Ready” content_max_width=”900px” _builder_version=”4.24.2″ title_font=”Raleway|700|||||||” title_font_size=”50px” title_line_height=”1.4em” content_font=”Poppins||||||||” content_font_size=”16px” content_line_height=”1.8em” subhead_font=”Poppins|600||on|||||” subhead_letter_spacing=”4px” subhead_line_height=”1.8em” background_color=”rgba(126,190,197,0)” custom_button_one=”on” button_one_text_size=”14px” button_one_bg_color=”#00A4E8″ button_one_border_width=”12px” button_one_border_color=”#00A4E8″ button_one_letter_spacing=”2px” button_one_font=”Poppins|600||on|||||” button_one_icon=”$||divi||400″ custom_button_two=”on” button_two_text_size=”14px” button_two_text_color=”#29cb8b” button_two_bg_color=”#ffffff” button_two_border_width=”12px” button_two_border_color=”#ffffff” button_two_letter_spacing=”2px” button_two_font=”Poppins|600||on|||||” button_two_icon=”$||divi||400″ custom_padding=”100px||100px||true” title_font_size_tablet=”40px” title_font_size_phone=”30px” title_font_size_last_edited=”on|desktop” content_font_size_last_edited=”off|desktop” subhead_font_size_tablet=”40px” subhead_font_size_phone=”30px” subhead_font_size_last_edited=”off|desktop” button_one_letter_spacing_hover=”2px” button_two_letter_spacing_hover=”2px” global_colors_info=”{}” button_one_text_size__hover_enabled=”off” button_two_text_size__hover_enabled=”off” button_one_text_color__hover_enabled=”off” button_two_text_color__hover_enabled=”off” button_one_border_width__hover_enabled=”off” button_two_border_width__hover_enabled=”off” button_one_border_color__hover_enabled=”off” button_two_border_color__hover_enabled=”off” button_one_border_radius__hover_enabled=”off” button_two_border_radius__hover_enabled=”off” button_one_letter_spacing__hover_enabled=”on” button_one_letter_spacing__hover=”2px” button_two_letter_spacing__hover_enabled=”on” button_two_letter_spacing__hover=”2px” button_one_bg_color__hover_enabled=”off” button_two_bg_color__hover_enabled=”off”][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ custom_padding_last_edited=”off|desktop” admin_label=”About Section” _builder_version=”4.22.1″ background_color=”#000000″ module_alignment=”right” custom_padding=”80px||80px||true|false” custom_padding_tablet=”||120px|” global_colors_info=”{}”][et_pb_row column_structure=”1_4,3_4″ _builder_version=”4.16″ custom_margin=”||50px|” custom_padding=”60px|0px|60px|0px|true|false” border_color_all=”rgba(0,0,0,0.12)” border_width_bottom=”2px” global_colors_info=”{}”][et_pb_column type=”1_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/neom-EQ7x8WJMR4Q-unsplash-scaled.jpg” title_text=”neom-EQ7x8WJMR4Q-unsplash” _builder_version=”4.24.2″ always_center_on_mobile=”off” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”3_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text ul_type=”circle” ul_position=”inside” _builder_version=”4.27.4″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Poppins||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”|||” hover_enabled=”0″ locked=”off” global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
Okay, your teams are asking for a scrum master, but what exactly will they add to the mix? Should you hire externally or look internally? And how can you separate the wheat from the chaff? In this article, I\u2019ll walk you through the key considerations and share tips for selecting and successfully onboarding a scrum master. <\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”3_4,1_4″ _builder_version=”4.24.2″ global_colors_info=”{}”][et_pb_column type=”3_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text ul_type=”circle” _builder_version=”4.27.4″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Roboto Mono||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” header_4_font=”|700|||||||” header_4_font_size=”16px” header_4_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”||50px|” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
At first glance, the scrum master is the person who keeps meetings structured, prevents discussions from derailing, and makes sure everything wraps up on time \u2014 all while armed with post-its and whiteboard markers. <\/p>\n
A scrum master isn\u2019t just there to facilitate meetings\u2014they\u2019re the quiet force keeping the engine running, helping the team stay on track and avoid hazards. Since they\u2019re embedded in the team without being functionally or technically involved, they can offer a fresh, unbiased view and hold up the mirror when needed. <\/p>\n
The scrum master is the team\u2019s moral compass and the one who keeps an eye on the finish line\u2014especially when things get hectic. They stay close to the team, help build trust and connection, and shield them from outside interference. <\/p>\n
Because course correction often happens subtly, it can be hard to notice. Team conflicts are addressed before they escalate, and when the product owner starts to lose control, the scrum master steps in with support and guidance. The more senior the scrum master, the earlier they can intervene in the delivery process. A junior typically supports one team and their product owner. A mid-level scrum master can guide multiple teams and facilitate collaboration between them. A senior also engages with management and the wider business. <\/p>\n
What does success look like for a scrum master? It\u2019s when people work together effortlessly, teams become more open and reliable, product owners stay focused on value, and hardly anything needs to be escalated.[\/et_pb_text][et_pb_text ul_type=”circle” _builder_version=”4.27.4″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Roboto Mono||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” header_4_font=”|700|||||||” header_4_font_size=”16px” header_4_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”||50px|” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
A good scrum master, in my view, focuses on implementing a practical, no-nonsense version of Scrum. That means clearly assigning ownership and doing everything possible to keep the team motivated and productive so they can deliver maximum value. In more traditional organizations, this can clash with the status quo\u2014especially where frameworks like ITIL or PRINCE2 dominate.[\/et_pb_text][et_pb_blurb title=”Difference classical and agile organizations” use_icon=”on” font_icon=”||fa||400″ icon_color=”#00A4E8″ icon_placement=”left” _builder_version=”4.27.4″ _module_preset=”default” header_text_color=”#FFFFFF” hover_enabled=”0″ border_radii_image=”on|1px|1px|1px|1px” global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
In traditional organizations, a \u201ccommand and control\u201d approach is common\u2014information flows from the floor to management, where decisions are made. In scrum, it’s the other way around: decision-making authority lies with the people who have the information. <\/p>\n
Take releasing software into production, for example. In a traditional organization, there’s a Change Advisory Board (CAB). Teams provide input on what they want to release, and the CAB decides if and when it will go live. <\/p>\n
In scrum, it\u2019s the team that makes the decision and takes responsibility for it. Because they are accountable, they also implement risk mitigation measures\u2014both technical and procedural\u2014manage communication, and handle any necessary on-call support. <\/p>\n
[\/et_pb_blurb][et_pb_text ul_type=”circle” _builder_version=”4.27.4″ text_font=”Poppins||||||||” text_font_size=”16px” text_line_height=”2em” ul_font=”Poppins||||||||” ul_line_height=”2em” header_font=”||||||||” header_3_font=”Raleway|700|||||||” header_3_font_size=”24px” header_3_line_height=”1.4em” header_4_font=”|700|||||||” header_4_font_size=”16px” header_4_line_height=”1.4em” background_layout=”dark” max_width=”750px” custom_margin=”||50px|” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
In certain situations, hiring an external scrum master may be more effective. As an outsider, they\u2019re less sensitive to internal politics or personal career concerns. In other words, an external scrum master can guide bold changes with greater independence. <\/p>\n
An internal scrum master, on the other hand, knows the organization well and is often better equipped to help teams navigate challenges rooted in the broader company structure.<\/p>\n
If a scrum master aims to drive meaningful improvement but keeps hitting a glass ceiling, it can seriously impact their motivation. In such cases, hiring an external scrum master may be the more effective choice. <\/p>\n
[\/et_pb_text][\/et_pb_column][et_pb_column type=”1_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_team_member name=”Wijnand Kroes” position=”Scrum Master \/ Agile Coach” image_url=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/Wijnand-Profielfoto.png” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_team_member][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_3,2_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”1_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/opinity.nl\/wp-content\/uploads\/2024\/03\/nick-morrison-FHnnjk1Yj7Y-unsplash-scaled.jpg” title_text=”nick-morrison-FHnnjk1Yj7Y-unsplash” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”2_3″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” text_text_color=”#FFFFFF” header_2_text_color=”#FFFFFF” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
In many job listings and project descriptions, I often see knock-out criteria like PSM I, PSM II, or SAFe certifications. While most scrum masters have a PSM I, those with many years of experience haven\u2019t always taken the time to pursue additional certifications. As a result, these strict requirements may unintentionally exclude highly experienced professionals. When I need to hire a fellow scrum master, this is how I assess their CV: <\/p>\n
What I don\u2019t take into account is the sector or the technology a candidate has worked with. However, I do consider the scale of the organization. A scrum master who has spent years working with development teams at large banks will likely perform well in a manufacturing company with very different teams. But a scrum master who has only worked at small companies may struggle in a large, slower-moving organization. <\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” text_text_color=”#FFFFFF” header_2_text_color=”#FFFFFF” header_3_text_color=”#FFFFFF” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
With the growing supply and demand for scrum masters, many teams and organizations can no longer see the wood for the trees. Their impact isn\u2019t always visible, especially to management. Hopefully, this blog post gave you more clarity and some pointers. Would you like tailored advice for your organization and teams? Feel free to contact Opinity \u2014 we\u2019re happy to help you find the best fit for your situation.[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
Okay, your teams are asking for a scrum master, but what exactly will they add to the mix? Should you hire externally or look internally? And how can you separate the wheat from the chaff? In this article, I\u2019ll walk you through the key considerations and share tips for selecting and successfully onboarding a scrum […]<\/p>\n","protected":false},"author":9,"featured_media":1031,"parent":1171,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"class_list":["post-1205","page","type-page","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\n