Project Management

Project management in games keeps scope, schedule and people in agreement: planning, dependencies, risk, and reporting a team can actually use.

The duties are planning across disciplines, tracking dependencies, running milestones, keeping a backlog honest, and reporting status upward - including the unwelcome part, which is saying early that a date will not hold.

Games bring their own difficulties. Creative work resists estimation, platform certification and store slots are fixed dates, external partners for art, audio and localisation sit in the critical path, and a live title needs a cadence rather than a finish line. Production tooling and version control belong to the requirements because the work happens inside the same pipeline as the team's.

The titles differ more than the duties. A producer carries delivery responsibility for a game or a feature. A project manager covers a defined programme or a cross-team initiative. A scrum master owns process rather than outcome. Release and operations positions use the same skill against a narrower target.

Where these positions are: Barcelona (6 positions), London (5 positions), Stockholm (5 positions), Paris (4 positions), Helsinki (3 positions), Warsaw (3 positions), Berlin (2 positions), Brighton (2 positions), Copenhagen (2 positions), Munich (2 positions), Belgrade (1 position), Cambridge (1 position), Cologne (1 position), Dublin (1 position), Frankfurt (1 position), Gdańsk (1 position), Kyiv (1 position), Malmo (1 position), Manchester (1 position), Newcastle upon Tyne (1 position), Potsdam (1 position), Vilnius (1 position), Wrocław (1 position)