Scrum im Großen und Ganzen
•
3 likes•890 views
This document discusses scaling Scrum to large organizations using the Large Scale Scrum (LeSS) framework. Some key points: - LeSS is based on 10 principles and has been used successfully in organizations with hundreds of people and multiple sites/locations. - It emphasizes feature teams that work on end-to-end slices of functionality rather than component-based teams. - Teams are self-organizing and self-designing. Additional structures include requirement areas, communities of practice, and impediment removal. - The framework maintains transparency and alignment through elements like sprint reviews, retrospectives, and coordination between teams and stakeholders.
Recommended
More Related Content
Viewers also liked
Similar to Scrum im Großen und Ganzen
Similar to Scrum im Großen und Ganzen (20)
More from Markus Gärtner
More from Markus Gärtner (16)
Recently uploaded
Recently uploaded (19)
Scrum im Großen und Ganzen
- 1. Text Scrum im Großen und Ganzen Markus Gärtner @mgaertne it-agile GmbH @itagile CONTINUOUS IMPROVEMENT COACHING GO SEE LEAN THINKING SYSTEMS THINKING PRINCIPLES FEATURE TEAMS TEAMS STRUCTURE ORGANIZATION TECHNICAL EXCELLENCE CONTINUOUS INTEGRATION ARCHITECTURE & DESIGN ROLE OF MANAGERS PRODUCT OWNER TEAM LESS HUGE ADOPTION REQUIREMENT AREAS MANAGEMENT COMMUNITIES SPRINT REVIEW RETROSPECTIVE OVERALL RETROSPECTIVE SPRINT PLANNING 1 WHY LeSS FRAMEWORK? PREVIOUS SPRINT NEXT SPRINT PRODUCT BACKLOG PRODUCT OWNER SPRINT BACKLOG SCRUMMASTER & FEATURE TEAM PRODUCT BACKLOG REFINEMENT DAILY SCRUM COORDINATION POTENTIALLY SHIPPABLE PRODUCT INCREMENT SPRINT PLANNING 2
- 2. The earliest large-scale software- intensive product development was the Semi-Automatic Ground Environment (SAGE) system. Created in the 1950s, it involved hundreds of people. What did a senior manager think of the development strategy?…
- 3. One of the directors of SAGE was discussing why the programming had gotten out of hand. He was then asked, “If you had it to do all over again, what would you do differently?” His answer was to “find the ten best people and write the entire thing themselves.” [Horowitz74]
- 4. Chet Hendrickson during Agile 2015: “I believe that in every 100 person project there is a 10 person project trying to get out.”
- 5. After many years working in large, multisite, & offshore development, our key advice? Large: don’t multisite: don’t offshore: don’t OK, you’re still gonna do it, so…
- 6. LeSS in a nutshell 600 Experiemente 50 Guides 3 Seiten Regeln 10 Prinzipien -> http://less.works CONTINUOUS IMPROVEMENT COACHING GO SEE LEAN THINKING SYSTEMS THINKING PRINCIPLES FEATURE TEAMS TEAMS STRUCTURE ORGANIZATION TECHNICAL EXCELLENCE CONTINUOUS INTEGRATION ARCHITECTURE & DESIGN ROLE OF MANAGERS PRODUCT OWNER TEAM LESS HUGE ADOPTION REQUIREMENT AREAS MANAGEMENT COMMUNITIES SPRINT REVIEW RETROSPECTIVE OVERALL RETROSPECTIVE SPRINT PLANNING 1 WHY LeSS FRAMEWORK? PREVIOUS SPRINT NEXT SPRINT PRODUCT BACKLOG PRODUCT OWNER SPRINT BACKLOG SCRUMMASTER & FEATURE TEAM PRODUCT BACKLOG REFINEMENT DAILY SCRUM COORDINATION POTENTIALLY SHIPPABLE PRODUCT INCREMENT SPRINT PLANNING 2
- 7. Case Studies u.a. von Nokia Networks bwin.party JP Morgan Chase Agfa Healthcare Ericsson http://less.works/case-studies
- 8. Feature Teams vs. Komponenten Teams
- 11. Feature Team Adoption Map
- 14. Koordination
- 17. SPRINT REVIEW RETROSPECTIVE OVERALL RETROSPECTIVE SPRINT PLANNING 1 WHY LeSS FRAMEWORK? PREVIOUS SPRINT NEXT SPRINT PRODUCT BACKLOG PRODUCT OWNER SPRINT BACKLOG SCRUMMASTER & FEATURE TEAM PRODUCT BACKLOG REFINEMENT DAILY SCRUM COORDINATION POTENTIALLY SHIPPABLE PRODUCT INCREMENT SPRINT PLANNING 2
- 20. Requirement Areas business-fokussierte Anforderungsbereiche 4-8 Teams Area Product Owner basic LeSS-Organization pro Requirement Area
- 21. Text QUEUEING THEORY SYSTEMS THINKING LEAN THINKING CONTINUOUS IMPROVEMENT TOWARDS PERFECTION EMPIRICAL PROCESS CONTROL LARGE-‐SCALE SCRUM IS SCRUM WHOLE PRODUCT FOCUS CUSTOMER CENTRIC MORE WITH LESS TRANSPARENCY Prinzipien
- 22. Scaling Scrum starts with understanding and being able to adopt standard real one-team Scrum. Large-scale Scrum requires examining the purpose of single- team Scrum elements and figuring out how to reach the same purpose while staying within the constraints of the standard Scrum rules. — Craig Larman, Bas Vodde
- 23. Lesenswertes http://less.works http://featureteams.org 15.-17. März 2016 Certified LeSS Practitioner mit Bas Vodde http://www.it-agile.de/schulungen/certified-less- practitioner-principles-to-practices/