[et_pb_section fb_built=”1″ _builder_version=”4.4.1″ background_color=”#fbfcfd” global_module=”1099″][et_pb_row column_structure=”1_2,1_2″ disabled_on=”on|on|off” _builder_version=”4.5.6″][et_pb_column type=”1_2″ _builder_version=”4.4.1″][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” _builder_version=”4.4.1″ custom_margin=”-5%|||25%|false|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;”][\/et_pb_image][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.5.6″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” custom_margin=”-3%|||-60%|false|false”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.5.6″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” custom_margin=”-5%|||-60%|false|false”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row disabled_on=”off|off|on” _builder_version=”4.4.1″][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” align=”center” _builder_version=”4.4.1″ custom_margin=”||||true|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;”][\/et_pb_image][et_pb_text _builder_version=”4.4.1″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” text_orientation=”center” custom_margin=”-3%||||false|false”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.4.1″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” text_orientation=”center” custom_margin=”-3%||||false|false”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.4.1″][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_post_title author=”off” comments=”off” featured_image=”off” _builder_version=”4.4.1″ title_font=”Source Sans Pro|700|||||||” title_text_align=”center” title_text_color=”rgba(0,0,0,0.8)” title_font_size=”47px” text_orientation=”center” title_font_size_tablet=”40px” title_font_size_phone=”35px” title_font_size_last_edited=”on|desktop”][\/et_pb_post_title][et_pb_text _builder_version=”4.7.4″ _module_preset=”default” text_font=”Source Sans Pro||||||||” text_font_size=”15px” text_line_height=”1em” text_orientation=”right” custom_margin=”|||10%|false|false”]
Photo by manfredsteger<\/a><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.4.1″][et_pb_row _builder_version=”4.8.1″ width=”90%”][et_pb_column type=”4_4″ _builder_version=”4.4.1″][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″]<\/p>\n How can you tell if the Scrum Master<\/a> of a development team is doing his job well? I’ve heard various exciting answers such as “Well, the team members are happy with him” and “He spends little time in meetings and is therefore efficient”, etc. The work of a Scrum Master cannot be judged simply on the basis of a few numerical results, but I will give you 5 main success criteria to follow. <\/span><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ quote_font_size_tablet=”” quote_font_size_phone=”” quote_font_size_last_edited=”on|phone”]<\/p>\n Many teams start their agile journey by coming from a command-and-control<\/em> environment where they were always told exactly what to do and how to do things. The first task of a Scrum Master is to change the behavior patterns and mindset<\/a> of team members so that the team is independent in its daily work and operates autonomously. An agile team must cover all the roles needed to make day-to-day development decisions and solve problems. The team must have a product owner, designer, analyst\/architect and other necessary technical expertise so that the team can function as a unified team (T-shaped team<\/em>). <\/p>\n An agile team is not managed from outside the team in its day-to-day work. A well-functioning team knows its goal and roadmap<\/em>, users’ wishes and feedback at all times, and the team also has the necessary skills and the right to make current decisions themselves. <\/p>\n If the Scrum Master has been able to create a self-functioning team that makes its daily decisions on its own, then the first and most important goal of his or her work has been achieved.<\/strong><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2021\/05\/Let-the-team-decide.jpeg” alt=”Let the team decide” title_text=”Let the team decide” show_in_lightbox=”on” align=”center” _builder_version=”4.9.4″ _module_preset=”default”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.9.4″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false”]<\/p>\n Photo by KeithJJ,<\/a> author<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″]<\/p>\n One of the main characteristics of an agile team is consistent learning and experimentation. And it is important to learn together and with a team, individual learning is part of everyday work these days anyway. If a team does not have the opportunity to regularly evaluate itself as a unified team and realize the potential for development, the result is a status quo<\/em> and a team that stands still in development. <\/p>\n The task of the Scrum Master is to conduct regular retrospective meetings<\/em>, where the team discusses how they can be better at their work, what are the current problem areas, what new approaches and practices should be tested. At the end of the meeting, it is agreed what will be the focus of the next sprint in order to improve the work process, and at the next meeting, they look back and assess how it went. A team that is constantly learning, experimenting and developing is a direct result of the successful work of the Scrum Master.<\/strong><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2021\/04\/RetroSailboatBoard-byAgileCoach-1.png” alt=”ZenHub Board” title_text=”RetroSailboatBoard-byAgileCoach” show_in_lightbox=”on” _builder_version=”4.9.4″ _module_preset=”default”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.9.4″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false”]<\/p>\n Sailboat Retrospective Board. Photo by Author<\/a> <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″]<\/p>\n We all need goals to move towards. The goals must also be suitable and meaningful for us on a personal level. Each team member must have a full understanding of where and why they are moving together. <\/p>\n The Scrum Master’s task is to contribute to goal-setting in every way. Their job is to implement an agile mindset that has a clear focus on value creation. Unfortunately, there is still a lot of “Feature Factory<\/em><\/a>” style development in software development, where the focus is on creating as many features as possible (and collecting story points<\/em>), while forgetting to check what the end users really want. <\/p>\n If the team knows and keeps in mind the goals based on the interests of the end users, the Scrum Master’s job in this paragraph is well done.<\/strong><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2021\/05\/Feature-Factory.jpeg” alt=”Feature Factory” title_text=”Feature Factory” show_in_lightbox=”on” align=”center” _builder_version=”4.9.4″ _module_preset=”default”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.9.4″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false”]<\/p>\n Photo by eprins67<\/a><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″]<\/p>\n A tidy Product Backlog means a list of tasks from which the members of the development team can pick the next job at any time, the business needs of which are thoroughly described. This means that the backlog must be prioritized by the Product Owner, the work at the top of it has been discussed, approved and is fully prepared for work. Unnecessary and outdated work has been removed from the backlog by the Product Owner, because an active Product Backlog must not be a garbage dump for years. <\/p>\n Although the lion’s share of Product Backlog management is done by the Product Owner, it is the task of the whole team, not just the Product Owner, to constantly update and maintain it. The Scrum Master’s task is to support the product owner and make working with the Backlog a natural part of each team member’s daily work. <\/p>\n A well-maintained Product Backlog and enabling a smooth development flow for the team are one of the hallmarks of a Scrum Master’s job well done.<\/strong><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2021\/05\/Niidirullid-rivis.jpeg” alt=”Thread spools in a row” title_text=”Thread spools in a row” show_in_lightbox=”on” align=”center” _builder_version=”4.9.4″ _module_preset=”default”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.9.4″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false”]<\/p>\n Photo by PublicDomainPictures<\/a><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.9.4″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″]<\/p>\n Striving for a consistently more efficient development process and keeping attention to the quality of development is also part of the work of a Scrum Master. The basis for high software product quality is both purposeful value creation and minimal technical debt. <\/p>\n The right development methodology is also important. At the beginning of the agile journey, the Scrum Master must help the team choose a methodology based on the goals and the content of the project. Scrum is not suitable for everyone, and there are many different agile methods<\/a>. Perhaps there is no need to use an empirical process at all in this project? Stacey Matrix<\/a> and Cynefin Matrix<\/a> help make this decision. <\/p>\n One of the characteristics of a Scrum Master’s good work is the team’s efficient development process and the creation of a high-quality product. <\/strong><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2021\/05\/Stacey-Matrix.png” alt=”Stacey Matrix” title_text=”Stacey Matrix” show_in_lightbox=”on” align=”center” _builder_version=”4.9.4″ _module_preset=”default”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.9.4″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false”]<\/p>\nSelf-acting team<\/h2>\n
\n
Continuous learning and development<\/h2>\n
Continuous development from the perspective of both the team and the individual gives team members a powerful motivational injection, not to mention becoming more efficient. <\/p>\n\n
The right goals<\/h2>\n
\n
Tidy Product Backlog<\/h2>\n
\n
High product quality<\/h2>\n
\n