Scrum Master Learning Objectives: Difference between revisions

From AgileMe
Jump to navigation Jump to search
No edit summary
No edit summary
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:Agile:Articles]][[Category:Agile:Scrum]][[Category:Agile:Certification]][[Category:Agile]]
[[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 Scrum Masters.


==Foundation Learning Objectives==
==Foundation Learning Objectives==
Line 7: Line 8:
!Classification
!Classification
!Learning Objective
!Learning Objective
!Session
!Session Mapping
|-
|-
|1.1
|F1.1
|Scrum Theory
|Scrum Theory
|Scrum easy to learn and difficult to master
|Scrum and Agile Manifesto
|Scrum Framework
|[[Agile Manifesto]]
|-
|-
|1.2
|F1.2
|Scrum Theory
|Scrum Theory
|3 Core Elements of Scrum
|Scrum and its Purpose
|Scrum Framework
|[[Scrum Framework]]
|-
|-
|1.3
|F1.3
|Scrum Theory
|Scrum Theory
|5 Scrum Values
|5 Scrum Values
|Scrum Values
|[[5 Scrum Values]]
|-
|-
|1.4
|F1.4
|Scrum Theory
|Scrum Theory
|3 Pillars of Empirical Process Control
|3 Pillars of Empirical Process Control
|Empirical Process Control
|[[Empirical vs Predictive Control Processes]]
|-
|-
|1.5
|F1.5
|Scrum Theory
|Scrum Theory
|Scrum as a Framework
|Traditional vs Empirical Product Planning
|Scrum Framework
|[[Empirical vs Predictive Control Processes]]
|-
|-
|1.6
|F1.6
|Scrum Theory
|Scrum Theory
|Scrum in its Entirety
|Scrum in its Entirety
|Scrum Framework
|[[Scrum Framework]]
|-
|F1.7
|Scrum Theory
|Iterative and Incremental Approaches
|[[Iterative vs. Incremental]]
|-
|-
|2.1
|F2.1
|Scrum Roles
|3 Roles and Responsibilities
|Scrum Roles
|Scrum Roles
|How Scrum Roles Interact
|[[Scrum Roles]]
|-
|-
|2.2
|F2.2
|Scrum Roles
|Scrum Roles
|Cross Functional and Self Organising Teams
|Cross Functional and Self Organising Teams
|Scrum Roles
|[[Scrum Roles]]
|-
|-
|2.3
|F3.1
|Scrum Roles
|Scrum Events
|Impacts of Shared Roles
|Timeboxing
|Scrum Roles
|
* [[Sprints]]
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|-
|3.1
|F3.2
|Scrum Events and Artefacts
|Scrum Events
|3 Artefacts
|5 Scrum Events
|Scrum Framework
|
* [[Sprints]]
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|-
|3.2
|F4.1
|Scrum Events and Artefacts
|Scrum Artefacts
|Definition of Done
|3 Scrum Artefacts
|Definition of Done
|
|-
* [[Scrum Artefacts]]
|3.3
|Scrum Events and Artefacts
|Definition of Done evolution over time
|Definition of Done
|-
|-
|3.4
|F4.2
|Scrum Events and Artefacts
|Scrum Artefacts
|Product Quality
|Definition of Done
|Definition of Done
|[[Definition of Done]]
|-
|-
|3.5
|F4.3
|Scrum Events and Artefacts
|Scrum Artefacts
|4 Scrum Events
|
* Sprints
* Sprint Planning
* Daily Scrum
* Sprint Review
* Sprint Retrospective
|-
|3.6
|Scrum Events and Artefacts
|Timeboxes
|Sprints
|-
|3.7
|Scrum Events and Artefacts
|Product Backlog Refinement
|Product Backlog Refinement
|Sprint Planning & Product Backlog Refinement
|[[Sprint Planning & Product Backlog Refinement]]
|-
|-
|3.8
|F4.4
|Scrum Events and Artefacts
|Scrum Events and Artefacts
|Development Team and Product Backlog Refinement
|3 Activities During Product Backlog Refinement
|Sprint Planning & Product Backlog Refinement
|[[Sprint Planning & Product Backlog Refinement]]
|-
|3.9
|Scrum Events and Artefacts
|3 Topics during Product Backlog Refinement
|Sprint Planning & Product Backlog Refinement
|-
|3.10
|Scrum Events and Artefacts
|3 Characteristics of Product Backlog Refinement
|Sprint Planning & Product Backlog Refinement
|}
|}


Line 116: Line 103:
!Classification
!Classification
!Learning Objective
!Learning Objective
!Session
!Session Mapping
|-
|-
|1.1
|1.1
|Value and Principles
|Scrum Roles
|Scrum & Agile Manifesto
|3 Rights and 5 Responsibilities
|Agile Manifesto
|[[Scrum Roles]]
|-
|-
|1.2
|1.2
|Scrum Theory
|Scrum Roles
|3 Pillars of Empirical Process Control
|2 Reasons Why Product Owner is one person
|
|[[Scrum Roles]]
|-
|-
|1.3
|1.3
|Scrum Theory
|Scrum Roles
|
|How and why Product Owner has authority over the product
|
|[[Scrum Roles]]
|-
|-
|1.4
|1.4
|Scrum Theory
|Scrum Roles
|
|5 Characteristics of the Development Team
|
|[[Scrum Roles]]
|-
|-
|1.5
|1.5
|Scrum Theory
|Scrum Events & Artefacts
|
|How Scrum Team increases transparency, inspection and adaptation in the Scrum events
|
|[[Empirical vs Predictive Control Processes]]
|-
|-
|1.6
|1.6
|Scrum Team
|Scrum Events & Artefacts
|
|3 responsibilities of the Scrum roles during events
|
|
* [[Sprint Planning & Product Backlog Refinement]]
* [[Daily Scrum]]
* [[Sprint Review]]
* [[Sprint Retrospective]]
|-
|-
|1.7
|1.7
|Scrum Team
|Sprint and Increment
|
|Sprint Goal does not change during Sprint
|
|[[Sprint Planning & Product Backlog Refinement]]
|-
|-
|1.8
|1.8
|Product Owner
|Sprint and Increment
|
|Outcome of each Sprint
|
|[[Definition of Done]]
|-
|-
|1.9
|1.9
|Product Owner
|Sprint and Increment
|
|3 reasons why Increment corresponds to the Definition of Done
|
|[[Definition of Done]]
|-
|-
|1.10
|1.10
|Product Owner
|Sprint Planning
|
|Activities during Sprint Planning
|
|[[Sprint Planning & Product Backlog Refinement]]
|-
|-
|1.11
|1.11
|Dev Team
|Sprint Planning
|
|Sprint Goals
|
|[[Sprint Planning & Product Backlog Refinement]]
|-
|-
|1.12
|1.12
|Dev Team
|Daily Scrum
|
|3 ways the Daily Scrum differs from a status reporting meeting
|
|[[Daily Scrum]]
|-
|-
|1.13
|1.13
|Dev Team
|Sprint Review
|
|3 Activities other than demo in a Sprint Review
|
|[[Sprint Review]]
|-
|-
|1.14
|1.14
|Dev Team
|Sprint Review
|
|3 outcome from a Sprint Review
|
|[[Sprint Review]]
|-
|-
|1.15
|1.15
|Scrum Master
|Sprint Retrospective
|
|2 approaches for a Sprint Retrospective
|
|[[Sprint Retrospective]]
|-
|-
|1.16
|1.16
|Scrum Master
|Product Backlog
|
|3 characteristics of the Product Backlog
|
|[[Scrum Artefacts]]
|-
|-
|1.17
|1.17
|Scrum Events and Artefacts
|Product Backlog
|
|4 attributes of a Product Backlog Item
|
|[[Scrum Artefacts]]
|-
|-
|1.18
|1.18
|Scrum Events and Artefacts
|Sprint Backlog
|
|3 characteristics of the Sprint Backlog
|
|[[Scrum Artefacts]]
|-
|-
|1.19
|1.19
|Sprint and Increment
|Sprint Backlog
|
|How the Sprint Backlog can change preserving the Sprint Goal
|
|[[Scrum Artefacts]]
|-
|-
|1.20
|1.20
|Sprint and Increment
|Definition of “Done”
|
|2 risks of weak Definition of Done
|
|[[Definition of Done]]
|-
|-
|1.21
|1.21
|Sprint and Increment
|Definition of “Done”
|
|How to create a Definition of Done
|
|[[Definition of Done]]
|-
|-
|1.22
|1.22
|Sprint and Increment
|Definition of “Done”
|
|Why multiple teams need to work to the same Definition of Done
|
|[[Definition of Done]]
|-
|1.23
|Sprint Planning
|
|
|-
|1.24
|Sprint Planning
|
|
|-
|1.25
|Sprint Planning
|
|
|-
|1.26
|Sprint Planning
|
|
|-
|1.27
|Sprint Planning
|
|
|-
|1.28
|Daily Scrum
|
|
|-
|1.29
|Daily Scrum
|
|
|-
|1.30
|Daily Scrum
|
|
|-
|1.31
|Daily Scrum
|
|
|-
|1.32
|Product Backlog Refinement
|
|
|-
|1.33
|Product Backlog Refinement
|
|
|-
|1.34
|Sprint Review
|
|
|-
|1.35
|Sprint Review
|
|
|-
|1.36
|Sprint Review
|
|
|-
|1.37
|Sprint Review
|
|
|-
|1.38
|Sprint Review
|
|
|-
|1.39
|Sprint Retrospective
|
|
|-
|1.40
|Sprint Retrospective
|
|
|-
|1.41
|Product Backlog
|
|
|-
|1.42
|Product Backlog
|
|
|-
|1.43
|Product Backlog
|
|
|-
|1.44
|Sprint Backlog
|
|
|-
|1.45
|Sprint Backlog
|
|
|-
|1.46
|Definition of Done
|
|
|-
|1.47
|Definition of Done
|
|
|-
|1.48
|Definition of Done
|
|
|-
|1.49
|Definition of Done
|
|
|-
|-
|2.1
|2.1
|Agile Facilitation
|Facilitation
|
|3 situations where Scrum Master helps with facilitation
|
|[[Scrum Master As A Facilitator]]
|-
|-
|2.2
|2.2
|Agile Facilitation
|Facilitation
|
|3 techniques for group decision making
|
|[[Scrum Master As A Facilitator]]
|-
|-
|2.3
|2.3
|Agile Facilitation
|Coaching
|
|Teaching, mentoring and coaching differences
|
|[[Scrum Master As A Coach]]
|-
|-
|2.4
|2.4
|Agile Facilitation
|Coaching
|
|How to apply at least one technique
|
|[[Scrum Master As A Coach]]
|-
|2.5
|Agile Facilitation
|
|
|-
|-
|3.1
|3.1
|Agile Coaching
|Scrum Master as Servant-Leader
|
|Define servant leadership
|
|[[Scrum Roles]]
|-
|-
|3.2
|3.2
|Agile Coaching
|Scrum Master as Servant-Leader
|
|3 scenarios where Scrum Master acts as servant leader
|
|[[Scrum Roles]]
|-
|-
|3.3
|3.3
|Agile Coaching
|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
|4.1
|Scrum Master As Servant Leader
|Service to the Product Owner
|
|3 ways Scrum Master supports the Product Owner
|
|[[Scrum Roles]]
|-
|-
|4.2
|4.2
|Scrum Master As Servant Leader
|Service to the Product Owner
|
|2 benefits of Product Owner participating in Sprint Retrospectives
|
|[[Sprint Retrospective]]
|-
|4.3
|Scrum Master As Servant Leader
|
|
|-
|4.4
|Engineering Practices
|
|
|-
|4.5
|Engineering Practices
|
|
|-
|4.6
|Engineering Practices
|
|
|-
|-
|5.1
|5.1
|Coaching The Product Owner
|Impediment Removal
|
|2 ways Scrum Master removes impediments
|
|[[Scrum Roles]]
|-
|-
|5.2
|5.2
|Coaching The Product Owner
|
|
|-
|6.1
|Impediment Removal
|Impediment Removal
|
|3 organisational impediments affecting Scrum teams
|
|[[Adoption of Scrum]]
|-
|-
|6.2
|5.3
|Impediment Removal
|
|
|-
|6.3
|Coaching the Organisation
|Coaching the Organisation
|
|Organisational design change caused by adopting Scrum
|
|[[Adoption of Scrum]]
|-
|-
|6.4
|5.4
|Coaching the Organisation
|Coaching the Organisation
|
|What happens to traditional project management activities
|
|[[Scrum Roles]]
|-
|6.5
|Coaching the Organisation
|
|
|-
|6.6
|Coaching the Organisation
|
|
|-
|6.7
|Coaching the Organisation
|
|
|-
|6.8
|Coaching the Organisation
|
|
|}
|}


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


==References==
==References==

Latest revision as of 00:05, 15 March 2022

Below are the learning objectives based upon the Scrum Alliance learning objectives for coaching Scrum Masters.

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

Scrum Master Learning Objectives

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
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

References

Retrieved from "https://agileme.wiki/wiki/index.php?title=Scrum_Master_Learning_Objectives&oldid=1446"