Product Owner Coaching Syllabus: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 104: | Line 104: | ||
*[[Strategic Awareness]] | *[[Strategic Awareness]] | ||
*[[Evolutionary Strategy]] | *[[Evolutionary Strategy]] | ||
*[[Story Mapping]] | |||
| | | | ||
* 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 | ||
* 2.3 - 1 way to plan a product release | * 2.3 - 1 way to plan a product release | ||
* 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments | * 2.4 - 2 approaches to identify small, valuable, and releasable Product Increments | ||
| Line 119: | Line 115: | ||
* 5.6 - Create a Product Backlog Item that includes description of desired outcome and value | * 5.6 - Create a Product Backlog Item that includes description of desired outcome and value | ||
|- | |- | ||
|[[Customer Research]] | | | ||
*[[Customer Research]] | |||
*[[Collaboration Frameworks]] | |||
*[[Empathy Mapping]] | |||
| | | | ||
* 3.1 - Why a Product Owner performs discovery and validation work | * 3.1 - Why a Product Owner performs discovery and validation work | ||
* 3.2 - 1 approach for segmenting customers and users | * 3.2 - 1 approach for segmenting customers and users | ||
* 3.3 - 1 technique to prioritise between conflicting customer (or user) needs | * 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 | |||
|- | |- | ||
|[[Design Sprint]] | |[[Design Sprint]] | ||
| Line 132: | Line 129: | ||
* 3.4 - 3 aspects of product discovery and how each contributes to successful product outcomes | * 3.4 - 3 aspects of product discovery and how each contributes to successful product outcomes | ||
* 3.6 - 3 approaches to connect the Development Team directly to customers and users | * 3.6 - 3 approaches to connect the Development Team directly to customers and users | ||
|- | |- | ||
|[[Testing Assumptions]] | |[[Testing Assumptions]] | ||
Revision as of 03:52, 23 June 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 |
|
| Scrum Roles |
|
| Agile Manifesto |
|
| 5 Scrum Values |
|
| Empirical vs Predictive Control Processes |
|
| Iterative vs. Incremental |
|
| Sprints |
|
| Sprint Planning & Product Backlog Refinement |
|
| Daily Scrum |
|
| Sprint Review |
|
| Sprint Retrospective |
|
| Definition of Done |
|
| Scrum Artefacts |
|
| Working With Stakeholders |
|
| Agile Estimation |
|
| Scaling Scrum |
|
| |
| |
| Backlog Strategy Archetypes |
|
| |
| Design Sprint |
|
| Testing Assumptions |
|
| Feature Debt |
|
| Working With The Product Backlog |
|
See Also
- Product Owner Workshop Syllabus
- Product Owner
- Scrum Master Coaching Syllabus
- Scrum Master Workshop Syllabus
- Scrum Framework
- Scrum Master