Product Owner

at  Medtronic

At Medtronic you can begin a life-long career of exploration and innovation, while helping champion healthcare access and equity for all. You’ll lead with purpose, breaking down barriers to innovation in a more connected, compassionate world.
A Day in the Life
With our award-winning Touch Surgery ecosystem, it is the dawn of Digital Surgery. Medtronic has created a digital data-driven ecosystem that uses the latest cutting-edge technologies like artificial intelligence, augmented reality, live video streaming & collaboration, and computer vision to modernize surgical workflows, orchestrate surgical teams in the operating room (OR) and deliver safer surgery around the world. If you’re interested in using modern technology and the best in user experience to improve the standard of care in surgery on a global scale, and to help surgeons, this could be the place for you.
We are currently looking for a talented Product Owner to help contribute to our amazing mission. The Product Owner (PO) is a member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to streamlin e 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 maximizing the value produced by the team and ensuring Stories meet the user’s needs and comply with the Definition of Done.

Responsibilities may include the following and other duties may be assigned:

• Participation in Roadmap Planning and Goal Setting - As a member of the Product Team, the PO is heavily involved in backlog refinement and prep for roadmap planning. The PO updates the team backlog and typically reviews and contributes to the vision, Roadmap, and content presentations. During the planning, the PO is involved with story definition, providing the clarifications necessary to assist the team with their story estimates and sequencing.
• Maintaining the team backlog – With input from Product Manager/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 (Impact vs Effort), and other team dependencies.
• Sprint Planning – The PO reviews and reprioritizes the backlog as part of the prep work for Sprint Planning, including coordination of dependencies with other POs. During the sprint planning event, the PO communicates story detail and priorities and ensures the team aligns and agrees on a final sprint plan. Just-in-time story elaboration – most backlog items are elaborated into user stories for implementation. This may happen before the sprint, during sprint planning, or during the sprint. 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.
• 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 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 – POs collaborate with their team and any other stakeholders in the team demo. They also participate in the Sprint Retrospective, where the teams gather to improve their processes.

Required Knowledge and Experience:

• 1-3 years of software development, product ownership, or UX experience with Agile teams
• You understand the Agile process and can successfully drive Agile projects
• Proven experience of working in an agile development environment with Product Managers and Engineers to create new digital/hardware products and services
• Exceptional attention to details and great organizational skills
• You are flexible – You can independently solve problems as they arise, but are comfortable asking for help when you need it
• You are a great communicator – You are comfortable talking with developers, customers (surgeons and hospital leaders), business leaders, and everyone in-between
• Excellent stakeholder management skills combined with a flexible and adaptable approach in order to achieve successful stakeholder satisfaction
• Self-driven with ability to work independently and collaboratively
• You love the technology you have, but love building tomorrow’s tech even more
• Experience working with clinicians and health professionals/ surgeons
• Knowledge of Test Driven Development and Behaviour Driven Development environments
• Understanding of health software systems and medical devices - preferably in the surgical arena Willingness to travel with some overnight stays

Physical Job Requirements
The above statements are intended to describe the general nature and level of work being performed by employees assigned to this position, but they are not an exhaustive list of all the required responsibilities and skills of this position.
Benefits & Compensation
Medtronic offers a competitive Salary and flexible Benefits Package
A commitment to our employees lives at the core of our values. We recognize their contributions. They share in the success they help to create. We offer a wide range of benefits, resources, and competitive compensation plans designed to support you at every career and life stage.
About Medtronic
We lead global healthcare technology and boldly attack the most challenging health problems facing humanity by searching out and finding solutions.
Our Mission — to alleviate pain, restore health, and extend life — unites a global team of 90,000+ passionate people.
We are engineers at heart— putting ambitious ideas to work to generate real solutions for real people. From the R&D lab, to the factory floor, to the conference room, every one of us experiments, creates, builds, improves and solves. We have the talent, diverse perspectives, and guts to engineer the extraordinary.
Learn more about our business, mission, and our commitment to diversity
her

• Participation in Roadmap Planning and Goal Setting - As a member of the Product Team, the PO is heavily involved in backlog refinement and prep for roadmap planning. The PO updates the team backlog and typically reviews and contributes to the vision, Roadmap, and content presentations. During the planning, the PO is involved with story definition, providing the clarifications necessary to assist the team with their story estimates and sequencing.
• Maintaining the team backlog – With input from Product Manager/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 (Impact vs Effort), and other team dependencies.
• Sprint Planning – The PO reviews and reprioritizes the backlog as part of the prep work for Sprint Planning, including coordination of dependencies with other POs. During the sprint planning event, the PO communicates story detail and priorities and ensures the team aligns and agrees on a final sprint plan. Just-in-time story elaboration – most backlog items are elaborated into user stories for implementation. This may happen before the sprint, during sprint planning, or during the sprint. 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.
• 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 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 – POs collaborate with their team and any other stakeholders in the team demo. They also participate in the Sprint Retrospective, where the teams gather to improve their processes