Product Owner Learning Objectives: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 130: | Line 130: | ||
|Product Ownership with Multiple Teams | |Product Ownership with Multiple Teams | ||
|2 ways of overcoming challenges when working with multiple teams | |2 ways of overcoming challenges when working with multiple teams | ||
|[[]] | |[[Scaling Scrum]] | ||
|- | |- | ||
|2.1 | |2.1 | ||
|Describing Purpose and Strategy | |Describing Purpose and Strategy | ||
|1 way of creating a product vision | |1 way of creating a product vision | ||
|[[]] | |[[Purpose & Strategy]] | ||
|- | |- | ||
|2.2 | |2.2 | ||
| Line 141: | Line 141: | ||
|1 way to create a product plan or forecast with stakeholders | |1 way to create a product plan or forecast with stakeholders | ||
| | | | ||
*[[Purpose & Strategy]] | |||
*[[Release Planning]] | *[[Release Planning]] | ||
*[[Release Strategy]] | *[[Release Strategy]] | ||
*[[Iterative vs. Incremental]] | |||
*[[Strategic Awareness]] | |||
*[[Evolutionary Strategy]] | |||
|- | |- | ||
|2.3 | |2.3 | ||
| Line 151: | Line 155: | ||
*[[Story Mapping]] | *[[Story Mapping]] | ||
*[[Release Strategy]] | *[[Release Strategy]] | ||
*[[Iterative vs. Incremental]] | |||
|- | |- | ||
|2.4 | |2.4 | ||
| Line 158: | Line 163: | ||
*[[Story Mapping]] | *[[Story Mapping]] | ||
*[[Release Strategy]] | *[[Release Strategy]] | ||
*[[Iterative vs. Incremental]] | |||
|- | |- | ||
|3.1 | |3.1 | ||
| Line 172: | Line 178: | ||
|Understanding Customers and Users | |Understanding Customers and Users | ||
|1 technique to prioritise between conflicting customer (or user) needs | |1 technique to prioritise between conflicting customer (or user) needs | ||
|[[]] | |[[Collaboration Frameworks]] | ||
|- | |- | ||
|3.4 | |3.4 | ||
| Line 197: | Line 203: | ||
|Validating Product Assumptions | |Validating Product Assumptions | ||
|How Scrum supports validating product assumptions | |How Scrum supports validating product assumptions | ||
|[[]] | |[[Testing Assumptions]] | ||
|- | |- | ||
|4.2 | |4.2 | ||
|Validating Product Assumptions | |Validating Product Assumptions | ||
|1 approach to validate product assumptions by their cost and quality of learning | |1 approach to validate product assumptions by their cost and quality of learning | ||
|[[]] | |[[Testing Assumptions]] | ||
|- | |- | ||
|5.1 | |5.1 | ||
| Line 212: | Line 218: | ||
|Differentiating Outcome and Output | |Differentiating Outcome and Output | ||
|3 attributes of a Product Backlog item that help assess maximising outcome | |3 attributes of a Product Backlog item that help assess maximising outcome | ||
|[[]] | |[[Working With The Product Backlog]] | ||
|- | |- | ||
|5.3 | |5.3 | ||
|Defining Value | |Defining Value | ||
|2 techniques to measure value | |2 techniques to measure value | ||
|[[]] | |[[Working With The Product Backlog]] | ||
|- | |- | ||
|5.4 | |5.4 | ||
|Defining Value | |Defining Value | ||
|Value from 3 different stakeholder groups | |Value from 3 different stakeholder groups | ||
|[[]] | |[[Working With The Product Backlog]] | ||
|- | |- | ||
|5.5 | |5.5 | ||
Revision as of 01:18, 15 March 2022
Below are the learning objectives based upon the Scrum Alliance learning objectives for coaching Product Owners.
Foundation Learning Objectives
| ID | Classification | Learning Objective | Session Mapping |
|---|---|---|---|
| F1.1 | Scrum Theory | Scrum and Agile Manifesto | Agile Manifesto |
| F1.2 | Scrum Theory | Scrum and its Purpose | Scrum Framework |
| F1.3 | Scrum Theory | 5 Scrum Values | 5 Scrum Values |
| F1.4 | Scrum Theory | 3 Pillars of Empirical Process Control | Empirical vs Predictive Control Processes |
| F1.5 | Scrum Theory | Traditional vs Empirical Product Planning | Empirical vs Predictive Control Processes |
| F1.6 | Scrum Theory | Scrum in its Entirety | Scrum Framework |
| F1.7 | Scrum Theory | Iterative and Incremental Approaches | Iterative vs. Incremental |
| F2.1 | Scrum Roles | How Scrum Roles Interact | Scrum Roles |
| F2.2 | Scrum Roles | Cross Functional and Self Organising Teams | Scrum Roles |
| F3.1 | Scrum Events | Timeboxing | |
| F3.2 | Scrum Events | 5 Scrum Events | |
| F4.1 | Scrum Artefacts | 3 Scrum Artefacts | |
| F4.2 | Scrum Artefacts | Definition of Done | Definition of Done |
| F4.3 | Scrum Artefacts | Product Backlog Refinement | Sprint Planning & Product Backlog Refinement |
| F4.4 | Scrum Events and Artefacts | 3 Activities During Product Backlog Refinement | Sprint Planning & Product Backlog Refinement |
Product Owner Learning Objectives
| ID | Classification | Learning Objective | Session Mapping |
|---|---|---|---|
| 1.1 | Fundamentals of the Product Owner Role | 3 organizational contexts that affect the approach to the Product Owner role | Scrum Roles |
| 1.2 | Fundamentals of the Product Owner Role | 3 anti-patterns that might exist for Product Owners | Scrum Roles |
| 1.3 | Working with Stakeholders | 1 technique to provide progress toward goals | |
| 1.4 | Working with Stakeholders | 3 techniques to engage, gather information and derive insights | Working With Stakeholders |
| 1.5 | Product Ownership with Multiple Teams | 2 ways of overcoming challenges when working with multiple teams | Scaling Scrum |
| 2.1 | Describing Purpose and Strategy | 1 way of creating a product vision | Purpose & Strategy |
| 2.2 | Describing Purpose and Strategy | 1 way to create a product plan or forecast with stakeholders | |
| 2.3 | Describing Purpose and Strategy | 1 way to plan a product release | |
| 2.4 | Describing Purpose and Strategy | 2 approaches to identify small, valuable, and releasable Product Increments | |
| 3.1 | Understanding Customers and Users | Why a Product Owner performs discovery and validation work | Customer Research |
| 3.2 | Understanding Customers and Users | 1 approach for segmenting customers and users | Customer Research |
| 3.3 | Understanding Customers and Users | 1 technique to prioritise between conflicting customer (or user) needs | Collaboration Frameworks |
| 3.4 | Understanding Customers and Users | 3 aspects of product discovery and how each contributes to successful product outcomes | [[]] |
| 3.5 | Understanding Customers and Users | 1 technique to describe users and customers: their jobs, activities, pains, and gains | Empathy Mapping |
| 3.6 | Understanding Customers and Users | 3 approaches to connect the Development Team directly to customers and users | [[]] |
| 3.7 | Understanding Customers and Users | 3 benefits of Development Team direct interactions | [[]] |
| 4.1 | Validating Product Assumptions | How Scrum supports validating product assumptions | Testing Assumptions |
| 4.2 | Validating Product Assumptions | 1 approach to validate product assumptions by their cost and quality of learning | Testing Assumptions |
| 5.1 | Differentiating Outcome and Output | describe the relationship between outcome and output | [[]] |
| 5.2 | Differentiating Outcome and Output | 3 attributes of a Product Backlog item that help assess maximising outcome | Working With The Product Backlog |
| 5.3 | Defining Value | 2 techniques to measure value | Working With The Product Backlog |
| 5.4 | Defining Value | Value from 3 different stakeholder groups | Working With The Product Backlog |
| 5.5 | Defining Value | 3 terms related to product economics | Agile Estimation |
| 5.6 | Creating and Refining Items | Create a Product Backlog Item that includes description of desired outcome and value | Product Backlog Refinement |
| 5.7 | Creating and Refining Items | 1 approach to Product Backlog Refinement | Product Backlog Refinement |
| 5.8 | Creating and Refining Items | 3 criteria for ordering the Product Backlog | Product Backlog Refinement |
See Also
- Product Owner Coaching Syllabus
- Product Owner Workshop Syllabus
- Product Owner
- Scrum Master Coaching Syllabus
- Scrum Master Workshop Syllabus
- Scrum Framework
- Scrum Master