Product Owner at ASSA ABLOY Group

Profile Summary:

• The Product Owner (PO) represents business priorities as set by PACS Product Management (represented by Product Managers) into relevant scrum teams. The PO also attends relevant Product Management meetings about planning and Program Backlog/Vision refinement. This specific role’s assignment will be focused physical access control (PACS) and Access Control Devices (controllers).
• The Product Owner follows the principles of Agile development. Gathers product requirements and assure that the team is always doing “the right thing”. The PO understands the product vision, identifies the needs and passes them on to the team in a clear and comprehensive manner.
• Gives constant feedback and bring new ideas on Product features. Manages a well-groomed and prioritized user story backlog[SE1] . Manages backlogs of 1 or 2 teams.
• This position is a key leadership role. This PO will own the PACS Controllers - Mercury product lifecycle with focus on M1 product in a lean start-up environment, backed by our global core teams.

Qualifications

• To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

Duties and Responsibilities include the following (Other duties may be assigned):
Preparation and participation in PI planning:

• As a member of the extended Product Management team, the PO is heavily involved in program backlog refinement and prep for Program Increment (PI) planning and also plays a significant role in the planning event itself.
• During the event, the PO is involved with story definition, providing the clarifications necessary to assist the team with their story estimates and sequencing.

Iteration 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.
• 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 meeting, the PO communicates story detail and priorities and ensures the team aligns and agrees on a final iteration plan.
• 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).
• 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 Architect/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 Iteration Retrospective, where the teams gather to improve[SE1]  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.
• The PO also has an instrumental role in producing the System Demo for program and Value Stream stakeholders.

Inspect and adapt:

• 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.

Education and/or Experience:

• B.S. degree preferably in a technical field or equivalent combination of education and experience. 7+ years’ experience in new[SE1]  product development.
• Experience encompassing hardware/firmware/software integration and test, new product introduction to manufacturing, and production launch.
• Experience with agile [SE2] [SE3] [SE4] development and lean innovation practices is a benefit. Training in SAFe such as Implementing SAFe and / or SAFe POPM is a benefit.

Customer Expectations:

• Excellent communication skills that can connect with all levels of the organization via face-to-face and group presentation

Language Skills:

• Ability to effectively communicate in the English language verbally and in writing. Must be able to present ideas and projects before groups of individuals

Computer Skills:

• Proficient in MS Office applications, such as Word, Excel, PowerPoint, etc. Familiar with current operating systems, such as Windows, etc.
• Knowledge of Microsoft Teams or other web-based communications software beneficial. Experience with Jira and Miro desired.