Product Owner Coaching Syllabus

From AgileMe
Jump to navigation Jump to search


Here is a suggested coaching syllabus to cover the Product Owner Learning Objectives based upon the Scrum Alliance learning objectives.

Session Learning Objective Mapping
Scrum Framework
  • F1.2 - Scrum and its Purpose
  • F1.6 - Scrum in its Entirety
Scrum Roles
  • F2.1 - How Scrum Roles Interact
  • F2.2 - Cross Functional and Self Organising Teams
  • 1.1 - 3 organizational contexts that affect the approach to the Product Owner role
  • 1.2 - 3 anti-patterns that might exist for Product Owners
Agile Manifesto
  • F1.1 - Scrum and Agile Manifesto
5 Scrum Values
  • F1.3 - 5 Scrum Values
Empirical vs Predictive Control Processes
  • F1.4 - 3 Pillars of Empirical Process Control
  • F1.5 - Traditional vs Empirical Product Planning
Sprints
  • F3.1 - Timeboxing
  • F3.2 - 5 Scrum Events
Sprint Planning & Product Backlog Refinement
  • F3.1 - Timeboxing
  • F3.2 - 5 Scrum Events
  • F4.3 - Product Backlog Refinement
  • F4.4 - 3 Activities During Product Backlog Refinement
  • 3.7 - 3 benefits of Development Team direct interactions
  • 5.6 - Create a Product Backlog Item that includes description of desired outcome and value
  • 5.7 - 1 approach to Product Backlog Refinement
  • 5.8 - 3 criteria for ordering the Product Backlog
Daily Scrum
  • F3.1 - Timeboxing
  • F3.2 - 5 Scrum Events
  • F3.1 - Timeboxing
  • F3.2 - 5 Scrum Events
Scrum Artefacts
  • F4.1 - 3 Scrum Artefacts
Iterative vs. Incremental
  • F1.7 - Iterative and Incremental Approaches
  • 2.2 - 1 way to create a product plan or forecast with stakeholders
  • 2.3 - 1 way to plan a product release
  • 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments
  • 1.3 - 1 technique to provide progress toward goals
  • 2.1 - 1 way of creating a product vision
  • 2.2 - 1 way to create a product plan or forecast with stakeholders
  • 3.1 - Why a Product Owner performs discovery and validation work
  • 3.2 - 1 approach for segmenting customers and users
  • 3.3 - 1 technique to prioritise between conflicting customer (or user) needs
  • 3.5 - 1 technique to describe users and customers: their jobs, activities, pains, and gains
  • 5.2 - 3 attributes of a Product Backlog item that help assess maximising outcome
  • 5.3 - 2 techniques to measure value
  • 5.4 - Value from 3 different stakeholder groups
  • 2.2 - 1 way to create a product plan or forecast with stakeholders
  • 2.3 - 1 way to plan a product release
  • 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments
  • 3.6 - 3 approaches to connect the Development Team directly to customers and users
  • 4.1 - How Scrum supports validating product assumptions
  • 4.2 - 1 approach to validate product assumptions by their cost and quality of learning
Working With Stakeholders
  • 1.3 - 1 technique to provide progress toward goals
  • 1.4 - 3 techniques to engage, gather information and derive insights
Feature Debt
  • 5.1 - describe the relationship between outcome and output
Definition of Done
  • F4.2 - Definition of Done
Agile Estimation
  • 1.3 - 1 technique to provide progress toward goals
  • 5.5 - 3 terms related to product economics
Scaling Scrum
  • 1.5 - 2 ways of overcoming challenges when working with multiple teams

See Also

References