Product Owner

Summary:

Plans, designs, develops and tests software systems or applications for software enhancements and new products including cloud-based or internet-related tools. Most companies should be able to match to a specific software development engineer position. Use this position if company does not breakout software development positions such as Software Engineer (Applications) (5141-5146) or Software Engineer (Systems) (5161-5166).

Duties & Responsibilities:

The PO is responsible for defining Stories and prioritising the Team Backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components for the team. The PO has a significant role in quality control and is the only team member empowered to accept stories as done. This is a critical role and a full-time job, requiring one PO to support each Agile team (or, at most, two teams). The PO has significant relationships and responsibilities outside the local team, including working with Product Management, who is responsible for the Program Backlog, to prepare for the Program Increment (PI) Planning meeting

• The PO is heavily involved in program backlog refinement and prep for PI planning also plays a significant role in the planning event itself.
• Assess MCRs and define Stories (Enablers, Feature) to capture WHAT (not how) must be done to deliver the MCR
• Define Test Purposes (requirements acceptance criteria) for MCR
• Responsible for the statement of compliance of the MCR (for example 3GPP or customer requirements/use cases)
• Understanding and analysing requirements (customer and 3GPP)
• First point of contact for product management
• Prioritise team backlogs for stories, including enablers and observations
• Works with Architects to define architectural guidelines
• The PO maintains the team backlog – With input from System Architect/Engineering and other stakeholders, the PO has the primary responsibility for building, editing, and maintaining the team backlog.
• The PO reviews and reprioritises the backlog as part of the prep work for Iteration Planning, including coordination of dependencies with other POs.

Supporting Test–Driven Development (TDD) – POs participate in the development of story acceptance criteria, draft them when feasible, and provide examples in support of TDD specification by example.
• Accepting stories – The PO is the only team member who can accept stories as done and assures a level of quality, focusing primarily on fitness for use.
• Understand enabler work – While POs are not expected to drive technological decisions, they are supposed to understand the scope of the upcoming enabler work and to collaborate with System and Solution Architect/Engineering to assist with decision-making and sequencing of the critical technological infrastructures that will host the new business functionality.
• Participate in team demo and retrospective – As the person responsible for requirements, POs have an essential role in the team demo, reviewing and accepting stories. They also participate in the Iteration Retrospective, where the teams gather to improve their processes and are active in the Agile Release Train’s (ART’s) Inspect and Adapt (I&A) workshop.
• During each PI, the PO coordinates dependencies with other POs.
• The PO also has an instrumental role in producing the System Demo for program and Value Stream stakeholders.
• Teams address their larger impediments in the I&A (inspect and adapt) workshop. There, the PO works across teams to define and implement improvement stories that will increase the velocity and quality of the program.
• The PI system demo is part of the I&A workshop. The PO has an instrumental role in producing the PI system demo for program stakeholders.
• To ensure that they will be able to show the most critical aspects of the solution to the stakeholders, POs also participate in the preparation of the PI system demo.
• Product Management and the PO share the content authority for the program

Pre-Requisites / Skills / Experience Requirements: