•  Ensuring that overall product strategy aligns with threat landscape, control objectives, and efficiency goals
o  The PPO will own and drive the budget(s) and assist with creation of business case(s) for its Products
o  Overseeing product definition and value proposition, product offering and roadmap, client engagement, financial management, service measurement, and continuous improvement for the end-to-end lifecycle of the product.
o Setting strategic direction for the product portfolio
o Research and product development
o  Demonstrating a strong understanding of the importance of end-to-end software development which 
will include working in Agile frameworks
o Enforcement of a fail-fast culture

•  Collaborative preparation and participation in Program Increment (PI) Planning
o  As a member of the extended Product Management team, the PPO is responsible for the refinement of the program backlog and prep for PI planning. The PPO is the most significant role in planning the event itself from a Platform perspective. Before the planning event, the PPO updates the team backlog and typically reviews and contributes to the program vision, roadmap, and content presentations.

o  During the event, the PPO is involved with story definition, providing the clarifications necessary to assist the team with their story estimates and sequencing. The PPO also drafts the team’s specific objectives for the upcoming PI.

 

•  Efficient iteration execution
o  Maintaining the team backlog – With input from the Solution Architect, Head of E-money and other 
stakeholders, the PPO 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, and other team dependencies determined in the PI planning meeting and refined during the PI.
o  Iteration Planning – The PPO reviews and reprioritizes the backlog as part of the prep work for Iteration Planning, including coordination of dependencies with other PPOs. During the iteration planning meeting, the PPO is the primary source for story detail and priorities and has the responsibility of accepting the final iteration plan.
o  Just-in-time story elaboration – Most backlog items are elaborated into user stories for implementation. This may happen before the iteration, during iteration planning, or during the iteration. While any team member can write stories and acceptance criteria, the PPO has the primary responsibility for maintaining the flow.
o  Apply Behavior-Driven Development (BDD) – PPOs collaborate with their team to details stories 
with acceptance criteria and acceptance tests.
o  Accepting stories – The PPO is the only team member who can accept stories as done. This includes validation that the story meets acceptance criteria and has the appropriate, persistent acceptance tests, and that it otherwise complies its Definition of Done (DoD). In so doing, the PPO also assures a level of quality, focusing primarily on fitness for use.
o  Understand enabler work – While PPOs are not expected to drive technological decisions, they are supposed to understand the scope of the upcoming enabler work and to collaborate with the Solution Architect and System Engineering to assist with decision-making and sequencing of the critical technological infrastructure that will host the new business functionality.
o  Participate in team demo and retrospective – As the person responsible for requirements, PPOs have an essential role in the team demo, reviewing and accepting stories. They also participate in the Iteration Retrospective, where the teams gather to improve their processes and are active in the Agile Release Train’s (ART’s) Inspect and Adapt (I&A) workshop.
o  Ensures that Agile teams deliver frequent, reliable, and continuous value-added solutions in each iteration throughout the PI. During each PI, the PPO coordinates dependencies with other PPOs. This often occurs in weekly PPO sync meetings.

•  Efficient program execution
o  Iterations and Agile teams serve a larger purpose; the frequent, reliability, and continuous release of value-added solutions. During each PI, the PPO coordinates dependencies with other PPOs. This often occurs in weekly PPO sync meetings.
o  The PO also has an instrumental role in producing the System Demo for Platform stakeholders.

 

•  Participating in the Inspect and Adapt workshop
o  Teams address their larger impediments in the I&A workshop. There, the PPO works across teams to define and implement improvement stories that will increase the velocity and quality of the program.
o  The PI system demo is part of the I&A workshop. The PPO has an instrumental role in producing the PI system demo for program stakeholders.