Product Owner Learning Objectives - Revision history

Mmusij: /* Product Owner Learning Objectives */

2022-03-15T02:27:06Z

Product Owner Learning Objectives

← Older revision		Revision as of 02:27, 15 March 2022
Line 184:		Line 184:
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|3 aspects of product discovery and how each contributes to successful product outcomes		\|3 aspects of product discovery and how each contributes to successful product outcomes
	\|[[]]		\|[[Design Sprint]]
	\|-		\|-
	\|3.5		\|3.5
Line 194:		Line 194:
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|3 approaches to connect the Development Team directly to customers and users		\|3 approaches to connect the Development Team directly to customers and users
	\|[[]]		\|[[Design Sprint]]
	\|-		\|-
	\|3.7		\|3.7
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|3 benefits of Development Team direct interactions		\|3 benefits of Development Team direct interactions
	\|[[]]		\|[[Sprint Planning & Product Backlog Refinement]]
	\|-		\|-
	\|4.1		\|4.1

Mmusij: /* Product Owner Learning Objectives */

2022-03-15T02:24:30Z

Product Owner Learning Objectives

← Older revision		Revision as of 02:24, 15 March 2022
Line 164:		Line 164:
	*[[Release Strategy]]		*[[Release Strategy]]
	*[[Iterative vs. Incremental]]		*[[Iterative vs. Incremental]]
			*[[Backlog Strategy Archetypes]]
	\|-		\|-
	\|3.1		\|3.1
Line 213:		Line 214:
	\|Differentiating Outcome and Output		\|Differentiating Outcome and Output
	\|describe the relationship between outcome and output		\|describe the relationship between outcome and output
	\|[[]]		\|
			*[[Feature Debt]]
	\|-		\|-
	\|5.2		\|5.2
Line 238:		Line 240:
	\|Creating and Refining Items		\|Creating and Refining Items
	\|Create a Product Backlog Item that includes description of desired outcome and value		\|Create a Product Backlog Item that includes description of desired outcome and value
	\|[[Product Backlog Refinement]]		\|
			*[[Product Backlog Refinement]]
			*[[Backlog Strategy Archetypes]]
	\|-		\|-
	\|5.7		\|5.7

Mmusij at 01:18, 15 March 2022

2022-03-15T01:18:18Z

← Older revision		Revision as of 01:18, 15 March 2022
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

Mmusij: /* Product Owner Learning Objectives */

2022-03-15T01:11:01Z

Product Owner Learning Objectives

← Older revision		Revision as of 01:11, 15 March 2022
Line 118:		Line 118:
	\|Working with Stakeholders		\|Working with Stakeholders
	\|1 technique to provide progress toward goals		\|1 technique to provide progress toward goals
	\|[[]]		\|
			*[[Working With Stakeholders]]
			*[[Agile Estimation]]
	\|-		\|-
	\|1.4		\|1.4
	\|Working with Stakeholders		\|Working with Stakeholders
	\|3 techniques to engage, gather information and derive insights		\|3 techniques to engage, gather information and derive insights
	\|[[]]		\|[[Working With Stakeholders]]
	\|-		\|-
	\|1.5		\|1.5
Line 138:		Line 140:
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|1 way to create a product plan or forecast with stakeholders		\|1 way to create a product plan or forecast with stakeholders
	\|[[]]		\|
			*[[Release Planning]]
			*[[Release Strategy]]
	\|-		\|-
	\|2.3		\|2.3
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|1 way to plan a product release		\|1 way to plan a product release
	\|[[]]		\|
			*[[Release Planning]]
			*[[Story Mapping]]
			*[[Release Strategy]]
	\|-		\|-
	\|2.4		\|2.4
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|2 approaches to identify small, valuable, and releasable Product Increments		\|2 approaches to identify small, valuable, and releasable Product Increments
	\|[[]]		\|
			*[[Story Mapping]]
			*[[Release Strategy]]
	\|-		\|-
	\|3.1		\|3.1
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|Why a Product Owner performs discovery and validation work		\|Why a Product Owner performs discovery and validation work
	\|[[]]		\|[[Customer Research]]
	\|-		\|-
	\|3.2		\|3.2
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|1 approach for segmenting customers and users		\|1 approach for segmenting customers and users
	\|[[]]		\|[[Customer Research]]
	\|-		\|-
	\|3.3		\|3.3
Line 218:		Line 227:
	\|Defining Value		\|Defining Value
	\|3 terms related to product economics		\|3 terms related to product economics
	\|[[]]		\|[[Agile Estimation]]
	\|-		\|-
	\|5.6		\|5.6
	\|Creating and Refining Items		\|Creating and Refining Items
	\|Create a Product Backlog Item that includes description of desired outcome and value		\|Create a Product Backlog Item that includes description of desired outcome and value
	\|[[]]		\|[[Product Backlog Refinement]]
	\|-		\|-
	\|5.7		\|5.7
	\|Creating and Refining Items		\|Creating and Refining Items
	\|1 approach to Product Backlog Refinement		\|1 approach to Product Backlog Refinement
	\|[[]]		\|[[Product Backlog Refinement]]
	\|-		\|-
	\|5.8		\|5.8
	\|Creating and Refining Items		\|Creating and Refining Items
	\|3 criteria for ordering the Product Backlog		\|3 criteria for ordering the Product Backlog
	\|[[]]		\|[[Product Backlog Refinement]]
	\|}		\|}

Mmusij at 00:37, 15 March 2022

2022-03-15T00:37:54Z

← Older revision		Revision as of 00:37, 15 March 2022
Line 117:		Line 117:
	\|1.3		\|1.3
	\|Working with Stakeholders		\|Working with Stakeholders
	\|~~use at least one~~ technique to provide ~~transparency to stakeholders on~~ progress toward goals		\|1 technique to provide progress toward goals
	\|[[]]		\|[[]]
	\|-		\|-
	\|1.4		\|1.4
	\|Working with Stakeholders		\|Working with Stakeholders
	\|~~list at least three~~ techniques to engage ~~stakeholders to~~ gather information or insights		\|3 techniques to engage, gather information and derive insights
	\|[[]]		\|[[]]
	\|-		\|-
	\|1.5		\|1.5
	\|Product Ownership with Multiple Teams		\|Product Ownership with Multiple Teams
	\|~~identify at least two~~ ways of overcoming ~~the~~ challenges ~~of being a Product Owner for~~ multiple teams		\|2 ways of overcoming challenges when working with multiple teams
	\|[[]]		\|[[]]
	\|-		\|-
	\|2.1		\|2.1
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|~~practice the creation~~ of a product vision.		\|1 way of creating a product vision
	\|[[]]		\|[[]]
	\|-		\|-
	\|2.2		\|2.2
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|~~list the components of~~ a product plan or forecast with stakeholders		\|1 way to create a product plan or forecast with stakeholders
	\|[[]]		\|[[]]
	\|-		\|-
	\|2.3		\|2.3
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|~~describe how~~ to plan a product release		\|1 way to plan a product release
	\|[[]]		\|[[]]
	\|-		\|-
	\|2.4		\|2.4
	\|Describing Purpose and Strategy		\|Describing Purpose and Strategy
	\|~~explain at least two~~ approaches to identify small, valuable, and releasable Product Increments		\|2 approaches to identify small, valuable, and releasable Product Increments
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.1		\|3.1
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~describe why~~ a Product Owner performs discovery and validation work		\|Why a Product Owner performs discovery and validation work
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.2		\|3.2
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~illustrate at least one~~ approach for segmenting customers and users		\|1 approach for segmenting customers and users
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.3		\|3.3
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~practice at least one~~ technique to prioritise between conflicting customer (or user) needs		\|1 technique to prioritise between conflicting customer (or user) needs
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.4		\|3.4
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~describe at least three~~ aspects of product discovery and ~~identify~~ how each contributes to successful product outcomes		\|3 aspects of product discovery and how each contributes to successful product outcomes
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.5		\|3.5
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~use one~~ technique to describe users and customers: their jobs, activities, pains, and gains		\|1 technique to describe users and customers: their jobs, activities, pains, and gains
	\|[[]]		\|[[Empathy Mapping]]
	\|-		\|-
	\|3.6		\|3.6
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~list at least three~~ approaches to connect the Development Team directly to customers and users		\|3 approaches to connect the Development Team directly to customers and users
	\|[[]]		\|[[]]
	\|-		\|-
	\|3.7		\|3.7
	\|Understanding Customers and Users		\|Understanding Customers and Users
	\|~~describe at least three~~ benefits of Development Team direct interactions		\|3 benefits of Development Team direct interactions
	\|[[]]		\|[[]]
	\|-		\|-
	\|4.1		\|4.1
	\|Validating Product Assumptions		\|Validating Product Assumptions
	\|~~describe how~~ Scrum supports validating product assumptions		\|How Scrum supports validating product assumptions
	\|[[]]		\|[[]]
	\|-		\|-
	\|4.2		\|4.2
	\|Validating Product Assumptions		\|Validating Product Assumptions
	\|~~describe at least one~~ 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
	\|[[]]		\|[[]]
	\|-		\|-
Line 202:		Line 202:
	\|5.2		\|5.2
	\|Differentiating Outcome and Output		\|Differentiating Outcome and Output
	\|~~describe at least three~~ attributes of a Product Backlog item that help assess ~~maximizing~~ outcome		\|3 attributes of a Product Backlog item that help assess maximising outcome
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.3		\|5.3
	\|Defining Value		\|Defining Value
	\|~~define value and list at least two~~ techniques to measure value		\|2 techniques to measure value
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.4		\|5.4
	\|Defining Value		\|Defining Value
	\|~~describe value~~ from ~~the perspective of at least three~~ different stakeholder groups		\|Value from 3 different stakeholder groups
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.5		\|5.5
	\|Defining Value		\|Defining Value
	\|~~list at least three~~ terms related to product economics		\|3 terms related to product economics
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.6		\|5.6
	\|Creating and Refining Items		\|Creating and Refining Items
	\|~~create at least one~~ Product Backlog ~~item~~ that includes description of desired outcome and value		\|Create a Product Backlog Item that includes description of desired outcome and value
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.7		\|5.7
	\|Creating and Refining Items		\|Creating and Refining Items
	\|~~describe at least one~~ approach to Product Backlog Refinement		\|1 approach to Product Backlog Refinement
	\|[[]]		\|[[]]
	\|-		\|-
	\|5.8		\|5.8
	\|Creating and Refining Items		\|Creating and Refining Items
	\|~~describe at least three~~ criteria for ordering the Product Backlog		\|3 criteria for ordering the Product Backlog
	\|[[]]		\|[[]]
	\|}		\|}

Mmusij at 00:29, 15 March 2022

2022-03-15T00:29:40Z

@@ Line 106: / Line 106: @@
 |-
 |1.1
-|Scrum Roles
+|Fundamentals of the Product Owner Role
-|3 Rights and 5 Responsibilities
+|3 organizational contexts that affect the approach to the Product Owner role
 |[[Scrum Roles]]
 |}

Mmusij at 00:14, 15 March 2022

2022-03-15T00:14:47Z

Show changes

Mmusij at 00:11, 15 March 2022

2022-03-15T00:11:32Z

← Older revision		Revision as of 00:11, 15 March 2022
Line 306:		Line 306:
	==References==		==References==
	* [https://scrumguides.org/index.html The Scrum Guide]		* [https://scrumguides.org/index.html The Scrum Guide]
	* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/~~E_CSM_LO_5~~-20-21.pdf Certified ~~Scrum Master~~ (~~CSM~~) Learning Objectives, 2021]		* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/E_CSPO_LO_5-20-21.pdf Certified Product Owner (CSPO) Learning Objectives, 2021]
	* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/E_Scrum-Foundations_LO_5-20-21.pdf Scrum Foundations Learning Objectives, 2021]		* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/E_Scrum-Foundations_LO_5-20-21.pdf Scrum Foundations Learning Objectives, 2021]

Mmusij: Created page with "Category:Agile:ArticlesCategory:Agile:ScrumCategory:Agile:CertificationCategory:Agile Below are the learning objectives based upon the Scrum Alliance learning objectives for coaching Product Owners. ==Foundation Learning Objectives== {| class="wikitable" !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...."

2022-03-15T00:05:22Z

Created page with "Category:Agile:Articles Category:Agile:Scrum Category:Agile:Certification Category:Agile Below are the learning objectives based upon the Scrum Alliance learning objectives for coaching Product Owners. ==Foundation Learning Objectives== {| class="wikitable" !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...."

New page

[[Category:Agile:Articles]][[Category:Agile:Scrum]][[Category:Agile:Certification]][[Category:Agile]]
Below are the learning objectives based upon the Scrum Alliance learning objectives for coaching Product Owners.

==Foundation Learning Objectives==

{| class="wikitable"
!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
|
* [[Sprints]]
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|F3.2
|Scrum Events
|5 Scrum Events
|
* [[Sprints]]
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|F4.1
|Scrum Artefacts
|3 Scrum Artefacts
|
* [[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==

{| class="wikitable"
!ID
!Classification
!Learning Objective
!Session Mapping
|-
|1.1
|Scrum Roles
|3 Rights and 5 Responsibilities
|[[Scrum Roles]]
|-
|1.2
|Scrum Roles
|2 Reasons Why Product Owner is one person
|[[Scrum Roles]]
|-
|1.3
|Scrum Roles
|How and why Product Owner has authority over the product
|[[Scrum Roles]]
|-
|1.4
|Scrum Roles
|5 Characteristics of the Development Team
|[[Scrum Roles]]
|-
|1.5
|Scrum Events & Artefacts
|How Scrum Team increases transparency, inspection and adaptation in the Scrum events
|[[Empirical vs Predictive Control Processes]]
|-
|1.6
|Scrum Events & Artefacts
|3 responsibilities of the Scrum roles during events
|
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|1.7
|Sprint and Increment
|Sprint Goal does not change during Sprint
|[[Sprint Planning & Product Backlog Refinement]]
|-
|1.8
|Sprint and Increment
|Outcome of each Sprint
|[[Definition of Done]]
|-
|1.9
|Sprint and Increment
|3 reasons why Increment corresponds to the Definition of Done
|[[Definition of Done]]
|-
|1.10
|Sprint Planning
|Activities during Sprint Planning
|[[Sprint Planning & Product Backlog Refinement]]
|-
|1.11
|Sprint Planning
|Sprint Goals
|[[Sprint Planning & Product Backlog Refinement]]
|-
|1.12
|Daily Scrum
|3 ways the Daily Scrum differs from a status reporting meeting
|[[Daily Scrum]]
|-
|1.13
|Sprint Review
|3 Activities other than demo in a Sprint Review
|[[Sprint Review]]
|-
|1.14
|Sprint Review
|3 outcome from a Sprint Review
|[[Sprint Review]]
|-
|1.15
|Sprint Retrospective
|2 approaches for a Sprint Retrospective
|[[Sprint Retrospective]]
|-
|1.16
|Product Backlog
|3 characteristics of the Product Backlog
|[[Scrum Artefacts]]
|-
|1.17
|Product Backlog
|4 attributes of a Product Backlog Item
|[[Scrum Artefacts]]
|-
|1.18
|Sprint Backlog
|3 characteristics of the Sprint Backlog
|[[Scrum Artefacts]]
|-
|1.19
|Sprint Backlog
|How the Sprint Backlog can change preserving the Sprint Goal
|[[Scrum Artefacts]]
|-
|1.20
|Definition of “Done”
|2 risks of weak Definition of Done
|[[Definition of Done]]
|-
|1.21
|Definition of “Done”
|How to create a Definition of Done
|[[Definition of Done]]
|-
|1.22
|Definition of “Done”
|Why multiple teams need to work to the same Definition of Done
|[[Definition of Done]]
|-
|2.1
|Facilitation
|3 situations where Scrum Master helps with facilitation
|[[Scrum Master As A Facilitator]]
|-
|2.2
|Facilitation
|3 techniques for group decision making
|[[Scrum Master As A Facilitator]]
|-
|2.3
|Coaching
|Teaching, mentoring and coaching differences
|[[Scrum Master As A Coach]]
|-
|2.4
|Coaching
|How to apply at least one technique
|[[Scrum Master As A Coach]]
|-
|3.1
|Scrum Master as Servant-Leader
|Define servant leadership
|[[Scrum Roles]]
|-
|3.2
|Scrum Master as Servant-Leader
|3 scenarios where Scrum Master acts as servant leader
|[[Scrum Roles]]
|-
|3.3
|Scrum Master as Servant-Leader
|Impacts of time pressure by Product Owner or stakeholders and how to resolve
|[[Adoption of Scrum]]
|-
|3.4
|Scrum Master as Servant-Leader
|Technical Debt
|[[Technical Debt]]
|-
|3.5
|Scrum Master as Servant-Leader
|3 development practices
|[[Extreme Programming (XP)]]
|-
|4.1
|Service to the Product Owner
|3 ways Scrum Master supports the Product Owner
|[[Scrum Roles]]
|-
|4.2
|Service to the Product Owner
|2 benefits of Product Owner participating in Sprint Retrospectives
|[[Sprint Retrospective]]
|-
|5.1
|Impediment Removal
|2 ways Scrum Master removes impediments
|[[Scrum Roles]]
|-
|5.2
|Impediment Removal
|3 organisational impediments affecting Scrum teams
|[[Adoption of Scrum]]
|-
|5.3
|Coaching the Organisation
|Organisational design change caused by adopting Scrum
|[[Adoption of Scrum]]
|-
|5.4
|Coaching the Organisation
|What happens to traditional project management activities
|[[Scrum Roles]]
|}

==See Also==
* [[Product Owner Coaching Syllabus]]
* [[Product Owner Workshop Syllabus]]
* [[Product Owner]]
* [[Scrum Master Coaching Syllabus]]
* [[Scrum Master Workshop Syllabus]]
* [[Scrum Framework]]
* [[Scrum Master]]

==References==
* [https://scrumguides.org/index.html The Scrum Guide]
* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/E_CSM_LO_5-20-21.pdf Certified Scrum Master (CSM) Learning Objectives, 2021]
* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Learning%20Objectives/E_Scrum-Foundations_LO_5-20-21.pdf Scrum Foundations Learning Objectives, 2021]