Scrum Master Coaching Syllabus: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
|[[Scrum Framework]] | |[[Scrum Framework]] | ||
| | | | ||
* F1.2 Scrum and its Purpose | * F1.2 - Scrum and its Purpose | ||
* F1.6 Scrum in its Entirety | * F1.6 - Scrum in its Entirety | ||
|- | |- | ||
|[[Scrum Roles]] | |[[Scrum Roles]] | ||
| | | | ||
* 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 Rights and 5 Responsibilities | * 1.1 - 3 Rights and 5 Responsibilities | ||
* 1.2 2 Reasons Why Product Owner is one person | * 1.2 - 2 Reasons Why Product Owner is one person | ||
* 1.3 How and why Product Owner has authority over the product | * 1.3 - How and why Product Owner has authority over the product | ||
* 1.4 5 Characteristics of the Development Team | * 1.4 - 5 Characteristics of the Development Team | ||
* 3.1 Define servant leadership | * 3.1 - Define servant leadership | ||
* 3.2 3 scenarios where Scrum Master acts as servant leader | * 3.2 - 3 scenarios where Scrum Master acts as servant leader | ||
* 4.1 3 ways Scrum Master supports the Product Owner | * 4.1 - 3 ways Scrum Master supports the Product Owner | ||
* 5.1 2 ways Scrum Master removes impediments | * 5.1 - 2 ways Scrum Master removes impediments | ||
* 5.4 What happens to traditional project management activities | * 5.4 - What happens to traditional project management activities | ||
|- | |- | ||
|[[Agile Manifesto]] | |[[Agile Manifesto]] | ||
| | | | ||
* F1.1 Scrum and Agile Manifesto | * F1.1 - Scrum and Agile Manifesto | ||
|- | |- | ||
|[[5 Scrum Values]] | |[[5 Scrum Values]] | ||
| | | | ||
* F1.3 5 Scrum Values | * F1.3 - 5 Scrum Values | ||
|- | |- | ||
|[[Empirical vs Predictive Control Processes]] | |[[Empirical vs Predictive Control Processes]] | ||
| | | | ||
* F1.4 3 Pillars of Empirical Process Control | * F1.4 - 3 Pillars of Empirical Process Control | ||
* F1.5 Traditional vs Empirical Product Planning | * F1.5 - Traditional vs Empirical Product Planning | ||
* 1.5 How Scrum Team increases transparency, inspection and adaptation in the Scrum events | * 1.5 - How Scrum Team increases transparency, inspection and adaptation in the Scrum events | ||
|- | |- | ||
|[[Iterative vs. Incremental]] | |[[Iterative vs. Incremental]] | ||
| | | | ||
* F1.7 Iterative and Incremental Approaches | * F1.7 - Iterative and Incremental Approaches | ||
|- | |- | ||
|[[Sprints]] | |[[Sprints]] | ||
| | | | ||
* F3.1 Timeboxing | * F3.1 - Timeboxing | ||
* F3.2 5 Scrum Events | * F3.2 - 5 Scrum Events | ||
|- | |- | ||
|[[Sprint Planning & Product Backlog Refinement]] | |[[Sprint Planning & Product Backlog Refinement]] | ||
| | | | ||
* F3.1 Timeboxing | * F3.1 - Timeboxing | ||
* F3.2 5 Scrum Events | * F3.2 - 5 Scrum Events | ||
* F4.3 Product Backlog Refinement | * F4.3 - Product Backlog Refinement | ||
* F4.4 3 Activities During Product Backlog Refinement | * F4.4 - 3 Activities During Product Backlog Refinement | ||
* 1.6 3 responsibilities of the Scrum roles during events | * 1.6 - 3 responsibilities of the Scrum roles during events | ||
* 1.7 Sprint Goal does not change during Sprint | * 1.7 - Sprint Goal does not change during Sprint | ||
* 1.10 Activities during Sprint Planning | * 1.10 - Activities during Sprint Planning | ||
* 1.11 Sprint Goals | * 1.11 - Sprint Goals | ||
|- | |- | ||
|[[Daily Scrum]] | |[[Daily Scrum]] | ||
| | | | ||
* F3.1 Timeboxing | * F3.1 - Timeboxing | ||
* F3.2 5 Scrum Events | * F3.2 - 5 Scrum Events | ||
* 1.6 3 responsibilities of the Scrum roles during events | * 1.6 - 3 responsibilities of the Scrum roles during events | ||
* 1.12 3 ways the Daily Scrum differs from a status reporting meeting | * 1.12 - 3 ways the Daily Scrum differs from a status reporting meeting | ||
|- | |- | ||
|[[Sprint Review]] | |[[Sprint Review]] | ||
| | | | ||
* F3.1 Timeboxing | * F3.1 - Timeboxing | ||
* F3.2 5 Scrum Events | * F3.2 - 5 Scrum Events | ||
* 1.6 3 responsibilities of the Scrum roles during events | * 1.6 - 3 responsibilities of the Scrum roles during events | ||
* 1.13 3 Activities other than demo in a Sprint Review | * 1.13 - 3 Activities other than demo in a Sprint Review | ||
* 1.14 3 outcome from a Sprint Review | * 1.14 - 3 outcome from a Sprint Review | ||
|- | |- | ||
|[[Sprint Retrospective]] | |[[Sprint Retrospective]] | ||
| | | | ||
* F3.1 Timeboxing | * F3.1 - Timeboxing | ||
* F3.2 5 Scrum Events | * F3.2 - 5 Scrum Events | ||
* 1.6 3 responsibilities of the Scrum roles during events | * 1.6 - 3 responsibilities of the Scrum roles during events | ||
* 1.15 2 approaches for a Sprint Retrospective | * 1.15 - 2 approaches for a Sprint Retrospective | ||
* 4.2 2 benefits of Product Owner participating in Sprint Retrospectives | * 4.2 - 2 benefits of Product Owner participating in Sprint Retrospectives | ||
|- | |- | ||
|[[Definition of Done]] | |[[Definition of Done]] | ||
| | | | ||
* F4.2 Definition of Done | * F4.2 - Definition of Done | ||
* 1.8 Outcome of each Sprint | * 1.8 - Outcome of each Sprint | ||
* 1.9 3 reasons why Increment corresponds to the Definition of Done | * 1.9 - 3 reasons why Increment corresponds to the Definition of Done | ||
* 1.20 2 risks of weak Definition of Done | * 1.20 - 2 risks of weak Definition of Done | ||
* 1.21 How to create a Definition of Done | * 1.21 - How to create a Definition of Done | ||
* 1.22 Why multiple teams need to work to the same Definition of Done | * 1.22 - Why multiple teams need to work to the same Definition of Done | ||
|- | |- | ||
|[[Scrum Artefacts]] | |[[Scrum Artefacts]] | ||
| | | | ||
* F4.1 3 Scrum Artefacts | * F4.1 - 3 Scrum Artefacts | ||
* 1.16 3 characteristics of the Product Backlog | * 1.16 - 3 characteristics of the Product Backlog | ||
* 1.17 4 attributes of a Product Backlog Item | * 1.17 - 4 attributes of a Product Backlog Item | ||
* 1.18 3 characteristics of the Sprint Backlog | * 1.18 - 3 characteristics of the Sprint Backlog | ||
* 1.19 How the Sprint Backlog can change preserving the Sprint Goal | * 1.19 - How the Sprint Backlog can change preserving the Sprint Goal | ||
|- | |- | ||
|[[Scrum Master As A Facilitator]] | |[[Scrum Master As A Facilitator]] | ||
| | | | ||
* 2.1 3 situations where Scrum Master helps with facilitation | * 2.1 - 3 situations where Scrum Master helps with facilitation | ||
* 2.2 3 techniques for group decision making | * 2.2 - 3 techniques for group decision making | ||
|- | |- | ||
|[[Scrum Master As A Coach]] | |[[Scrum Master As A Coach]] | ||
| | | | ||
* 2.3 Teaching, mentoring and coaching differences | * 2.3 - Teaching, mentoring and coaching differences | ||
* 2.4 How to apply at least one technique | * 2.4 - How to apply at least one technique | ||
|- | |- | ||
|[[Adoption of Scrum]] | |[[Adoption of Scrum]] | ||
| | | | ||
* 3.3 Impacts of time pressure by Product Owner or stakeholders and how to resolve | * 3.3 - Impacts of time pressure by Product Owner or stakeholders and how to resolve | ||
* 5.2 3 organisational impediments affecting Scrum teams | * 5.2 - 3 organisational impediments affecting Scrum teams | ||
* 5.3 Organisational design change caused by adopting Scrum | * 5.3 - Organisational design change caused by adopting Scrum | ||
|- | |- | ||
|[[Extreme Programming (XP)]] | |[[Extreme Programming (XP)]] | ||
| | | | ||
* 3.5 3 development practices | * 3.5 - 3 development practices | ||
|- | |- | ||
|[[Technical Debt]] | |[[Technical Debt]] | ||
| | | | ||
* 3.4 Technical Debt | * 3.4 - Technical Debt | ||
|} | |} | ||
Revision as of 03:35, 15 March 2022
Here is a suggested coaching syllabus to cover the Scrum Master 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 |
|
| Scrum Master As A Facilitator |
|
| Scrum Master As A Coach |
|
| Adoption of Scrum |
|
| Extreme Programming (XP) |
|
| Technical Debt |
|