Scrum Master
A scrum master keeps an agile team's process working: the meetings that matter, the obstacles that need removing, and the honesty about what a sprint can hold.
The role serves the team rather than directing it. It runs planning, review and retrospective so they stay short and useful, keeps the backlog in a state the team can work from, and spends the rest of its time removing whatever is blocking someone: a missing decision, a dependency, a tool that does not work.
Game development stretches agile practice in a specific way. Creative work is hard to estimate, a feature often cannot be judged until it is playable, and milestones towards a fixed release date sit awkwardly beside open-ended sprints. A scrum master who insists on ceremony over outcome makes that worse rather than better.
A Producer owns what the game needs and when. A Project Manager owns plan and budget. The scrum master owns how the team works day to day.
Where these positions are: Munich (1 position)
