Scrum Master Learning Objectives: Difference between revisions
Jump to navigation
Jump to search
| Line 146: | Line 146: | ||
|Sprint and Increment | |Sprint and Increment | ||
|Sprint Goal does not change during Sprint | |Sprint Goal does not change during Sprint | ||
|Sprint Planning & Backlog Refinement | |Sprint Planning & Product Backlog Refinement | ||
|- | |- | ||
|1.8 | |1.8 | ||
| Line 160: | Line 160: | ||
|1.10 | |1.10 | ||
|Sprint Planning | |Sprint Planning | ||
| | |Activities during Sprint Planning | ||
| | |Sprint Planning & Product Backlog Refinement | ||
|- | |- | ||
|1.11 | |1.11 | ||
|Sprint Planning | |Sprint Planning | ||
| | |Sprint Goals | ||
| | |Sprint Planning & Product Backlog Refinement | ||
|- | |- | ||
|1.12 | |1.12 | ||
|Daily Scrum | |Daily Scrum | ||
| | |3 ways the Daily Scrum differs from a status reporting meeting | ||
| | |Daily Scrum | ||
|- | |- | ||
|1.13 | |1.13 | ||
|Sprint Review | |Sprint Review | ||
| | |3 Activities other than demo in a Sprint Reivew | ||
| | |Sprint Review | ||
|- | |- | ||
|1.14 | |1.14 | ||
|Sprint Review | |Sprint Review | ||
| | |3 outcome from a Sprint Review | ||
| | |Sprint Review | ||
|- | |- | ||
|1.15 | |1.15 | ||
|Sprint Retrospective | |Sprint Retrospective | ||
| | |2 approaches for a Sprint Retrospective | ||
| | |Sprint Retrospective | ||
|- | |- | ||
|1.16 | |1.16 | ||
|Product Backlog | |Product Backlog | ||
| | |3 characteristics of the Product Backlog | ||
| | |Product Backlog | ||
|- | |- | ||
|1.17 | |1.17 | ||
|Product Backlog | |Product Backlog | ||
| | |4 attributes of a Product Backlog Item | ||
| | |Product Backlog | ||
|- | |- | ||
|1.18 | |1.18 | ||
|Sprint Backlog | |Sprint Backlog | ||
| | |3 characteristics of the Sprint Backlog | ||
| | |Sprint Backlog | ||
|- | |- | ||
|1.19 | |1.19 | ||
|Sprint Backlog | |Sprint Backlog | ||
| | |How the Sprint Backlog can change preserving the Sprint Goal | ||
| | |Sprint Backlog | ||
|- | |- | ||
|1.20 | |1.20 | ||
|Definition of “Done” | |Definition of “Done” | ||
| | |2 risks of weak Definition of Done | ||
| | |Definition of Done | ||
|- | |- | ||
|1.21 | |1.21 | ||
|Definition of “Done” | |Definition of “Done” | ||
| | |How to create a Definition of Done | ||
| | |Definition of Done | ||
|- | |- | ||
|1.22 | |1.22 | ||
|Definition of “Done” | |Definition of “Done” | ||
| | |Why multiple teams need to work to the same Definition of Done | ||
| | |Definition of Done | ||
|- | |- | ||
|2.1 | |2.1 | ||
Revision as of 06:05, 2 December 2021
Foundation Learning Objectives
| ID | Classification | Learning Objective | Session Mapping |
|---|---|---|---|
| 1.1 | Scrum Theory | Scrum and Agile Manifesto | Agile Manifesto |
| 1.2 | Scrum Theory | Scrum and its Purpose | Scrum Framework |
| 1.3 | Scrum Theory | 5 Scrum Values | Scrum Values |
| 1.4 | Scrum Theory | 3 Pillars of Empirical Process Control | Empirical Process Control |
| 1.5 | Scrum Theory | Traditional vs Empirical Product Planning | Deterministic vs Empirical Product Planning |
| 1.6 | Scrum Theory | Scrum in its Entirety | Scrum Framework |
| 1.7 | Scrum Theory | Iterative and Incremental Approaches | Iterative and Incremental |
| 2.1 | Scrum Roles | How Scrum Roles Interact | Scrum Roles |
| 2.2 | Scrum Roles | Cross Functional and Self Organising Teams | Scrum Roles |
| 3.1 | Scrum Events | Timeboxing |
|
| 3.2 | Scrum Events | 5 Scrum Events |
|
| 4.1 | Scrum Artefacts | 3 Scrum Artefacts |
|
| 4.2 | Scrum Artefacts | Definition of Done | Definition of Done |
| 4.3 | Scrum Artefacts | Product Backlog Refinement | Sprint Planning & Product Backlog Refinement |
| 4.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 |
|
| 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 Process Control |
| 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 Reivew | 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 | Product Backlog |
| 1.17 | Product Backlog | 4 attributes of a Product Backlog Item | Product Backlog |
| 1.18 | Sprint Backlog | 3 characteristics of the Sprint Backlog | Sprint Backlog |
| 1.19 | Sprint Backlog | How the Sprint Backlog can change preserving the Sprint Goal | Sprint Backlog |
| 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 | ||
| 2.2 | Facilitation | ||
| 2.3 | Coaching | ||
| 2.4 | Coaching | ||
| 3.1 | Scrum Master as Servant-Leader | ||
| 3.2 | Scrum Master as Servant-Leader | ||
| 3.3 | Scrum Master as Servant-Leader | ||
| 3.4 | Scrum Master as Servant-Leader | ||
| 3.5 | Scrum Master as Servant-Leader | ||
| 4.1 | Service to the Product Owner | ||
| 4.2 | Service to the Product Owner | ||
| 5.1 | Impediment Removal | ||
| 5.2 | Impediment Removal |