Technical Product Owner

Purpose of the Role
As the technical product owner you deliver engineering efficiency and platform stability. This means that your main customers are the product and engineering teams. You will work on projects such as automating zero downtime deployments, rationalising logging, implementing telemetry and improving developer experience through code generation - maximising the value delivered by the team.
You live by the 3 pillars of Product Ownership - Clarity, Complexity and Conviction. You work embedded in an engineering scrum team where your responsibilities include ensuring high quality documentation, productive grooming with engineers and providing clarity throughout the development process.

The TPO is enthusiastic in applying cloud/platform expertise in a Product role, and enjoys connecting the two. Leveraging experience of cloud environments (ideally AWS), agile platform engineering and software-as-a-service combined with commercial awareness to visualise how to turn technology requirements into a structured Product roadmap/backlog.

The TPO is an outstanding communicator and stakeholder manager, you will thrive in a culture where you can build relationships, identify new opportunities and develop solutions that meet the needs of engineers, of the business and of end-users.

The TPO also works as the Release Manager to deliver the product to our customer. Using your extensive digital knowledge you have an in-depth insight into dependencies and delivery constraints and have a consistent eye on improving delivery to minimise risk and cost.

A Typical Day
Working remotely your first check-in will be at the daily standup where you will get to understand the progress on the team commitment for the sprint. You answer any questions related to the requirements and try to remove any impediments to progress.

You invest the time necessary to document clearly and comprehensively, covering the edge cases that nobody else would think of.

After your mid-morning coffee you lead the Grooming session with your scrum team, starting with a feature overview that provides context to your audience, and then working through the sizing process scenario-by-scenario you conclude the session with a well-groomed feature ready to enter development

You plan out the next releases and examine the dependencies for each release.

Responsibilities

• Requirements Development
• Represents the voice of the User.
• Work closely with Product Management and Engineering to create and maintain a product backlog according to business objectives.
• Converts ideas into User Stories/Use Cases to describe platform Features and provide clarity for developers.
• Ensure complex requirements are discussed with Technology ahead of time to ensure any Architectural concerns are handled.
• Provide a prioritised and groomed feature backlog for your scrum team.
• Ensure a well-groomed backlog item includes user story, acceptance criteria, story point estimate and clear value.
• Providing vision and direction to the Agile development team and stakeholders throughout the project
• The voice for Platform Roadmap within your team, including upcoming development and releases.
• Represent the business in Backlog Grooming sessions with the Development Team.
• Release Management
• Define software release scope as the Release Manager.
• Plan product releases and set the expectation for delivery of features.
• Actively participate in Sprint Planning meetings and understand the progress made by the team since the previous meeting.
• Active in mitigating impediments impacting successful team completion of Release/Sprint Goals
• Fields all requirement questions from the Development Team and provides answers within a reasonable timeframe.
• Organises, coordinates releases.
• Identify and action improvements to the release process
• Continuous Improvement
• Seek and identify opportunities to improve the Requirements Development process.
• Actively participate in Sprint Retrospectives.
• Keep abreast with Agile/Scrum best practices and new trends