Erik's Scrum Journey

I have had good experiences with discussing the responsibilities between Scrum Master, Product Owner and Dev Team together.

I proceed as follows: 1. the Scrum Master builds a board that describes the “default setting” in Scrum, e.g. ownership of the product backlog or the Scrum backlog. 2. then a.) the tasks are concretized, cut or divided and b. discussed together in order to 3. arrive at a common matrix that functions as a team agreement.

As Scrum Master, it is particularly important to keep an eye on the basic settings of the framework and to correct any deviations.

Inspect and adapt this agreement regularly ... ;)

Read the collab article here: https://lnkd.in/ek8STtin

#Scrum #Responsibilities #ScrumMaster #DevTeam #ScrumTeam #TeamAgreement

---

Find me on:

LinkedIn: https://www.linkedin.com/in/ehauth/ Mastodon: https://norden.social/@ring2

Me: As a Senior Scrum Master, I lead agile teams to deliver innovative and user-centric digital products and services for the media industry. With over 25 years of work experience in various roles and sectors, I have developed a diverse and versatile skill set that includes Scrumban, Scrum, Facilitation, Product Management, and Project Leadership.

I hold a Certified Scrum Master (CSM) credential from Scrum Alliance and a Facilitator badge. I also write as a columnist for ZEIT ONLINE, sharing my insights and perspectives on topics such as digital transformation, innovation, and culture.

Was tue ich als Scrum Master, wenn ich mit “ Servant Leadership” nicht weiter komme?

Eine vollkommen unterschätzte Rolle des Scrum Masters ist die des “Domain Leaders”. Neben dem “Servant Leader” eine der Führungsrollen in Scrum – allerdings eine offensivere.

Wenn Servant Leadership an ihre Grenzen stößt

Der “Domain Leader” sorgt dafür, dass quasi die Diskursethik im und gegenüber dem Scrum Team stimmt. Gibt es beispielsweise Probleme mit notorisch störenden Charakteren (bis hin zu Saboteuren), kann diese Führungsrolle auch Menschen zeitweise von Events bspw. ausschließen, oder Auflagen formulieren, die in der “Domäne” des Scrum Teams vereinbart sind.

Bis hin zum Entfernen von Personen aus dem Scrum Team.

Als Tool nutze ich gerne “Team Agreements”, die auch beinhalten, dass es Sanktionen geben kann, wenn sich nicht an gemeinsame Vereinbarungen gehalten wird.

#Scrum #ScrumMaster #Leadership

---

Find me on:

LinkedIn: https://www.linkedin.com/in/ehauth/ Mastodon: https://norden.social/@ring2

Me: As a Senior Scrum Master, I lead agile teams to deliver innovative and user-centric digital products and services for the media industry. With over 25 years of work experience in various roles and sectors, I have developed a diverse and versatile skill set that includes Scrumban, Scrum, Facilitation, Product Management, and Project Leadership.

I hold a Certified Scrum Master (CSM) credential from Scrum Alliance and a Facilitator badge. I also write as a columnist for ZEIT ONLINE, sharing my insights and perspectives on topics such as digital transformation, innovation, and culture.