Difference between revisions of "LeSS Organization: Big Ideas and Organizational Design In Large-Scale Scrum"
(11 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
You will learn the big ideas in LeSS (Large-Scale Scrum), with a special focus on organizational design change implications. | You will learn the big ideas in LeSS (Large-Scale Scrum), with a special focus on organizational design change implications. | ||
+ | |||
== Audience == | == Audience == | ||
− | Since LeSS (and even regular one-team Scrum) implies an organizational design change, the '''primary audience is senior managers''' ( | + | Since LeSS (and even regular one-team Scrum) implies an organizational design change, the '''primary audience is senior managers''' (usually '''executive C-level managers''') who have the authority and ability to change the design, including the authority to eliminate or change groups, roles, policies and processes. |
+ | |||
A second key audience is '''ScrumMasters @ Scale''' who need to understand everything about Large-Scale Scrum and advise and educate senior leadership in the organizational design implications of LeSS. | A second key audience is '''ScrumMasters @ Scale''' who need to understand everything about Large-Scale Scrum and advise and educate senior leadership in the organizational design implications of LeSS. | ||
+ | |||
A third audience are people in the various '''traditional manager roles''' that are no longer needed in Scrum, including functional (analysis, test, architecture, UX, ...) managers, team leads, project and program managers. This course will explore what new roles and behaviors may be relevant. | A third audience are people in the various '''traditional manager roles''' that are no longer needed in Scrum, including functional (analysis, test, architecture, UX, ...) managers, team leads, project and program managers. This course will explore what new roles and behaviors may be relevant. | ||
+ | |||
A fourth audience are people in '''traditional single-specialist roles''' no longer needed in Scrum, since Scrum is based on multi-skilled multi-learning ''T-shaped'' workers. This course will explore what new roles and behaviors may be relevant. | A fourth audience are people in '''traditional single-specialist roles''' no longer needed in Scrum, since Scrum is based on multi-skilled multi-learning ''T-shaped'' workers. This course will explore what new roles and behaviors may be relevant. | ||
Line 22: | Line 26: | ||
== Outline == | == Outline == | ||
− | * Large-Scale Thinking, Organization, and Action Tools | + | * Large-Scale Scrum: Thinking, Organization, and Action Tools |
− | * | + | * Why LeSS? |
− | * | + | * Systems thinking |
− | * | + | * LeSS principles |
− | * | + | * LeSS rules |
+ | * LeSS guides | ||
+ | * The 2 LeSS frameworks: LeSS Framework & LeSS Huge Framework | ||
* Scaling with Requirement Areas | * Scaling with Requirement Areas | ||
+ | * Adopting LeSS: transition | ||
+ | * Organizing by customer value | ||
* Feature and component teams | * Feature and component teams | ||
* Scaling the Product Owner role, and Product Management | * Scaling the Product Owner role, and Product Management | ||
− | |||
* ScrumMasters @ Scale | * ScrumMasters @ Scale | ||
* Scaling the Definition of Done, and organizational design implications | * Scaling the Definition of Done, and organizational design implications | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Enterprise-level policies and systems that support agility | * Enterprise-level policies and systems that support agility | ||
* Architecture & design in LeSS | * Architecture & design in LeSS | ||
− | |||
− | |||
− | |||
− | |||
− | |||
== Maximum Participants == | == Maximum Participants == | ||
− | + | 35 | |
Line 58: | Line 53: | ||
== Environment - Room, Tools, Texts == | == Environment - Room, Tools, Texts == | ||
− | Read this: [[Course Environment - | + | Read this: [[Course Environment - LeSS]] |
'''Text and Notes''' | '''Text and Notes''' | ||
− | + | Participants will receive copies of 3 books: | |
+ | |||
+ | (1) '''Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum''' | ||
+ | |||
+ | (2) '''Practices for Scaling Lean & Agile Development: Large, Multisite & Offshore Product Development with Large-Scale Scrum''' | ||
+ | |||
+ | (3) (when published in late 2014) '''Large-Scale Scrum: More with LeSS''' |
Latest revision as of 01:46, 18 June 2014
Contents
Overview
2 days
You will learn the big ideas in LeSS (Large-Scale Scrum), with a special focus on organizational design change implications.
Audience
Since LeSS (and even regular one-team Scrum) implies an organizational design change, the primary audience is senior managers (usually executive C-level managers) who have the authority and ability to change the design, including the authority to eliminate or change groups, roles, policies and processes.
A second key audience is ScrumMasters @ Scale who need to understand everything about Large-Scale Scrum and advise and educate senior leadership in the organizational design implications of LeSS.
A third audience are people in the various traditional manager roles that are no longer needed in Scrum, including functional (analysis, test, architecture, UX, ...) managers, team leads, project and program managers. This course will explore what new roles and behaviors may be relevant.
A fourth audience are people in traditional single-specialist roles no longer needed in Scrum, since Scrum is based on multi-skilled multi-learning T-shaped workers. This course will explore what new roles and behaviors may be relevant.
Prerequisites
Understand all the concepts in standard 1-Team Scrum. (Some pre-readings will be assigned to facilitate this).
Outline
- Large-Scale Scrum: Thinking, Organization, and Action Tools
- Why LeSS?
- Systems thinking
- LeSS principles
- LeSS rules
- LeSS guides
- The 2 LeSS frameworks: LeSS Framework & LeSS Huge Framework
- Scaling with Requirement Areas
- Adopting LeSS: transition
- Organizing by customer value
- Feature and component teams
- Scaling the Product Owner role, and Product Management
- ScrumMasters @ Scale
- Scaling the Definition of Done, and organizational design implications
- Enterprise-level policies and systems that support agility
- Architecture & design in LeSS
Maximum Participants
35
Methods of Education
Discussion, presentation, Q&A, exercises
Environment - Room, Tools, Texts
Read this: Course Environment - LeSS
Text and Notes
Participants will receive copies of 3 books:
(1) Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
(2) Practices for Scaling Lean & Agile Development: Large, Multisite & Offshore Product Development with Large-Scale Scrum
(3) (when published in late 2014) Large-Scale Scrum: More with LeSS