Advanced Scrum Product Owner (A-CSPO) Training Program

Examining the Product Owner Role

• Analyze how you as a Product Owner help the organization realize value through delivering product solutions that delight customers and users within the constraints of technical feasibility, organizational context, and regulatory requirements

• Discuss the skills and capabilities needed for a Product Owner to collaborate as a member of a cross-functional Scrum Team in order to create successful products

• Explain the role of the Product Owner and at least three of the benets of mastering the role.

• Illustrate why Scrum and product ownership is important for you.

Working with Stakeholders

• Identify at least four major stakeholder groups and describe how a Product Owner may interact with them during the development cycles (e.g., customers, sponsors, users, service, team members, customer support, training, governance (audit, compliance, risk), managers, infrastructure, security, architecture, etc.).

• Discuss three questions that will help you identify that you are working with the key stakeholders you need. Example questions: Can you clearly identify what you want from the stakeholder Can you exist without or easily replace the stakeholder

• Using two concrete examples, recognize when the Product Owner should not act as the facilitator for the stakeholders (i.e., emotional conict, impediment to creativity, lack of facilitation skills, too invested in the outcome of the discussion to be impartial

• Demonstrate at least three facilitative listening techniques (e.g., paraphrasing, mirroring, making space, stacking, etc.).

• List at least three alternatives to open discussion (e.g., structured go-arounds, individual writing, listing ideas, dialogue in pairs or small groups, etc.) and demonstrate the use of at least one of them

• Identify at least three indicators when a group is engaged in divergent thinking and at least three indicators where a group is engaged in convergent thinkin

• Identify at least three challenges of integrating multiple frames of reference.

• Describe at least three ways a group of stakeholders could reach their nal decision (e.g., st of ve, decider protocol, majority vote, etc.)

• Practice a product backlog ordering session with multiple stakeholders

• Debate the importance of various stakeholders participating in sprint review meetings (e.g., CEO, external customer, head of engineering, other teams, et

• Demonstrate at least three techniques for engaging with stakeholders on a regular basis. For example, product backlog renement, roadmapping, release planning, qualitative market research, Sprint Reviews, observe Daily Scrums, etc.

Working with the Development Team

• List at least ve practices (e.g., from extreme programming: test-driven development, pair programming, continuous integration, collective code ownership, refactoring) that will help Scrum Teams deliver a high-quality product increment and reduce technical debt each sprint.

Product Ownership with Multiple Teams

• List at least three scaling frameworks or approaches (LeSS, DAD, Enterprise Scrum, etc.)

• Describe how at least two large-scale participatory meeting formats (Open Space, World Cafe, Review Bazaar) might be adapted to scale Scrum meetings

• Illustrate at least three techniques for visualizing, managing, or reducing dependencies between teams.

• Describe at least three benefits and drawbacks of feature teams and component teams.