The Product Owner is responsible for ensuring clear communication of product or service functionality requirements to the Scrum Team, defining Acceptance Criteria, and ensuring those criteria are met. The Product Owner must always maintain a dual view. He must understand and support the needs and interests of all stakeholders, while also understanding the needs and workings of the Scrum Team.

The final exam confirms that candidates have acquired practical knowledge of Scrum to play the role of Product Owner in a SCRUM context.

● Agile and Scrum Overview

○ What is Agile?

○ Why use Agile?

○ The Agile Manifesto

○ Principles of the Agile Manifesto ○ Agile Methods

○ Other Agile Methods ○ Scrum Overview ○ Scrum Summary

● Scrum Roles

○ The Product Owner

○ The Scrum Team

○ The Scrum Master

○ Advantages of Cross-functional Teams

● Planning in Scrum

○ Scrum Flow

○ Requirements in Scrum

○ Prioritizing the Product Backlog

○ Adaptive Project Management

○ Scrum Planning

○ User Stories

○ The Concept of Persona

○ Acceptance Criteria

○ Generic Done Criteria

○ Criteria for a Good User Story

○ Estimation

○ Importance of Value

○ Risk Burndown Graphics

○ Scrum Board 

● Sprint Planning

○ Sprints (from Product Owner's point of view)

○ Sprint Planning Meeting

○ Planning Game ○ Task Estimation

○ The Sprint Backlog

● Implementation of Scrum

○ Daily Stand-up Meeting

○ Sprint Review Meeting

○ Sprint Retrospective Meeting

○ Product Backlog Grooming

● Scrum for Large Projects

○ Scrum for Large Projects

○ The Chief Product Owner

○ Distributed teams in Scrum

○ Transition to Scrum

○ Mapping Traditional Roles to Scrum

○ Maintaining Stakeholder Involvement