Job Summary

• Coach 2-week Scrum teams through the full ceremony set: Sprint Planning, Daily Scrum, Sprint Review, Retrospective, and Backlog Refinement

• Ensure ceremonies deliver real value, not ritual compliance. Spot and address anti-patterns (e.g., Daily Scrum becoming a status report to the EM, retros raising the same issues with no action)

• Drive adoption of Definition of Ready as a genuine quality gate between discovery/UX and sprint entry

• Transition teams from hours/days estimation to relative sizing (story points) using velocity-based forecasting

• Design and implement Kanban systems for infrastructure and operations teams, including board design, WIP limits, buffer states, and pull policies

• Introduce classes of service (Standard, Expedite, Fixed Date) and help teams define SLAs for each

• Establish Kanban cadences: replenishment meetings, daily standups at the board, and service delivery reviews

• Configure and maintain JIRA dashboards for team-level metrics: predictability (say/do ratio), lead time, cycle time, throughput, quality (escaped defects), and flow efficiency

• Teach teams to read and act on Cumulative Flow Diagrams, cycle time scatter plots, and throughput run charts

• Facilitate retrospectives using a variety of formats (Start/Stop/Keep, Timeline) and ensure improvement actions are tracked and completed

• Coach within Eeze's specific organisational model where Engineering Managers carry significant planning and execution accountability

• Protect team self-management and the Scrum Master role without undermining the EM's legitimate responsibilities

• Help teams and EMs understand the guardrails documented in the playbook's RACI matrix

• Configure and maintain Scrum and Kanban boards aligned to the playbook's hierarchy: Initiative → Epic → Story → Sub-task (with Tasks for Kanban teams)

• Ensure sprint goals are documented and distributed, blocked items are flagged, and dependency links are maintained

• Support teams in using JIRA Premium features effectively

• Coach Business Owners on their role during Sprint Reviews — providing feedback, validating business value, and adjusting priorities based on demonstrated outcomes

• Help teams present work in terms of business outcomes (not just feature demos) so Business Owners can make informed investment decisions

• Facilitate the connection between team-level delivery and the business value metrics that Business Owners care about

• 3–5 years of experience as an Agile Coach, Scrum Master, or equivalent role coaching multiple teams simultaneously in a product development environment

• Deep practical knowledge of Scrum and Kanban, not just theory, but the ability to diagnose what's going wrong in a standup or a retro and intervene effectively

• Experience coaching teams through an Agile transformation (not just maintaining existing practices)

• Strong facilitation skills, you can hold space for difficult conversations in retrospectives and planning sessions

• Fluent English

• CSM/PSM II, KMP, or ICAgile-ICP certification

• Experience in iGaming, fintech, or regulated tech environments

• Familiarity with SAFe (particularly team-level practices within a scaled context)

• Experience working in organisations where engineering management and Scrum Master roles overlap or coexist

• Understanding of Domain-Driven Design concepts and Team Topologies

• Personal Qualities

• You coach by building capability, not by becoming a "super Scrum Master" who runs everything

• You're comfortable with ambiguity — Eeze's model has deliberate deviations from textbook Agile, and you can work within that

• You have the patience to change habits gradually and the assertiveness to call out anti-patterns when they matter

• You understand that psychological safety is a prerequisite for continuous improvement, and you model it