The document outlines the principles of adopting a DevOps culture, emphasizing the need for organizations to identify signs of inefficiencies and resistance to change. It stresses the importance of fostering collaboration, positive leadership, and community engagement to overcome cultural hurdles in software development and operations. Recommendations include embracing a mindset of continuous improvement, encouraging teamwork across departments, and effectively communicating the need for change.

1. 1st DevOps Culture principle:
computer scientists
are only human
Jörg Hastreiter
Head of Business Technology

2.  Top 10 signs, that you have to change
something
 How we involve people and practice
positive leadership
 Our next step: Inner Source community
Agenda

3. Signs,
that you have to change something!Top10

4. Your development, test and operation tools
are absolutely incompatible and redundant …
Different toolsTop 10:

5. The go live of your "finished" software comes close
to an adventurous journey through a labyrinth ...
Expensive transitionTop 9:

6. You analyze in detail who has made the mistake
and sanction instead of learning from it ...
Finger pointing and no improvementTop 8:

7. Your software development, test and operation teams are
organizationally and geographically separated and talk
about each other but not to each other...
Too much tailorizationTop 7:

8. Your deployment to production depends on the heroic
commitment and genius of a single employee ...
Dependence on heroismTop 6:

9. You need 100 testers to complete the manual quality assurance for the
monthly release within a week ...
No test automationTop 5:

10. To restart a virtual server, you must complete
a six step approval process ...
Bureaucratic processesTop 4:

11. The installation of your software in operation takes as long as
printing and retyping the complete source code …
Manual deploymentsTop 3:

12. The go live of your software is delayed and falls with the
retirement of the user at the same time ...
Time to market missedTop 2:

13. Yan Weihao* has an appointment with your software and operation
teams and wants to learn how to play ping pong even faster ...
Constant ticket ping pongTop 1:
* World Champion of Ping Pong 2017

14. How we involve people and
practice positive leadership
Involve
People

15. Our main points of resistance
WillI still be
needed?
CanIdo
it?
What‘sthe
point?
Fears
Dev/TestTools
Ops Tools
Development
(Agile)
Agil – Fast–Proven
Operating
(ITIL)
Certified standards
Different
Tools
Different
Processes
Cultural
Hurdles
Flexibility&Agility
System security&stability
One goal
Divisionthinking
More efficient
together
Not inventedhere-
Syndrome
Inventingtogether
Organ. hurdles
& conflicting goals
Different goals &
responsibilities
d
o
i
a
m
d
o
p
u
p
p
e
t
d
o
i
m
a
g
e
d
o
m
y
s
e
r
v
Improvement of
standards &
automation
Project business
(Cost&timepressure)
Conflicts of
Resources
Wall of Confusion

16. Devops is not just technology – it is a
cultural change
16
Enterprise DevOps Adoption isn´t
mandatory – but neither is survival.
Gene Kim
You can´t directly change culture.
But you can change behavior, and
behavior becomes culture.
Lloyd Taylor, VP Infrastructure, Ngmoco
It feels right because it´s good for
your people.
Damon Edwards
DevOps is a human problem.
Patrick Dubois

17. Attention: Change!
Important: turn
concerned employees
into involved employees
Image source: http://www.change-management-consultant.de/wp-content/uploads/2016/02/Change_Management.jpg

18. Image source: http://www.change-management-consultant.de/wp-content/uploads/2016/02/Change_Management.jpg
Info-Lunches
Intranet
presentations
Show INFO VIDEOs about
the Vision
Employee
survey
Roadshows
Informal
discussions
Dev Day
Participation in the
program
Our Way: TURN CONCERNED EMPLOYEES into
involved employees

19. Our Way: TURN CONCERNED EMPLOYEES into
involved employees
19
Community
management and
incentive
mechanisms.
Knowledge
tandem advice
Know how-
exchange.
Consideration of
the requirements
and participation
of the community.
Trainings for
innovative
Dev/Test/Ops
tools and
processes.
Open Source
Use the practices
internally (= Inner
Source ).
Job rotation
Into the DevOps-
team and back.

20. Our Way: master the digital transformation
together
20
Piloting of new
microservices /
full-service
organizational
forms (Dev + Test +
Ops in one unit).
Employee survey
Finding out how
changes can be
implemented in
practice.
Standardized
processes along
the Dev-Test-Ops
value chain.
Employees from
various roles and
areas are
participants in the
DevOps change
program.
Standardized
Continuous
Integration and
Continuous
Delivery Tool
Chain.
Communication
Roadshows
Info lunches
Info videos
DevDay
d
o
i
a
m
d
o
p
u
p
p
e
t
d
o
i
m
a
g
e
d
o
m
y
s
e
r
v
d
o
i
a
m
d
o
p
u
p
p
e
t
d
o
i
m
a
g
e
d
o
m
y
s
e
r
v
Full-Service

21. Find and Talk about your
Success stories!
Start small.
But start the change!

22. DevOps Community
Inner Source Community
Our
Future

23. Preparation Implementation Acceptance
Motivation
0.Worry
Time
1.Alarm/Shock
2.Defensiveness
3.Rationalunderstanding
4.Emotionalunderstanding,
frustration
5.Opening
6.Integration
Based on next level consulting
change processes
Startofcompanywide
DevOpsprogramin2015
Weare
herenow…

24. Outlook:
We Establish a devOps Community
• Our DevOps community is decentral organized and good at getting better.
• We work together interdisciplinary and cross departmental on the
development of our methodologies.
• Together, we develop tools and services that enable us to automate,
standardize and deliver high quality services from A-Z.
Community mission:

25. DevOps Community
get employees involved
Motivation at community level, e.g.:
 Evolutionary user status (e.g. User  Contributor  Committer)
 Encourage users to collaborate and generate content
 Account assignment and budget for controlled development of the framework
 Prioritization of budget use by the community under benefit assessment
 Employees are visible as recognized experts
 Motivation at the individual level by executives when the DevOps Framework Services
have successfully applied in customer projects
 Recognition "Top Community Members"

26. Some recommendationsFinally

27. recommendations
 Don’t try to be ready with your DevOps implementation to a certain
milestone. Try to “be good in continuous getting better”.
 Share success stories loudly and proudly.
 Don’t force it. No one likes to be told what to do. Try to explain the
“Why?” Try to practice PERMA.
 Try to avoid political struggles and connect “DevOps minded” colleagues.
 Let teams work together across disciplines and make the entire team
responsible for the success.
 Shape you own company DevOps transformation story.
 DevOps is your approach, to bring agility to the customer.

28. Thank
you.
Jörg Hastreiter
Head of Business Technology
& Excellence
T-Systems Multimedia Solutions GmbH
Riesaer Straße 5
D-01129 Dresden
Phone: +49 351 2820 2824
Mobile: +49 151 1211 7750
E-Mail: Joerg.Hastreiter@t-systems.com
Internet: www.t-systems-mms.com