Product Owner Coaching Syllabus - Revision history

Mmusij at 00:23, 27 October 2022

2022-10-27T00:23:04Z

← Older revision		Revision as of 00:23, 27 October 2022
Line 112:		Line 112:
	* 4.1 - How Scrum supports validating product assumptions		* 4.1 - How Scrum supports validating product assumptions
	* 4.2 - 1 approach to validate product assumptions by their cost and quality of learning		* 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]]		\|[[Feature Debt]]
Line 120:		Line 125:
	\|		\|
	* F4.2 - Definition of Done		* F4.2 - Definition of Done
	\|-
	~~\|[[Working With Stakeholders]]~~
	\|
	* 1.3 - 1 technique to provide progress toward goals
	* 1.4 - 3 techniques to engage, gather information and derive insights
	\|-		\|-
	\|[[Agile Estimation]]		\|[[Agile Estimation]]

Mmusij at 00:20, 27 October 2022

2022-10-27T00:20:33Z

← Older revision		Revision as of 00:20, 27 October 2022
Line 78:		Line 78:
	*[[Story Mapping]]		*[[Story Mapping]]
	*[[Working With The Product Backlog]]		*[[Working With The Product Backlog]]
			*[[Affinity Estimation]]
	*[[Value Mapping]]		*[[Value Mapping]]
	*[[Kano Analysis]]		*[[Kano Analysis]]
	\|		\|
			* 1.3 - 1 technique to provide progress toward goals
	* 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

Mmusij at 23:51, 26 October 2022

2022-10-26T23:51:28Z

← Older revision		Revision as of 23:51, 26 October 2022
Line 48:		Line 48:
	* 5.8 - 3 criteria for ordering the Product Backlog		* 5.8 - 3 criteria for ordering the Product Backlog
	\|-		\|-
	\|		\|[[Daily Scrum]]
	* [[~~Sprint Review]]~~
	* [[Sprint Retrospective]]
	\|		\|
	* F3.1 - Timeboxing		* F3.1 - Timeboxing
	* F3.2 - 5 Scrum Events		* F3.2 - 5 Scrum Events
	\|-		\|-
	\|[[~~Daily Scrum~~]]		\|
			* [[Sprint Review]]
			* [[Sprint Retrospective]]
	\|		\|
	* F3.1 - Timeboxing		* F3.1 - Timeboxing

Mmusij at 23:47, 26 October 2022

2022-10-26T23:47:40Z

Show changes

Mmusij at 08:14, 23 June 2022

2022-06-23T08:14:09Z

← Older revision		Revision as of 08:14, 23 June 2022
Line 119:		Line 119:
	*[[Collaboration Frameworks]]		*[[Collaboration Frameworks]]
	*[[Empathy Mapping]]		*[[Empathy Mapping]]
			*[[Design Sprint]]
	\|		\|
	* 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.4 - 3 aspects of product discovery and how each contributes to successful product outcomes
	* 3.5 - 1 technique to describe users and customers: their jobs, activities, pains, and gains		* 3.5 - 1 technique to describe users and customers: their jobs, activities, pains, and gains
	\|-
	~~\|[[Design Sprint]]~~
	\|
	* 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
	\|-		\|-

Mmusij at 03:52, 23 June 2022

2022-06-23T03:52:51Z

← Older revision		Revision as of 03:52, 23 June 2022
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.4 - 2 approaches to identify small, valuable, and releasable Product Increments
	\|-
	~~\|[[Story Mapping]]~~
	\|
	* 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
	\|-
	~~\|[[Collaboration Frameworks]]~~
	\|
	* 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
	\|-
	~~\|[[Empathy Mapping]]~~
	\|
	* 3.5 - 1 technique to describe users and customers: their jobs, activities, pains, and gains
	\|-		\|-
	\|[[Testing Assumptions]]		\|[[Testing Assumptions]]

Mmusij at 03:57, 21 April 2022

2022-04-21T03:57:54Z

← Older revision		Revision as of 03:57, 21 April 2022
Line 93:		Line 93:
	\|-		\|-
	\|		\|
	[[Purpose & Strategy]]		*[[Purpose & Strategy]]
	[[Impact Mapping]]		*[[Impact Mapping]]
	\|		\|
	* 2.1 - 1 way of creating a product vision		* 2.1 - 1 way of creating a product vision
Line 100:		Line 100:
	\|-		\|-
	\|		\|
	[[Release Planning]]		*[[Release Planning]]
	[[Release Strategy]]		*[[Release Strategy]]
	[[Strategic Awareness]]		*[[Strategic Awareness]]
	[[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

Mmusij at 03:56, 21 April 2022

2022-04-21T03:56:58Z

← Older revision		Revision as of 03:56, 21 April 2022
Line 92:		Line 92:
	*1.5 - 2 ways of overcoming challenges when working with multiple teams		*1.5 - 2 ways of overcoming challenges when working with multiple teams
	\|-		\|-
	\|[[Purpose & Strategy]]		\|
			[[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
	\|-		\|-
	~~\|[[Release Planning]]~~
	\|		\|
	* 2.2 - 1 way to create a product plan or forecast with stakeholders		[[Release Planning]]
	* 2.3 - 1 way to plan a product release		[[Release Strategy]]
	\|-		[[Strategic Awareness]]
	\|[[~~Release~~ 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
	* 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
	\|-
	~~\|[[Strategic Awareness]]~~
	\|
	* 2.2 - 1 way to create a product plan or forecast with stakeholders
	\|-
	~~\|[[Evolutionary Strategy]]~~
	\|
	* 2.2 - 1 way to create a product plan or forecast with stakeholders
	\|-		\|-
	\|[[Story Mapping]]		\|[[Story Mapping]]

Mmusij at 03:52, 15 March 2022

2022-03-15T03:52:56Z

Show changes

Mmusij at 03:31, 15 March 2022

2022-03-15T03:31:28Z

← Older revision		Revision as of 03:31, 15 March 2022
Line 16:		Line 16:
	* F2.1 How Scrum Roles Interact		* F2.1 How Scrum Roles Interact
	* F2.2 Cross Functional and Self Organising Teams		* 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]]		\|[[Agile Manifesto]]
Line 68:		Line 70:
	\|		\|
	* F4.1 3 Scrum Artefacts		* F4.1 3 Scrum Artefacts
			\|-
			\|[[Working With Stakeholders]]
			\|
			* 1.3 1 technique to provide progress toward goals
			* 1.4 3 techniques to engage, gather information and derive insights
			\|-
			\|[[Agile Estimation]]
			\|
			* 1.3 1 technique to provide progress toward goals
	\|}		\|}