When more than 10 people are needed to reach a goal multiple agile teams are needed. These teams have to coordinate - we have to scale agile. There are several blueprints for scaling agile. This session argues that using a blueprint is premature optimization. When looking at successful agile companies one thing becomes clear: they didn't follow a blueprint but implemented unique structures and processes. Every company is unique and needs unique structures and processes matching its purpose. In this talk Stefan presents the Agile Scaling Cycle, an organic approach to find and optimize scaling structures appropriate for the company.

1. Agile Scaling
without
Blueprints
Goto, Berlin,
04-dec-2015
Stefan Roock
stefan.roock@it-agile.de
@StefanRoock
Track: On the Boundaries of Agile

2. Scaling in the „good old days“™
(∼2005)
4 teams, 20-25 developers
from 3 companies
13 teams, 65 developers
from 3 companies

3. Sprint
Backlog
Product
Owner
Vision
Scrum
Master
Daily
Scrum
Sprint
Review
Sprint
Planning
Product
Backlog
Sprint
Product
Increment
Sprint
Retro-
spective
Development
Team
Just Scrum?

4. Sprint
Backlog
Product
Owner
Vision
Scrum
Master
Daily
Scrum
Sprint
Review
Sprint
Planning
Product
Backlog
Sprint
Product
Increment
Sprint
Retro-
spective
Development
Team
Just Scrum+XP
Pair
Programming
Continuous
Integration
Test Driven
Development
On-site Customer
On-site Team
Collective
Ownership

5. Scaling today

6. Agile in the
old days
Deliver useful software
every few weeks with
Scrum & XP.
At least we
suck less.
Agile
nowadays
t
2000-2005
2015
I have the
greatest job
ever.
SAFe
DAD LeSS
…

7. Agile in the
old days
Deliver useful
software every
few weeks.
At least we
suck less.
Agile
nowadays
t
2000-2005
2015
I have the
greatest job
ever.
WTF?
SAFe
DAD LeSS
…

8. Insanity?

9. Cargo Cult

10. Agile in the
old days
Deliver useful
software every
few weeks.
At least we
suck less.
Agile
nowadays
t
2000-2005
2015
I have the
greatest job
ever.
Cargo
Cult
SAFe
DAD LeSS
…

11. Culture and principles are more
important than practices.

12. After years of research we
discovered the secret ingredient
for successfully scaling agile!

13. Secret ingredient for
successful scaling
Blueprint

14. Emergent structures with
the Agile Scaling Cycle
Coordinate
teams
Reduce
dependencies
Develop the
organization
Values
and
principles

15. Agile
Scaling
Cycle
Coordinate
teams
Reduce
dependencies
Develop the
organization
Agile: Autonomous
business focused
teams that own
their process.
Values
and
principles

16. X - Teams

17. Some practices for dependency reduction
Autonomy
Cross functional
Teams
Team MissionsOpen Allocation
Verticals
Sandboxing
Product
Definition
Definition of
DoneDefinition of
Ready
Modularization
Extend team
responsibility up-/
downstram
synchronized
Sprints
Release Train
Continuous
Delivery
Release Cadence
Product Owner
Beta Codex
low high
Market
Company
Teams
Technology

18. Agile
Scaling
Cycle
Coordinate
teams
Reduce
dependencies
Develop the
organization
Values
and
principles

19. Communities of Practice
Goal#1
Coordination practices
Time horizon
Numberofteams
Team Verløtung
Portfolio/Program Kanban
shared Sprint
Planning
shared Sprint Review
Continuous
Integration
shared Release
Planning
Visit Daily
Scrums
Scrum of
Scrums
consultative individual decision
Task-Forces
Open Prio Meeting
Hours Days Weeks Months
Launch Pate

20. Number of
coordination
practices that
aren’t needed
(any longer)
Stefans Agile Scaling Maturity Model

21. Agile
Scaling
Cycle
Coordinate
teams
Reduce
dependencies
Develop the
organization
Values
and
principles

22. Practices for organizational development
Transition team /
Agile Center
Transition
Backlog
Successful teams in
agile organization
organizational
impediments

23. Practices for organizational development
PDCA
Transition team /
Agile Center
Transition
Backlog
Theory of
Constraints
Lean
Thinking
Systems
Thinking
North
Star
Successful teams in
agile organization
organizational
impediments
Open Spaces
…
Gemba
Walks
Operations
Review
shared
Retrospectives

24. Find structures matching your business
…

25. see also: scaledprinciples.org
Summary

26. •Cultural change
•Emergent structures
•Inspect & adapt
•Self organization
•Team autonomy
•Process ownership
see also: scaledprinciples.org
Summary

27. Free ebook:
http://bit.ly/JimdoStory
Booklet about agile
scaling (german)
http://www.itagileshop.de/lesen/weitere-broschüren/luna/
More information

28. Thank you for your attention!
Stefan Roock
stefan.roock@it-agile.de
Twitter: @StefanRoock
Feel free to
contact me: