The document discusses the need for a holistic view when scaling agile organizations. It covers topics like the problems of scaling agile, what constitutes a scaled agile organization, and how individuals can contribute to its success. The keynote speaker advocates adopting a networked structure over hierarchical ones and emphasizes quality being everyone's responsibility through cross-functional teams and a whole product focus.

1. The
Need
for
a
Holis/c
View
Keynote
by
Cesario
Ramos
cesario@agilix.nl
@cesarioramos

3. Topics
• The
problems
of
Scaling
Agile.
• What
is
a
scaled
Agile
organiza/on?
• How
can
you
contribute
to
it’s
success?

4. ENIAC

6. SoIware
Crisis
The
Major
Source
of
the
soIware
crisis
is
that
machines
have
become
several
orders
of
magnitude
more
powerful.
1972
-­‐
E.W.
Dijkstra
• OS/360

7. “We
need
to
discipline
the
SoIware
Engineering
Profession”

8. Func/onal
Specialisa/on
Head
BA
UI
Arch
Test
Domain
Staff

11. GATE
1
STAGE
1
GATE
2
STAGE
2
GATE
3
STAGE
3
GATE
4
STAGE
4

12. Development?
Systemic
Mechanis6c
Sum
Of
The
Parts
Product
of
Interac6on

13. Systemic
1. There
are
many
places
where
making
the
performance
of
the
part
worse
will
improve
the
performance
of
the
whole.
2. Performance
of
a
system
depends
on
how
the
parts
interact,
never
on
how
the
parts
act
separately.
Proff.
R.
Ackhoff

14. Test
Separa/on
Tes/ng
should
always
be
done
by
an
outside
party
who
is
somewhat
detached
from
the
program
and
project.
System
tes/ng
should
always
be
done
by
an
independent
group
such
as
a
separate
QA
department.
Glenford
J.
Meyers
Maturity
GOAL:
Establish
a
Test
Organiza/on

15. Component
Specialisa/on
Head
A
B
C
D
E
F
Staff

16. Component
Teams
A
B
C
F
D
E
F1
F2
F3
F4
F5
F6
Feature
Backlog

17. Component
Op/miza/on
A
B
C
F
D
E
F1
F2
F3
F4
F5
F6

18. Component
Op/miza/on
A
B
C
F
D
E
F1
F2
F3
F4
F5
F6

19. Component
Op/miza/on
A
B
C
F
D
E
F1
F2
F3
F4
F5
F6

20. Component
Op/miza/on
F1
F2
F3
F4
F5
F6
A
B
C
F
D
E

21. Component
Op/miza/on
A
B
C
F
D
E
Who
does
tes6ng?
Who
does
analysis?
Who
does
architecture?
Who
does
coordina6on?
How
do
you
measure
progress?

23. WE
GOT
IT
TO
WORK
FOR
ONE
TEAM…

24. What
is
scaled
agile?

25. #1:
Scrum
Teams
Skills
Code,
Analysis,
Test
Skills
Analysis,
Tes/ng
Skills
Tes/ng,
Code
Skills
UIX,
Tes/ng
Skills
Code,
Automa/on
Skills
Business
Domain,
Tes/ng
Skills
QA,
automa/on

26. #2
Customer
Centric
Features

27. Feature
Team
Learning
A
B
C
F
D
E

28. Feature
Team
Learning
Audio
/
Video
A
B
C
F
D
E

29. #3
Cross
Component
Teams
A
B
C
F
D
E

30. #4
Whole
Product
Focus

31. Example:
Whole
Product
Focus
• 70+
people
• 8+
teams
• One
Sprint.
• One
Defini/on
Of
Done.
• One
Product
Increment.
• One
Sprint
Planning
• One
Sprint
Review

32. From
Hierarchical
Structure
Mgr
Comp.
Team
Mgr
Comp.
Team
Mgr
Comp.
Team
Mgr
Comp.
Team
Mgr
Comp.
TeamComp.
Team
Comp.
Team
Comp.
Team Comp.
Team
Mgr
Mgr
Head

33. #5:
To
a
Networked
Structure
Line
Mgr
Line
Mgr
Head
=
PO
Team
Team
Team
Team
Team
Team
Team

34.
Why
aren’t
there
any
test
roles
in
Scrum?
?

35. #6:
Quality
is
everybody's
responsibility
• Mul/
skilled
QA
professionals
• QA
as
a
Service
• Analyse
customer
feedback
• Discover
customer
needs
• Coach
Team
members
on
tes/ng
• And
the
other
things
testers
do…

36.
“Tes/ng
is
the
process
of
execu/ng
a
program
with
the
inten/on
of
finding
errors”
Meyers
G,
The
Art
of
SoRware
Tes6ng,
page
11
The
role
of
the
tester?

37. Agile
QA
Professionals
Needed!!
• Successfully
Scale
Agile.
• Validate
business
specula/ons.
• Service
your
teams
to
prevent
making
the
wrong
thing
faster.
• Facilitate
discovering
how
to
build
the
right
thing
right.

38. MORE
LESS
Learning
&
adapta/on
Prescrip/on
&
Following
Flow
Of
Value
Resource
Op/miza/on
Feature
Teams
Roles,
Silos
&
Layers
Coaching
&
Mentoring
Telling
and
showing
Preven/ng
Detec/ng
Openness
&
Transparency
Fear
&
Secrecy
Scaled
Agile
Organiza/on

39. Cesario Ramos
cesario@agilix.nl
http://agilix.nl
AgiliX Agile Consulting
To
be
published
THANK
YOU!

40. The
Need
for
a
Holis/c
View
Keynote
by
Cesario
Ramos
cesario@agilix.nl
@cesarioramos