{"id":3978,"date":"2021-02-09T13:01:19","date_gmt":"2021-02-09T12:01:19","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=3978"},"modified":"2026-02-02T12:12:31","modified_gmt":"2026-02-02T11:12:31","slug":"scrum-master","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/scrum-master\/","title":{"rendered":"The Scrum Master is responsible for processes, infrastructure, organizational development, people and culture"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\">The Scrum Master is responsible for promoting and supporting Scrum &amp; P4 in accordance with the P4 rules. Scrum Masters do this by helping everyone involved to understand Scrum\/P4 theory, practices, <a href=\"http:\/\/p4dev.hardscrum.com\/p4-principles\/\">principles and values<\/a>.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h3><span style=\"vertical-align: inherit;\">General description<\/span><\/h3>\n<p><em><span style=\"vertical-align: inherit;\">This chapter describes the role of the Scrum Master in general, ie for all levels in the P4 framework. We therefore also use the general terms &#8220;Team&#8221;, &#8220;Product Owner&#8221; and &#8220;Product Backlog&#8221;. The description is based very deliberately on the Scrum description.<\/span><\/em><\/p>\n<p><span style=\"vertical-align: inherit;\">The Scrum Master is a \u201cServant Manager\u201d for the team. The Scrum Master helps those who are not part of the team to understand which of their interactions with the team are helpful and which are not. The Scrum Master helps optimize collaboration so that the value generated by the team is maximized.<\/span><\/p>\n<h4><span style=\"vertical-align: inherit;\">The service of the Scrum Master for the Product Owner<\/span><\/h4>\n<p><span style=\"vertical-align: inherit;\">The Scrum Master serves the Product Owner in various ways, including:<\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\">Ensure that the goals, scope and product domain are understood as well as possible by everyone in the team;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Providing techniques for effective Backlog management;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Provide an understanding of the need for clear, concise backlog entries in the team;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Understand product planning in an empirical work environment;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Ensure that the product owner knows how to arrange the backlog so that it generates the greatest value;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Conveying the correct understanding of agility and its application;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Support in the implementation of Scrum events if required or on request.<\/span><\/li>\n<\/ul>\n<h4><span style=\"vertical-align: inherit;\">The service of the Scrum Masters for the Working Team<\/span><\/h4>\n<p><span style=\"vertical-align: inherit;\">The Scrum Master serves the Working Team in various ways, including:<\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\">Coaching the Working Team towards self-organization and cross-functional teamwork;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Support the Working Team in creating high quality products;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Removing obstacles that stop the Working Team;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Support in the implementation of Scrum events if required or on request;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Coaching the Working Team in organizations where Scrum is not yet fully accepted and understood.<\/span><\/li>\n<\/ul>\n<h4><span style=\"vertical-align: inherit;\">The service of the Scrum Master for the entire Organization<\/span><\/h4>\n<p><span style=\"vertical-align: inherit;\">The Scrum Master serves the organization in various ways, including:<\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\">Leading and coaching the Organization in the introduction of Scrum and P4;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Planning P4 implementations within the Organization;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Supporting colleagues and Stakeholders to understand and implement Scrum and empirical product development;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Trigger changes to increase team productivity;<\/span><\/li>\n<li><span style=\"vertical-align: inherit;\">Collaborate with other Scrum Masters to improve the effectiveness of the organization.<\/span><\/li>\n<\/ul>\n<p><em><span style=\"vertical-align: inherit;\">&#8211; end of general part &#8211;<\/span><\/em><\/p>\n<p>The role of the Scrum Master is implemented in the P4 framework on all levels.<\/p>\n<h3><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\"><span style=\"vertical-align: inherit;\">Team Scrum Master (TSM)<\/span><\/a><\/h3>\n<p><span style=\"vertical-align: inherit;\">The Team Scrum Master (TSM) ensures that the members of the Working Team can work optimally. He ensures an optimal workflow between the team members by solving disabilities and problems that arise in the cooperation of the teams, especially those that cannot be solved by the self-organized Working Team. To this end, he organizes and moderates the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\"><span style=\"vertical-align: inherit;\">Team Retrospective<\/span><\/a><span style=\"vertical-align: inherit;\"> , in which the team members exchange ideas for the best possible working conditions and workflow within the team. He works with other TSMs within the Cluster in the <a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\">Team Scrum Master Group<\/a> to prevent local optimization within the Team.<\/span><\/p>\n<h3><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master (CSM)<\/span><\/a><\/h3>\n<p><span style=\"vertical-align: inherit;\">The Cluster Scrum Master (CSM) ensures that the teams in its <a href=\"http:\/\/p4dev.hardscrum.com\/rclusterlevel\/\">Cluster<\/a> can work optimally. Together with the TSMs, he ensures an optimal workflow between the Teams, by solving disabilities and problems that arise in the teamwork. To this end, he organizes and moderates the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\"><span style=\"vertical-align: inherit;\">Cluster Retrospective<\/span><\/a><span style=\"vertical-align: inherit;\"> and heads the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\"><span style=\"vertical-align: inherit;\">Team Scrum Master Group<\/span><\/a><span style=\"vertical-align: inherit;\">, in which the TSMs exchange ideas in order to optimize the working conditions and work flow within the Cluster. He works with other CSMs within the Organization in the <a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\">Cluster Scrum Master Group<\/a> to prevent local optimizations within the Cluster.<\/span><\/p>\n<h3><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\"><span style=\"vertical-align: inherit;\">Organizational Scrum Master (OSM)<\/span><\/a><\/h3>\n<p><span style=\"vertical-align: inherit;\">The Organizational Scrum Master (OSM) ensures that the Clusters in its <a href=\"http:\/\/p4dev.hardscrum.com\/rportfoliolevel\/\">Organization<\/a> can work optimally. Together with the CSMs, he ensures an optimal workflow between the Clusters by solving disabilities and problems that arise in the collaboration of the Clusters and Teams. To do this, he organizes and moderates the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\"><span style=\"vertical-align: inherit;\">Organization Retrospective<\/span><\/a><span style=\"vertical-align: inherit;\"> and heads the <\/span><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\"><span style=\"vertical-align: inherit;\">Cluster Scrum Master Group<\/span><\/a><span style=\"vertical-align: inherit;\"> , in which the CSMs exchange ideas for a global optimum of working conditions and workflow within the organization.<\/span><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr style=\"background-color: #f8f8f8;\">\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr style=\"background-color: #ffffff;\">\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Team Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/retrospective\/\">Team Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-sync\/\">Cluster Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\">Cluster Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisation-sync\/\">Organisation Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\">Organisation Retrospective<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\">Team Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\">Organisation Scrum Master<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\">Team Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\">Cluster Management Circle<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p style=\"text-align: left;\"><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\">Cluster Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\">Organisation Management Circle<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Team DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/improvementbacklog\/\">Team Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\">Cluster DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\">Cluster Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\">Organisation DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioimprovementbacklog\/\">Organisation Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"The Scrum Master is responsible for promoting and supporting Scrum &amp; P4 in accordance with the P4 rules. Scrum Masters do this by helping everyone involved to understand Scrum\/P4 theory, practices, principles and values. &nbsp; General description This chapter describes the role of the Scrum Master in general, ie for all levels in the P4&hellip;","protected":false},"author":3,"featured_media":359,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[34,24],"tags":[416,417],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3978"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=3978"}],"version-history":[{"count":12,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3978\/revisions"}],"predecessor-version":[{"id":3981,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/3978\/revisions\/3981"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/359"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=3978"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=3978"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=3978"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}