0% found this document useful (0 votes)
6 views2 pages

Product Owner Syllabus

Download as docx, pdf, or txt
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 2

Scrum Basics

 Understand the Scrum Flow, the core components of the Scrum framework, and the Scrum vocabulary
 Understand the principles/legs of empirical process control
 Understand the work culture Scrum creates

Roles & Responsibilities

 Understand the scope of the Product Owner, ScrumMaster and the team role in detail
 Understand why there is no project manager and no agile product manager

Product Vision

 Understand the importance of having the product vision as an overarching goal galvanizing the entire
Scrum team
 Understand the desirable qualities of the vision and how it can be shaped
 Understand the importance of carrying out just enough prep work
 Understand the relationship between vision and product roadmap

Estimating

 Understand the different estimation levels in Scrum


 Understand that the accuracy of an estimate is more important than the precision of the estimate
 Understand that estimates of size and duration can be done separately
 Understand the impact of pressuring team members to provide low estimates
 Understand the difference between estimating and committing

Product Backlog

 Understand what the product backlog is, and what it is not


 Understand product backlog grooming

Prioritizing

 Understand the importance and benefits of prioritizing the product backlog


 Understand the implications of saying everything is mandatory
 Understand who should have input into prioritization decisions
 Understand that proper prioritization of a product backlog is based on multiple factors
 Understand and know how to apply formal approaches to prioritizing (i.e. beyond just ‘gut feel’ or
intuition)
 Understand how much latitude to give a team in adjusting the sequence of work

Release Management

 Understand the goals and how-tos of release planning


 Understand that planning is adaptive, iterative and collaborative
 Understand why quality is frozen and the concept of technical debt
 Understand why software should be released early and frequently
 Understand and measure a velocity
 Understand release burndown charts
 Understand how a release plan can help predict the future

Sprints

 Understand the product owner’s role in Scrum meetings, and how the Product Owner and Team
collaborate
 Understand why sprints are timeboxed and protected
 Understand the concept of sustainable pace
 Understand team commitment

You might also like