Product Owner Learning Objectives: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 106: | Line 106: | ||
|- | |- | ||
|1.1 | |1.1 | ||
| | |Fundamentals of the Product Owner Role | ||
|3 | |3 organizational contexts that affect the approach to the Product Owner role | ||
|[[Scrum Roles]] | |[[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 | |||
|use at least one technique to provide transparency to stakeholders on progress toward goals | |||
|[[]] | |||
|- | |||
|1.4 | |||
|Working with Stakeholders | |||
|list at least three techniques to engage stakeholders to gather information or insights | |||
|[[]] | |||
|- | |||
|1.5 | |||
|Product Ownership with Multiple Teams | |||
|identify at least two ways of overcoming the challenges of being a Product Owner for multiple teams | |||
|[[]] | |||
|- | |||
|2.1 | |||
|Describing Purpose and Strategy | |||
|practice the creation of a product vision. | |||
|[[]] | |||
|- | |||
|2.2 | |||
|Describing Purpose and Strategy | |||
|list the components of a product plan or forecast with stakeholders | |||
|[[]] | |||
|- | |||
|2.3 | |||
|Describing Purpose and Strategy | |||
|describe how to plan a product release | |||
|[[]] | |||
|- | |||
|2.4 | |||
|Describing Purpose and Strategy | |||
|explain at least two approaches to identify small, valuable, and releasable Product Increments | |||
|[[]] | |||
|- | |||
|3.1 | |||
|Understanding Customers and Users | |||
|describe why a Product Owner performs discovery and validation work | |||
|[[]] | |||
|- | |||
|3.2 | |||
|Understanding Customers and Users | |||
|illustrate at least one approach for segmenting customers and users | |||
|[[]] | |||
|- | |||
|3.3 | |||
|Understanding Customers and Users | |||
|practice at least one technique to prioritise between conflicting customer (or user) needs | |||
|[[]] | |||
|- | |||
|3.4 | |||
|Understanding Customers and Users | |||
|describe at least three aspects of product discovery and identify how each contributes to successful product outcomes | |||
|[[]] | |||
|- | |||
|3.5 | |||
|Understanding Customers and Users | |||
|use one technique to describe users and customers: their jobs, activities, pains, and gains | |||
|[[]] | |||
|- | |||
|3.6 | |||
|Understanding Customers and Users | |||
|list at least three approaches to connect the Development Team directly to customers and users | |||
|[[]] | |||
|- | |||
|3.7 | |||
|Understanding Customers and Users | |||
|describe at least three benefits of Development Team direct interactions | |||
|[[]] | |||
|- | |||
|4.1 | |||
|Validating Product Assumptions | |||
|describe how Scrum supports validating product assumptions | |||
|[[]] | |||
|- | |||
|4.2 | |||
|Validating Product Assumptions | |||
|describe at least one approach to validate product assumptions by their cost and quality of learning | |||
|[[]] | |||
|- | |||
|5.1 | |||
|Differentiating Outcome and Output | |||
|describe the relationship between outcome and output | |||
|[[]] | |||
|- | |||
|5.2 | |||
|Differentiating Outcome and Output | |||
|describe at least three attributes of a Product Backlog item that help assess maximizing outcome | |||
|[[]] | |||
|- | |||
|5.3 | |||
|Defining Value | |||
|define value and list at least two techniques to measure value | |||
|[[]] | |||
|- | |||
|5.4 | |||
|Defining Value | |||
|describe value from the perspective of at least three different stakeholder groups | |||
|[[]] | |||
|- | |||
|5.5 | |||
|Defining Value | |||
|list at least three terms related to product economics | |||
|[[]] | |||
|- | |||
|5.6 | |||
|Creating and Refining Items | |||
|create at least one Product Backlog item that includes description of desired outcome and value | |||
|[[]] | |||
|- | |||
|5.7 | |||
|Creating and Refining Items | |||
|describe at least one approach to Product Backlog Refinement | |||
|[[]] | |||
|- | |||
|5.8 | |||
|Creating and Refining Items | |||
|describe at least three criteria for ordering the Product Backlog | |||
|[[]] | |||
|} | |} | ||
Revision as of 00:29, 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 | use at least one technique to provide transparency to stakeholders on progress toward goals | [[]] |
1.4 | Working with Stakeholders | list at least three techniques to engage stakeholders to gather information or insights | [[]] |
1.5 | Product Ownership with Multiple Teams | identify at least two ways of overcoming the challenges of being a Product Owner for multiple teams | [[]] |
2.1 | Describing Purpose and Strategy | practice the creation of a product vision. | [[]] |
2.2 | Describing Purpose and Strategy | list the components of a product plan or forecast with stakeholders | [[]] |
2.3 | Describing Purpose and Strategy | describe how to plan a product release | [[]] |
2.4 | Describing Purpose and Strategy | explain at least two approaches to identify small, valuable, and releasable Product Increments | [[]] |
3.1 | Understanding Customers and Users | describe why a Product Owner performs discovery and validation work | [[]] |
3.2 | Understanding Customers and Users | illustrate at least one approach for segmenting customers and users | [[]] |
3.3 | Understanding Customers and Users | practice at least one technique to prioritise between conflicting customer (or user) needs | [[]] |
3.4 | Understanding Customers and Users | describe at least three aspects of product discovery and identify how each contributes to successful product outcomes | [[]] |
3.5 | Understanding Customers and Users | use one technique to describe users and customers: their jobs, activities, pains, and gains | [[]] |
3.6 | Understanding Customers and Users | list at least three approaches to connect the Development Team directly to customers and users | [[]] |
3.7 | Understanding Customers and Users | describe at least three benefits of Development Team direct interactions | [[]] |
4.1 | Validating Product Assumptions | describe how Scrum supports validating product assumptions | [[]] |
4.2 | Validating Product Assumptions | describe at least one approach to validate product assumptions by their cost and quality of learning | [[]] |
5.1 | Differentiating Outcome and Output | describe the relationship between outcome and output | [[]] |
5.2 | Differentiating Outcome and Output | describe at least three attributes of a Product Backlog item that help assess maximizing outcome | [[]] |
5.3 | Defining Value | define value and list at least two techniques to measure value | [[]] |
5.4 | Defining Value | describe value from the perspective of at least three different stakeholder groups | [[]] |
5.5 | Defining Value | list at least three terms related to product economics | [[]] |
5.6 | Creating and Refining Items | create at least one Product Backlog item that includes description of desired outcome and value | [[]] |
5.7 | Creating and Refining Items | describe at least one approach to Product Backlog Refinement | [[]] |
5.8 | Creating and Refining Items | describe at least three criteria for ordering the Product Backlog | [[]] |
See Also
- Product Owner Coaching Syllabus
- Product Owner Workshop Syllabus
- Product Owner
- Scrum Master Coaching Syllabus
- Scrum Master Workshop Syllabus
- Scrum Framework
- Scrum Master