A popular method is self-organization

[suchona.kani.z]

Practice shows that there are often special roles in organizations whose expertise we need in parts of different teams, but we cannot provide such employees for every team. In these cases, we recommend letting the special role jump between teams, but always including knowledge transfer as a work order. In this way, the teams can solve smaller, less complex special topics independently over time without having to use the special role, thus increasing their self-sufficiency.


Now that we have already determined the competencies and capacities for the teams on paper and the product owner has been assigned responsibility, there are various ways to staff the teams from the pool of employees in the organization.

Last but not least, we recommend that when selecting the people with the necessary skills for the teams, the personalities of the people in question should be taken into account. Ultimately, it is of no use if, in theory, all the necessary skills are present in the team, but they cannot be called upon because of interpersonal difficulties.

This usually results in a consensus that ensures that all teams are greece consumer email list satisfied with the team setup in the long term. The advice here is to hold a larger event with the available employees. To get everyone in the mood, we recommend that the product owner prepare a product presentation. The focus should be on the added value for potential users in order to motivate employees as best as possible to create this added value.

This allocation process can be longer or shorter depending on the number of teams that need to be formed. Empathetic colleagues in the organization can be very helpful here as contact persons and advisors.

Which brings us to Scrum Masters, Kanban Masters and Team Coaches (depending on the team's framework). The different names don't matter here, however, as the task is the same in all cases: to promote and continuously increase the effectiveness of the team. For the sake of simplicity, we will only refer to the Scrum Master from now on.