short introduction to large scale scrum less
TRANSCRIPT
LeSS – Large Scale Scrum
A short intro to LeSS
“There is no question that the cost of production is lowered by separating the work of planning and the brain work as much as possible from the manual labor“
Frederick Taylor
What it is actually about…
Roles
Team-based Organizations
Learning humans over “one-skill resources”
Teams over individuals as unit of ‘resourcing’
Give work to creative teams over Creating teams around work
Stable organizations over dynamic matrixed structures
Guidelines
Spec
ialis
atio
n
in te
chno
logy
Specialisation in customer domain
Most Traditional
TeamsProbably more
preferable
Team = Development-Team
Product Owner
Single Team Scrum Large Scale Scrum
PO is the single person responsible for the team working
on items with the highest ROI
PO is the single person responsible for the team working
on items with the highest ROI
PO clarifies PBIs with the teamPO connects team with users /
stakeholders needed for clarification
PO accepts / rejects the work PO typically accepts anything that fulfils the DoD
Roles & Backlogs
PO
Product Backlog
Item 1Item 2Item 3 Item 4Item 5Item 6Item 7Item 8Item 9
…
Sprint Backlog 1
Item 1Item 4Item 5 Item 8
Team 1
Sprint Backlog 2
Item 2Item 7Item 9 Item 10
Team 2
Sprint Backlog 3
Item 3Item 6Item 11
Team 3
1 Product Backlog Sprint backlog per team
SM
SM
Up to 8 dev. teams
1 Scrum Master per 1-3 teams
Huge-LeSS
PO
Product Backlog
Epic 1
Epic 2
Epic 3
Epic 4
Epic 5
Epic 6
…
Activation PO
Retention PO
Activation Backl.Epic 1, Item 1Epic 1, Item 2Epic 3, Item 1Epic 3, Item 2Epic 3, Item 3Epic 1, Item 3Epic 1, Item 4Epic 1, Item 5Epic 1, Item 6
…
Retention Backl.Epic 2, Item 1Epic 2, Item 2Epic 4, Item 1Epic 4, Item 2Epic 4, Item 3Epic 2, Item 3Epic 2, Item 4Epic 2, Item 5Epic 2, Item 6
…
…4-8
feature teams
Five relationships of the PO
PO
Customers
Team
SM
Higher Management
Clarification of PBIs
Events
Events with Representatives
Meeting Planning OneOverall Product
Backlog Refinement
Overall Retrospective
ParticipantsPO + Team
Representatives + SM
PO + Team Representatives +
SM
PO + SM + Team Representatives +
(Managers)
Activities/Focus
- Teams apportion items
- clear open questions - discuss coordination
for upcoming sprint
- Split big items - lightweight analysis for
basic understanding - estimate - identify strongly related
items and apportion items to teams
- issues common to all teams: closeness to customer, CoP, coordination, systematic organisational issues
- Is PO doing well?
Definition of Done
Extending “Done” to cover potentially shippable
Implement Code
Implement Integration Tests
Implement Unit Tests
Today 2 years 5 years 10 years
analysis & design
customer tests
customer doc
performance tests
marketing material
production
Needed to be potentially shippable
Why I like it
1. The minimal rules to kick-off learning in larger org.
2. Real decision authority, that I’ve rarely experienced 1. Very important efficiency gain is possible (Pareto rule)
3. Real product quality ownership of the teams 1. Enables real motivation 2. Enables real learning 3. Allows to tap into the cognitive potential of all employees
4. Honesty about feature teams | DoD vs. potentially shippable
Anton Skornyakov Coach for Agile Product
Development
@antonskornyakov www.agile.coach
BackUp
Principles
QUEUEINGTHEORY
SYSTEMSTHINKING
LEANTHINKING
CONTINUOUSIMPROVEMENTTOWARDSPERFECTION
EMPIRICALPROCESSCONTROL
LARGE-SCALESCRUMISSCRUM
WHOLEPRODUCTFOCUS
CUSTOMERCENTRIC
MOREWITHLESS
TRANSPARENCY
Coordination (= Integration)Nr. 1: Just Talk
Communicate in Code- social coding tools: github/gitlab- Have a CI & highly visible build results
Scrum of Scrum - SoS only means of last resort
Communities of PracticeTravelersComponent Guardians (mentors not quality gate keepers)
Leading Team Approach, when needed to sync with externals
Scrum Master
1. Question 2. Educate 3. Facilitate 4. Actively do nothing (observe) 5. Interrupt
DO’s1. Remove impediments (thats
for the team to do) 2. Never suggest one thing (if
you must suggest, suggest a lot of things
DONT’s
Team vs. manager responsibilitysetting overall
direction
designing the team and its
organisational context
Monitoring and managing work and progress
Execute team tasks
Manager-led teams
Self-Managing teams
Self- Designing
team
Self-Governing
teams
Management responsibility
Team’s own responsibility
Changing from manager-lead teams to self-managing teams has huge implications on the role of managers. It means that:
• the team checks whether they are on track (monitor the progress) • the team takes action when not on track (manage the progress) • the team decides how to work (managing the process) • the team resolves team conflict and fixes problems in the team (monitor and manage the process)