Scrum: Scaling Concepts and Rules
Über den Vortrag
Der Vortrag „Scrum: Scaling Concepts and Rules“ von Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider ist Bestandteil des Kurses „Sprint 4“.
Quiz zum Vortrag
When scaling Scrum teams, what primary approach should an organization take?
- Divide the organization into several independent Scrum teams and have them develop in parallel.
- Plan scaling based on theoretical models and best practices from other companies.
- Start scaling with a single team and add more teams only after successful implementation.
- Scale quickly and simultaneously with all teams in the organization to leverage synergies.
- Select a framework and implement it strictly throughout the organization.
Complete the following sentence: "Scaling should be avoided because..."
- ...all existing problems will become many times bigger.
- ...the scaling frameworks only concern the technical side, never the organizational side.
- ...the teams are usually no longer located in one place.
- ...Scrum, according to the Scrum Guide, is only designed for one team.
What is the most important thing you need to pay attention to when scaling?
- Know, interpret and live the Agile Manifesto and the Scrum Guide.
- Know, interpret and live the roles of PSM and PO.
- Know, interpret and live the Scrum values and agile principles.
- Know, interpret and live the sprint retrospective and review.
- Know, interpret and live the strengths of the feature teams.
What principle applies to organizing products in a scaled Scrum environment?
- The number of product backlogs should correspond to the number of development teams.
- Every product basically has exactly one product backlog, even if there are multiple teams.
- Each team should manage multiple product backlogs in parallel.
- Product backlogs should be shared flexibly between different products.
- Product backlogs should be organized by department, not by product.
How should teams ideally be structured in a scaled Scrum environment?
- According to existing departmental structures
- Following the value stream and focusing on feature teams
- After the availability of Scrum Masters
- According to geographical proximity of team members
- According to technical specializations of the team members
Where should the scaling process begin?
- By building additional development teams
- With the creation of new management levels for coordination
- By scaling the volunteer teams as simultaneously as possible
- By considering what can be descaled
- With an analysis of which teams are suitable for scaling
Dozent des Vortrages Scrum: Scaling Concepts and Rules
Dipl.-Wirtschafts.-Ing(FH), M.Sc. Sebastian Schneider
Sebastian Schneider arbeitet seit 2005 mit dem agilen Projektmanagement Framework Scrum, hat eine Vielzahl von Projekten selbst als Product Owner, Scrum Master, Agile Coach und Certified Team Coach (Scrum Alliance) begleitet und berät seit 2011 Kunden in unterschiedlichen Branchen mit Schwerpunkt Automotive. Mit dem ScrumKurs24.de stellt er eine Wissensbasis rund um Scrum zur Verfügung und hat es sich zur Aufgabe gemacht, Kunden zu befähigen Produkte zu entwickeln, die deren Kunden lieben!Kundenrezensionen
5,0 von 5 Sternen
| 5 Sterne |
|
5 |
| 4 Sterne |
|
0 |
| 3 Sterne |
|
0 |
| 2 Sterne |
|
0 |
| 1 Stern |
|
0 |
