Proxy Product Owner

Role Summary: The Proxy Product Owner (PPO) is the entry point for all external partners/stakeholders of IT Market Services (ITMS) for new ideas/initiatives, change requests. The PPO's role is to

• User their expertise to support ITMS stakeholders (business lines, operational teams, transversal IT, internal ITMS leads) in structuring and/or co-designing their requirements.
• Work closely with ITMS teams to design solutions to the requirements.

Responsibilities: 

Idea Phase: 

Support ITMS stakeholders to structure and/or co-design their requirements and challenge them if necessary. 

Align with ITMS partners to confirm the maturity/readiness of functional and non-functional requirements. 

Ensure that a priority has been assigned to ITMS partners' ideas. 

Ensure that ITMS partners have provided a strict deadline if applicable. 

Gather size estimates for the main impacted applications. 

Detail assumptions for calculating the size. 

Align the provisional request gate with internal ITMS teams and partners. 

Provide key information by regularly interacting with the ITMS roadmap team. 

Store all documentation in the "Initiatives" folder of the project in the project SharePoint. 

Pre-assessement Phase: 

Verify that all stakeholders have been onboarded by the PO. 

Coordinate ITMS experts and act as the bridge between ITMS and partners on the solution. 

Build and deliver the scoping note ensuring that all requirements have been addressed. 

Collect high-level estimates. 

Ensure the review and agreement on the scoping note by ITMS and external stakeholders. 

Integrate BA, Architecture, PM, and ITMS managers through an ITMS project kick-off to ensure understanding of the initiative, requirements, and approved solution to be implemented. 

Store all documentation in the project SharePoint in the Initiative folder. 

Validate the request gate and provide the date to the ITMS roadmap team. 

Study and Execution Phases: 

Assist ITMS teams in case of questions or doubts. 

Remain the ITMS contact for external stakeholders in case of additional requirements or questions about the solution. 

PPO Practice Principles: 

Act as a team player. Help and ask for help. Support, share, and care positively. 

Scoping notes and high-level estimates are all done according to the model and stored in the "Initiative" folder in SharePoint. 

All requirements are addressed in the deliverables. 

All comments in the scoping notes are responded to. 

Out-of-scope sections and high-level estimate assumptions are well documented. 

Dependencies between projects and external constraints are well documented and shared. 

Ensure that all business requests start with requirements and not pre-assumed solutions. 

Evaluate the business value of each request and ensure that the business case is validated. 

Jira idea tickets are systematically created and updated at all times. 

All scope changes are duly tracked, reported, and scoping notes/high-level estimates updated and versioned. 

Share relevant topics internally with other PPOs. 

Participate in the improvement, application, and documentation of PPO practice. 

Ensure that at least one PPO is present at the business priority review meeting. 

Ensure that the roadmap team is updated with relevant updates (dates, workloads, readiness).