Product Owner (PO)
Supply Chain Device Lifecycle Management Product Owner (PO) is a member of the extended Product Management team and crucial member of the Agile Team. PO owns the Team / Sprint backlog representing the single source of truth and is the single point of contact to the Dev team and Customer team for user story details. PO is responsible for defining and refining user stories and prioritizing the Agile Team backlog to streamline execution of product (program) priorities while maintaining conceptual and technical integrity of features for the team. In this capacity the PO remains highly available to the Dev teams during each iteration (sprint) in order to answer real time questions and provide clarity to user stories. PO also drives user story refinement activities ensuring Team backlog contains 2 iterations worth of 'ready' work for Dev team. These two functions are critical to enabling Dev teams to improve and maintain high velocity / productivity in iteration (sprint) execution. For this reason, a PO supports a single Agile (Scrum) Team up to a maximum of 2 teams.
PO also has a significant role in quality control and is the only team member empowered to accept stories as done, ensuring the acceptance criteria has been met. This role has significant relationships and responsibilities outside their specific Agile team, including working with Product Management, who is responsible for the Product (Program) Backlog, to prepare for the Program Increment (PI) Planning meeting (Big Room Planning).
Business and Technical Execution
• Develops deep understanding of customer experience, especially at a tactical and transaction level.
• Builds and maintains Agile (Scrum / Sprint) team backlog, with input from customer, Product Manager, System Architect/Engineering and other stakeholders (team backlog consists mostly of user stories, it also includes defects and enablers.)
• Collaborates with Agile team and stakeholders to write user stories and requirements that include acceptance criteria and acceptance tests, typically for 1 or 2 (max) Agile / Scrum teams.
• Reviews and prioritizes Agile Team backlog for Iteration (Sprint) Planning, including coordination of dependencies with other Product Owners.
• Reviews and assesses enabler work, understands scope of the upcoming enabler work and collaborates with System and Solution Architect/Engineering to assist with decision-making and sequencing of the technical infrastructures that will host the new business functionality. Ultimately determining where, when and priority of enabler work so that it can be included in sequence in Team backlog(s).
• Primary resource (and source of truth / single point of contact) to Technical (Dev) team and Customer team for user story details. Highly available to technical team during iteration (sprint) in order to answer real time questions and provide clarity to user stories.
• Manages and maintains efficient flow of just-in-time story elaboration activities (user story refinement) throughout team execution, typcially maintaining 2 iterations (sprints) worth user stories available and ready in team backlog.
• Participates in team demo with primary responsibility of reviewing and accepting completed user stories (PO is the only team member who can accept as done). This includes validation that stories meet acceptance criteria and meets team's Definition of Done (DoD).
• Participates in Iteration Retrospective, where teams gather to improve their processes. Also actively supports the Agile Release Train's (ART's) Inspect and Adapt (I&A) workshop.
• 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 ensuring representation of user stories within PO's scope.
• The PI system demo is part of the I&A workshop. The PO has an instrumental role in working with Product Management team to produce the PI system demo for program stakeholders ensuring representation of user stories within PO's scope.
• Coordinates user story, functional, and techncial dependencies with other Product Owners throughout each iteration and Program Increment. This is often done in weekly PO/ART sync meetings.
• Works across Agile teams to define and implement improvement stories that will increase velocity and quality of the program.
• Accountable and responsible for user story quality and performance in production environment.
Relationship & People, Professional Development
• Develops positive working relationships with Customer groups or Customer Representatives.
• Collaborates and develops positive working relationships with technical and non-technical teams, including sales, commercial accounting, marketing, legal, go-to-market, and finance. Works with outside partners and other third parties.
• Develops professional and technical knowledge by attending educational workshops; reviews professional publications; establishes personal networks; participates in professional societies.
• Actively participates in T-Mobile Product Owner/Manager Community of Practice (COP)
It's easy, and free! Add jobs from any website! Get recommendations from your friends! Start by adding this job...