Business Professional - Systems Product Owner Lv3

Job Description : MAX BILL RATE : BR / HR.

Schedule : Monday through Friday 8 : 00 - 5 : 00 PM

Hybrid Schedule : 2-3 days a week; candidates must be local

As a Product Manager, you will be responsible for delivering products that drive value for our stakeholders. You will work with stakeholders to understand technology problems, refine and prioritize the product backlog containing user stories, tracking completion of user stories, and develop and validate solutions for team members on a day to day basis. The Product Manager possesses knowledge of product and product delivery and acts as the primary interface with other project / product teams.

80% Sprint and Release Planning and Execution

As a member of the Scrum product development team, the Product Manager is the primary point of contact and decision maker on key requirements and features to be developed. Key activities include managing requirements, defining use cases, documentation, and user stories for the current sprint as well as refining and preparing for subsequent sprints.

Requirements Gathering : The Product Manager works across teams to understand requirements and convert to actionable items on the backlog. The Product Manager is accountable for synchronizing scrum teams backlog activities, user story creation, acceptance criteria and loading into our feature / requirement tracking tool.

Product Release / Planning : The Product Manager transforms product vision from Product Management into actionable release backlogs. The Product Manager manages the product backlog pulling items which provide the most value to the customer into the release backlog in preparation for release planning. The Product Manager also has a significant role in the planning event itself as the main point of contact for questions and clarification of user stories Backlog Management : The Product Manager has the primary responsibility to build, refine, and maintain the product backlog. The backlog consists mostly of user stories, but also includes defects, technical debt and infrastructure work. Backlog items are prioritized based on user value, time and other team dependencies which are determined in Release Planning.

Release Planning : During Release Planning, the Product Manager is involved with user story definition, writing acceptance criteria, providing clarifications necessary to assist the team with their story estimates, sprint planning, story sequencing, and drafting the team s specific objectives for the upcoming sprints

Quality : Monitor ongoing performance of features and act as point of contact for questions, concerns and suggestions. Provide input on test strategy and test cases, being an advocate of quality solutions that meet or exceed defined customer expectations. Perform reviews with key internal teams throughout the design lifecycle to ensure alignment on solution designs and requirements

Leadership : Holds self and project team accountable for their deliverables to ensure timely, cost-effective project execution.

20% Stakeholder Insights & Communications

The Product Manager is responsible for gathering input from and managing expectations of the voice of the stakeholders in a software development cycle including product management, marketing, customer support, scrum master, project management, and development team members.

Develop strong relationships with all development, internal groups, and stakeholders in order to ensure timely and effective delivery of software features and defect resolution.

In collaboration with other team members, identify and prioritize key product documentation as needed.

Create and maintain long-term working relationships with technology teams, functional counterparts, 3rd parties, go to market.

Engage and influence internal leaders and stakeholders to help contribute to their targeted product development and return on investment.

Engage and influence team members to ensure productivity and solution quality.

Monitor the functional / product landscape for changes in competitive positioning.

Project demands may from time to time require work during non-standard business hours. An example would be during a system implementation at a plant which can only happen during scheduled

downtime.

Must complete background check only

Additional Sills :