-
Scrum origins9 Topics
-
Grow as a Scrum Master, become a leader5 Topics
-
Scrum Team7 Topics1 Quiz
-
Service to the Product Owner8 Topics
-
Service to the Organisation7 Topics2 Quizzes
-
Scrum Master as a Facilitator1 Topic
-
Scrum Master as a Coach4 Topics1 Quiz
-
Scaling Scrum6 Topics3 Quizzes
-
eXtreme Programming4 Topics
-
Kanban5 Topics2 Quizzes
-
More Practice, More real life examples1 Topic
Quizzes
Participants 1
5.3 recognize at least two approaches to scaling Scrum.
Examples of approaches are LeSS, SAFe, Scrum at Scale, Enterprise Scrum, Spotify, Nexus. We are aware that some of these approaches are actually not scaling Scrum but embedding Scrum-like work processes into a different structure. Students should be able to recognize these approaches by having indicators; for instance, having a single Product Owner for multiple teams points to a LeSS-like adoption; having a Nexus team is pointing to Nexus, etc.
5.4 describe at least two reasons why an organization might decide not to scale.
Examples for reasons why not to scale: learning curves; adaptivity and agility; information loss; communication clutter.
5.6 describe at least three benefits and drawbacks of feature teams and component teams.
Examples for benefits of feature teams: Product Backlog can contain actual user requirements or stories; less dependencies between teams; planning is sped up because of team capabilities. Examples for benefits of component teams: compatible with existing structures; consistency within
components; knowledge transfer about technologies easier.
Bonus : Feature factory to Product outcome