Product Owner Coaching Syllabus: Difference between revisions

From AgileMe
Jump to navigation Jump to search
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 31: Line 31:
* F1.4 - 3 Pillars of Empirical Process Control
* F1.4 - 3 Pillars of Empirical Process Control
* F1.5 - Traditional vs Empirical Product Planning
* F1.5 - Traditional vs Empirical Product Planning
|-
|[[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
|-
|-
|[[Sprints]]
|[[Sprints]]
Line 60: Line 53:
* F3.2 - 5 Scrum Events
* F3.2 - 5 Scrum Events
|-
|-
|[[Sprint Review]]
|
|
* F3.1 - Timeboxing
* [[Sprint Review]]
* F3.2 - 5 Scrum Events
* [[Sprint Retrospective]]
|-
|[[Sprint Retrospective]]
|
|
* F3.1 - Timeboxing
* F3.1 - Timeboxing
* F3.2 - 5 Scrum Events
* F3.2 - 5 Scrum Events
|-
|[[Definition of Done]]
|
* F4.2 - Definition of Done
|-
|-
|[[Scrum Artefacts]]
|[[Scrum Artefacts]]
Line 78: Line 64:
* F4.1 - 3 Scrum Artefacts
* F4.1 - 3 Scrum Artefacts
|-
|-
|[[Working With Stakeholders]]
|[[Iterative vs. Incremental]]
|
|
* 1.3 - 1 technique to provide progress toward goals
* F1.7 - Iterative and Incremental Approaches
* 1.4 - 3 techniques to engage, gather information and derive insights
* 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
|-
|-
|[[Agile Estimation]]
|
*[[Purpose & Strategy]]
*[[Strategic Awareness]]
*[[Empathy Mapping]]
*[[Impact Mapping]]
*[[Story Mapping]]
*[[Working With The Product Backlog]]
*[[Affinity Estimation]]
*[[Value Mapping]]
*[[Kano Analysis]]
|
|
* 1.3 - 1 technique to provide progress toward goals
* 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
|-
|
[[Purpose & Strategy]]
[[Impact Mapping]]
|
* 2.1 - 1 way of creating a product vision
* 2.1 - 1 way of creating a product vision
* 2.2 - 1 way to create a product plan or forecast with stakeholders
* 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
|-
|-
|
|
[[Release Planning]]
*[[Release Planning]]
[[Release Strategy]]
*[[Release Strategy]]
[[Strategic Awareness]]
*[[Backlog Strategy Archetypes]]
[[Evolutionary Strategy]]
*[[Evolutionary Strategy]]
|
|
* 2.2 - 1 way to create a product plan or forecast with stakeholders
* 2.2 - 1 way to create a product plan or forecast with stakeholders
Line 109: Line 103:
* 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments
* 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments
|-
|-
|[[Story Mapping]]
|
|
* 2.3 - 1 way to plan a product release
*[[Customer Research]]
* 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments
*[[Collaboration Frameworks]]
|-
*[[Testing Assumptions]]
|[[Backlog Strategy Archetypes]]
*[[Design Sprint]]
|
|
* 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
* 5.6 - Create a Product Backlog Item that includes description of desired outcome and value
* 4.1 - How Scrum supports validating product assumptions
* 4.2 - 1 approach to validate product assumptions by their cost and quality of learning
|-
|-
|[[Customer Research]]
|[[Working With Stakeholders]]
|
|
* 3.1 - Why a Product Owner performs discovery and validation work
* 1.3 - 1 technique to provide progress toward goals
* 3.2 - 1 approach for segmenting customers and users
* 1.4 - 3 techniques to engage, gather information and derive insights
|-
|-
|[[Collaboration Frameworks]]
|[[Feature Debt]]
|
|
* 3.3 - 1 technique to prioritise between conflicting customer (or user) needs
* 5.1 - describe the relationship between outcome and output
|-
|-
|[[Design Sprint]]
|[[Definition of Done]]
|
|
* 3.4 - 3 aspects of product discovery and how each contributes to successful product outcomes
* F4.2 - Definition of Done
* 3.6 - 3 approaches to connect the Development Team directly to customers and users
|-
|-
|[[Empathy Mapping]]
|[[Agile Estimation]]
|
|
* 3.5 - 1 technique to describe users and customers: their jobs, activities, pains, and gains
* 1.3 - 1 technique to provide progress toward goals
* 5.5 - 3 terms related to product economics
|-
|-
|[[Testing Assumptions]]
|[[Scaling Scrum]]
|
|
* 4.1 - How Scrum supports validating product assumptions
*1.5 - 2 ways of overcoming challenges when working with multiple teams
* 4.2 - 1 approach to validate product assumptions by their cost and quality of learning
|-
|[[Feature Debt]]
|
* 5.1 - describe the relationship between outcome and output
|-
|[[Working With The Product Backlog]]
|
* 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
|}
|}


Latest revision as of 00:23, 27 October 2022


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

Retrieved from "https://agileme.wiki/wiki/index.php?title=Product_Owner_Coaching_Syllabus&oldid=1611"