What are the responsibilities and job description for the Product Owner position at BNY Mellon?
Overview
Overview:
Provides application design and support services to applications teams. Creates flexible and scalable designs for high performance. Enforces best practices and principles of architecture while complying with the firm's architecture policies and procedures. Is responsible for architecture solutions mainly with a line of business focus. In addition to the individual contributor primary responsibilities shown below, may also have managerial responsibilities such as: participates in the recruiting process; instructs, assigns, directs and reviews the work of architects; prepares performance reviews and provides ongoing feedback. Designs stable and flexible, high performance solutions aligned with architecture principles. Engages in various design and execution activities with other stakeholders. Identifies organization-wide initiatives and makes recommendations for the use of technology. Works closely with senior management to educate and to articulate resource requirements necessary to promote architecture goals. Works toward architecture solutions, mainly with a line of business focus. Engages in enterprise architecture solutions as part of service delivery support and career development. Involved in governance and other design activities. Works with administrators to maintain and publish architecture policies, standards etc. Contributes to the achievement of team objectives.
Member of the Agile Team responsible for defining stories and prioritizing the backlog to streamline the execution of priorities while maintaining the conceptual and technical integrity of the features or components for the team. Each agile team has a dedicated product owner. The product owner is responsible for the team backlog, defining, and accepting user stories. The product owner answers the team’s questions during development. The PO is the member of the Agile team who serves as the customer proxy responsible for working with Product Management and other stakeholders—including other POs—to define and prioritize stories in the Team Backlog. This allows the Solution to effectively address program priorities while maintaining technical integrity.
Responsibilities:
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.
Experience in leading team & creating stories
Strong experience in Jira and understanding how best to organize Jira tickets.
Strong knowledge of Agile principles
Preferred experience as Scrum Master who has lead developments team, has testing experience and advise on design strategy.
Qualification:
Bachelor's degree in computer science or a related discipline, or equivalent work experience required. Advanced degree preferred. 8-10 years of experience in technology and architecture roles required; experience in the securities or financial services industry is a plus
BNY Mellon is an Equal Employment Opportunity/Affirmative Action Employer. Minorities/Females/Individuals with Disabilities/Protected Veterans. Our ambition is to build the best global team – one that is representative and inclusive of the diverse talent, clients and communities we work with and serve – and to empower our team to do their best work. We support wellbeing and a balanced life, and offer a range of family-friendly, inclusive employment policies and employee forums.
Overview:
Provides application design and support services to applications teams. Creates flexible and scalable designs for high performance. Enforces best practices and principles of architecture while complying with the firm's architecture policies and procedures. Is responsible for architecture solutions mainly with a line of business focus. In addition to the individual contributor primary responsibilities shown below, may also have managerial responsibilities such as: participates in the recruiting process; instructs, assigns, directs and reviews the work of architects; prepares performance reviews and provides ongoing feedback. Designs stable and flexible, high performance solutions aligned with architecture principles. Engages in various design and execution activities with other stakeholders. Identifies organization-wide initiatives and makes recommendations for the use of technology. Works closely with senior management to educate and to articulate resource requirements necessary to promote architecture goals. Works toward architecture solutions, mainly with a line of business focus. Engages in enterprise architecture solutions as part of service delivery support and career development. Involved in governance and other design activities. Works with administrators to maintain and publish architecture policies, standards etc. Contributes to the achievement of team objectives.
Member of the Agile Team responsible for defining stories and prioritizing the backlog to streamline the execution of priorities while maintaining the conceptual and technical integrity of the features or components for the team. Each agile team has a dedicated product owner. The product owner is responsible for the team backlog, defining, and accepting user stories. The product owner answers the team’s questions during development. The PO is the member of the Agile team who serves as the customer proxy responsible for working with Product Management and other stakeholders—including other POs—to define and prioritize stories in the Team Backlog. This allows the Solution to effectively address program priorities while maintaining technical integrity.
Responsibilities:
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.
Experience in leading team & creating stories
Strong experience in Jira and understanding how best to organize Jira tickets.
Strong knowledge of Agile principles
Preferred experience as Scrum Master who has lead developments team, has testing experience and advise on design strategy.
Qualification:
Bachelor's degree in computer science or a related discipline, or equivalent work experience required. Advanced degree preferred. 8-10 years of experience in technology and architecture roles required; experience in the securities or financial services industry is a plus
BNY Mellon is an Equal Employment Opportunity/Affirmative Action Employer. Minorities/Females/Individuals with Disabilities/Protected Veterans. Our ambition is to build the best global team – one that is representative and inclusive of the diverse talent, clients and communities we work with and serve – and to empower our team to do their best work. We support wellbeing and a balanced life, and offer a range of family-friendly, inclusive employment policies and employee forums.
Product Owner
Compunnel Inc. -
Jersey, NJ
Product Owner
Info Origin, Inc. -
Newark, NJ
Product Owner
Accroid Inc -
Tysons Corner, VA
