An interactive product leadership-focused workshop providing specific skills and competencies required to effectively guide agile products. Topics include Scrum roles and responsibilities, the Product Owner Team, balancing stakeholder needs, Scrum Product Management and the product backlog, prioritization strategies, strategic and tactical product balance, incremental release strategies, measuring value, and engaging with the Scrum team.

This workshop includes a 1 year membership into the Scrum Alliance and a Certified Scrum Product Owner (CSPO) designation. This is a two-day workshop, or as one-day extension on the Scrum Team Workshop. This workshop covers the following disciplines:

Â	Balancing Stakeholder Needs A Product Owner is the single voice for the product representing many diverse stakeholders and end users who may have varying needs and wants. Balancing these needs, understanding and maintaining their expectations, and determining the right mix of functionality is critical in maximizing the company’s investment. A Product Owner sets the vision and makes sure that vision is aligned with and communicated to all of the stakeholders.
Â	Defining the Product Backlog A Product Owner drives the Scrum process of incremental development, delivery and feedback through the Product Backlog. It is one of the most critical tools to enable Scrum. A Product Owner will identify solutions, decompose into small units of value, articulate success for each unit and prioritize them based on the value they represent to their end users and stakeholders. User Stories with acceptance criteria are the primary items in the backlog, however, working with risk, uncertainty, technical debt, defects and non-functional requirements make this a difficult assignment.
Â	Engaging with the Scrum Team A Product Owner must stay focused on both the product vision and the progress towards that vision. To make sure that the stakeholders needs are being addressed correctly, the Product Owner must work closely with the Scrum Team. Engaging them in release planning to gain their ownership and buy-in to the release; working a step ahead of the team to keep their sprints properly focused on the most important work; and meeting with them each sprint to drill down into the details of the solutions and insure that they are meeting users’ expectations are some of the key responsibilities of the Product Owner.
Â	Releasing the Product A Product Owner must ultimately deliver solutions to their user constituents. Scrum leverages early and frequent feedback through each sprint, and also through frequent releases. A Product Owner starts with aligning the stakeholder community on a common vision then building shared ownership with the Scrum Team through release planning. Finally, a Product Owner must keep the progress, process and expectations transparent through shared sprint reviews.