{"id":408,"date":"2019-06-13T21:51:21","date_gmt":"2019-06-13T19:51:21","guid":{"rendered":"http:\/\/blog.hardscrum.com\/?p=408"},"modified":"2021-10-30T14:46:45","modified_gmt":"2021-10-30T12:46:45","slug":"the-fundamental-misunderstanding-of-agile-management","status":"publish","type":"post","link":"https:\/\/blog.hardscrum.com\/en\/the-fundamental-misunderstanding-of-agile-management\/","title":{"rendered":"The fundamental misunderstanding of agile Management"},"content":{"rendered":"<p>The new way of organizing and working according to lightweight and flow-oriented principles has led to a rethinking in many organizations and in many individuals. However, there are still some misconceptions, especially with the term &#8220;agile management&#8221;.<\/p>\n<p><!--more-->Many believe that leadership and management should only take the form of <strong>support, enabling and coaching<\/strong>. Thus writes the german FAZ in the article &#8220;language in the office: Unwoven of the year&#8221; that\u00a0 <a href=\"https:\/\/www.fazschule.net\/article\/aHR0cHM6Ly93d3cuZmF6Lm5ldC9ha3R1ZWxsL2JlcnVmLWNoYW5jZS9iZXJ1Zi9zcHJhY2hlLWltLWJ1ZXJvLXVuc2VyZS11bndvcnRlLWRlcy1qYWhyZXMtMTU5NTM5NjUuaHRtbA\">Agile Managers are only allowed to support<\/a>. (sorry, only available in german language)<\/p>\n<p>But also the advocates of the new management culture, such as Simon Sinek, one of my favorite speakers, sees only a supporter in the New Work Manager.<\/p>\n<p>In addition, some of the agile framework consultants for large organizations have expressed the opinion that middle management can be significantly streamlined by introducing agility. In my opinion, they are not only wrong, but also create fears in middle managers, fears about their jobs and their careers.<\/p>\n<p>Scrum and the <a href=\"https:\/\/p4-dev.com\">P4 framework<\/a> have three roles that are clearly separated in their area of \u200b\u200bresponsibility:<\/p>\n<ul>\n<li>The Product Owner, with a strong market and business responsibility,<\/li>\n<li>the Scrum Master, with the supporting, moderating responsibility, and who also takes care of the work environment and infrastructure,<\/li>\n<li>the Working Team, which is responsible for the implementation and the &#8220;incorporation of quality&#8221;, as well as the own team processes.<\/li>\n<\/ul>\n<p>All three roles have a significant management share. That&#8217;s why I call it the &#8220;Trinity of Agile Management&#8221;. The same roles can also be found in the <a href=\"http:\/\/p4-dev.com\">P4 framework<\/a> at &#8220;higher&#8221; levels: the system \/ cluster level for multiple teams and the portfolio level for multiple team clusters.<\/p>\n<p>Yes, the Scrum masters are supporters, that&#8217;s right. But the <strong>Product Owners are innovators, leaders and visionaries<\/strong>. And those responsible for technology, who are called <strong>System Engineers and Portfolio Architects in the <a href=\"https:\/\/p4-dev.com\">P4 framework<\/a>, are also designers and innovators<\/strong>.<\/p>\n<p>Therefore, even in a fully agile organization, there is still plenty of room for management positions, advancement opportunities and careers. However, one has to opt \u200b\u200bfor one of the three clearly defined areas of responsibility, which I personally see as a great advantage.<\/p>\n<p>Read more about the <a href=\"https:\/\/blog.hardscrum.com\/organizational-model-of-knowledge-work\/\">Organizational Model of Knowledge Work here<\/a>.<\/p>\n<p>{Photo by @danielmingookkim on unsplash.com}<\/p>\n","protected":false},"excerpt":{"rendered":"The new way of organizing and working according to lightweight and flow-oriented principles has led to a rethinking in many organizations and in many individuals. However, there are still some misconceptions, especially with the term &#8220;agile management&#8221;.","protected":false},"author":3,"featured_media":418,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[53,4],"tags":[220,54],"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:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/408"}],"collection":[{"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=408"}],"version-history":[{"count":17,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/408\/revisions"}],"predecessor-version":[{"id":1563,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/408\/revisions\/1563"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/418"}],"wp:attachment":[{"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=408"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=408"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}