Requirement Gathering and Analysis
§ Accountable and responsible for the production of clear, high-quality, specific, unambiguous, and traceable, requirements, both functional and non-functional, for controlled changes of various complexities, and presenting them for review in accordance with the appropriate Definition of Ready.
§ Facilitates scoping and business priority setting for large or complex changes, engaging senior stakeholders as required, and selects the most appropriate means of representing business requirements in the context of a specific change initiative.
§ Accountable and responsible for the definition of specific and measurable Acceptance Criteria
§ Accountable and responsible for the assessment of reported defects, non-functional requirements, and other technical debt, triaging severity and prioritizing resolution alongside feature work, to ensure not only that the product always meets established Quality Criteria, but that quality continuously improves.
§ Accountable and responsible for the generation of documents and other artifacts describing current and future product features and functions, using approved processes
§ Proactively develops and maintains own specialist expertise and commercial awareness, demonstrating understanding of the relevant business areas and its customers.
§ Responsible to learn the product(s), hands-on, to ensure proper understanding of context, features and functions, and to share knowledge with the team and other stakeholders, in both formal and informal sessions
Prioritization and Planning
§ Responsible for setting priorities and developing plans in collaboration with key stakeholders against planned objectives, in consideration of constraints, dependencies and competing interests, and ensuring that the product needs and vision are maintained.
§ Responsible for tracking progression over time to ensure client, business, and technical goals are met, supporting sprint planning and similar activities when required
§ Responsible for coordinating development and defect resolution across multiple teams, programmes and locations, and identifying dependencies between teams
§ Responsible for establishing an agile, iterative and data driven team or group backlog in collaboration with key stakeholders
§ Accountable and responsible for ensuring the timely progression of backlog items, including ensuring they are assigned appropriately, and the recorded status, in accordance with processes and procedures
§ Accountable and responsible for the regular presentation of progress, issues, and risks to all stakeholders
People Management
§ Line management of multiple Product Owners across multiple Agile teams in different product areas
§ Encourage a culture of collaboration, innovation, and continuous improvement within the product team.
§ Facilitate knowledge sharing and best practices across the team to enhance efficiency and effectiveness.
§ Responsible for the continual growth and success of team members, including:
o Encouraging a culture of personal development ownership
o Acting as a role model, displaying a positive enthusiastic, can-do approach in the face of adversity
o Ensuring that all team members have stretching goals, development plans and regular performance reviews to embed a high performance culture.
o Support and induction of new team members ensuring development of technical knowledge and clarity around behavioural and cultural expectations
Working Practices with Product Owners
§ Membership of and active contribution to the Product Owner practice leadership team
§ Driving best practice around the Product Owners including, improving processes to increase efficiency and performance, set and update standards, etc.
§ Provide necessary guidance to Product Owners in relation to product capabilities
§ Providing leadership amongst peers, and more junior members of the team, ensuring quality through fair and challenging feedback
Working Practices and with Software Engineering Teams
§ Engaging with management and members of Software Engineering teams across the globe
§ Engaging regularly with Software Engineering leaders
§ Ensuring that Software Engineers understand requirements and acceptance criteria
§ Working with Software Engineering teams to discover underlying design gaps and/or technical gaps against associated risks e.g. security, performance, usability, etc.
Advocating Agile practices, to Software Engineering teams and other stakeholders to achieve increasingly Agile
