Product Owner

NOVOVISION is a casino management system serving dozens of customers across the gaming industry. The company is undergoing a transformation to mature how it builds and delivers software, focusing on strong, disciplined product ownership with clear vision, well-maintained backlog, sharp prioritisation, and confidence to challenge requests that do not serve the product's long-term direction.

Must-have experience:

• Solid, hands-on Product Owner experience - you have owned a backlog, run sprints, and are accountable for product outcomes
• Demonstrable backlog hygiene discipline - you can show what a well-maintained Jira board looks like and explain how you got there
• Strong user story writing - you understand the difference between a story and a task, and you write acceptance criteria that engineering teams can actually use
• Experience managing and synthesising input from multiple stakeholders with competing priorities
• Proven ability to say no constructively - with reasoning, alternatives, and maintained relationships
• Comfortable working in Jira and Confluence as primary tools of record

Ways of working:

• Rigorous - you treat backlog hygiene and documentation as professional standards, not administrative overhead
• Decisive - you can make prioritisation calls under pressure and explain them clearly
• Collaborative - you work with Design, Engineering, Sales, and Market Owners as genuine partners, not information consumers
• Curious - you ask 'why' before 'what', and you validate assumptions before committing to solutions
• Resilient - you can handle a large, messy backlog and multiple stakeholders without losing focus or rigour

Optional:

• Experience in the casino or gaming technology sector - this is a significant advantage given the compliance and market complexity of our environment
• Familiarity with multi-market or multi-tenant product environments
• CSPO (Certified Scrum Product Owner), PSPO (Professional Scrum Product Owner), or equivalent
• Any Agile/Scrum practitioner certification is a positive signal of foundational discipline

Own your product domain end-to-end & backlog management:

• Take full accountability for the product vision, backlog, and roadmap within your assigned domain
• Define and maintain a clear, prioritised backlog in Jira - well-structured, up-to-date, and genuinely useful to engineering teams
• Write high-quality user stories with clear acceptance criteria, context, and rationale - not just task descriptions
• Own the 'why' behind every item in your backlog; be able to articulate business value and user impact for each initiative
• Take over and restructure an existing, high-volume backlog - apply frameworks and discipline to bring it under control
• Ruthlessly prioritise: distinguish between must-haves, should-haves, and items that should simply be closed
• Introduce and maintain backlog hygiene practices - regular grooming, story readiness criteria, and sprint-ready definitions
• Use data, usage patterns, and stakeholder input to drive prioritisation decisions, not just volume or loudness of requests

Product decision-making & stakeholder alignment:

• Act as the gatekeeper for your domain - evaluate incoming feature requests from Sales, Market Owners, and engineering against product strategy
• Confidently push back on requests that lack clear value, conflict with the roadmap, or would create unsustainable technical or product debt
• Facilitate discovery conversations to understand the real need behind a request before committing to a solution
• Document decisions and their rationale in Confluence - create a transparent record of what was decided and why
• Manage stakeholder expectations proactively: communicate roadmap status, changes, and trade-offs clearly and consistently
• Represent your domain in cross-functional planning discussions with confidence and with evidence

Collaboration across product, design, and engineering:

• Work hand-in-hand with the Product Design department from early discovery through to delivery - design and product ownership should be inseparable in how we work
• Co-own the user experience vision for your domain; ensure UX and functional requirements are developed together, not sequentially
• Review and validate designs against acceptance criteria and user needs before handoff to engineering
• Serve as the primary point of contact between engineering teams and business stakeholders for your domain
• Translate market and sales input into clear, actionable product requirements - and translate engineering constraints back to stakeholders in plain language
• Participate in sprint ceremonies: planning, reviews - as an active contributor, not a passive attendee
• Work closely with the IT Project Manager to ensure your roadmap aligns with delivery capacity and project commitments