Reporting in Data Architecture Governance and Operations Programs management team the Data Product Owneroversees the development of data products from start to finish to ensure they meet the clients' needs and preferences cross all Enterprise Domains assigned use cases. Their main duties include determining the overall vision of products, managing various backlog items and deciding which features each product will have according to clients' preferences.
Functions:
As part of their role on a product team, a successful Product Owner should fulfill the following duties and responsibilities:
Collaborating with prospective users and clients to understand and anticipate their needs and translate them into product requirements
Defining the vision for the team's product
Creating a product road map based on this vision
Managing the product backlog and prioritizing them based on changing requirements
Overseeing all stages of product creation including design and development
Developing user stories
Monitoring and evaluating product progress at each stage of the process
Liaising with the product team and end-users to deliver updates
Participating in Scrum meetings and product sprints
Will collaborate closely with both the scrum and product development departments to ensure the products meet specific objectives as outlined by stakeholders. After product completion, the Product Owner will conduct a final review and submit their approval before releasing the product .
Execution:
Maintaining 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. Consisting mostly of user stories, it also includes defects and enablers. Backlog items are prioritized based on user value, time, and other team dependencies determined in the PI planning event and refined during the PI. Iteration Planning - The PO reviews and reprioritizes the backlog as part of the prep work for Iteration Planning, including coordination of dependencies with other POs. During the iteration planning event, the PO communicates story detail and priorities and ensures the team aligns and agrees on a final iteration plan. Just-in-time story elaboration - Most backlog items are elaborated into user stories for implementation. This may happen before the iteration, during iteration planning, or during the iteration. While any team member can write stories and acceptance criteria, the PO maintains proper flow. Apply Behavior-Driven Development (BDD) - POs collaborate with their team to detail stories with acceptance criteria and examples in the form of acceptance tests. See the BDD article for more details. Accepting stories - The PO works with the team to agree on accepted story completion. This includes validating that the story meets acceptance criteria, that it has the appropriate, persistent acceptance tests, and that it otherwise complies with its Definition of Done (DoD). In so doing, the PO also 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 collaborate with System and Solution Architects/Engineering to assist with decision-making and sequencing of the critical technological infrastructures that will host the new business functionality. This can often be best accomplished by establishing a capacity allocation, as described in the Team Backlog article. Participate in team demo and retrospective - POs collaborate with their team and any other stakeholders in the team demo. 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.
Program Execution:
Iterations and Agile teams serve a larger purpose; the frequent, reliable, and continuous release of value-added solutions. During each PI, the PO coordinates dependencies with other POs. This often occurs in weekly PO sync events (see the PI article for more information). The PO also has an instrumental role in producing the System Demo for program and Value Stream stakeholders.
Inspect and Adapt:
Teams address their larger impediments in the I&A 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.
Skills and Qualifications:
To carry out the role of a Product Owner successfully, a candidate should possess the following skills and qualifications:
In-depth knowledge of Scrum and Agile Software Development Methodology
Working knowledge of product development architecture
Proficiency in the use of analytic tools
Ability to prioritize effectively
Excellent knowledge of user-centered design principles
Excellent oral and written communication
Ability to work with large teams
Understanding of design quality standards
5+ years in Technical Project/Program Management roles/PO
Certifications: Six Sigma, PPM, Agile
Master: MBA or Similar (Optional)
Conditions:
Long term contract. Direct hiring by this multinational company.
Very attractive and competitive salary (according to the skills and experience of the candidate) and important social benefits.
Starting Day: ASAP
Location: Barcelona (40% remote work)
