Road To Devops - Telia Finland Story

1. Road to DevOps
Telia Finland story

2. Sami SöderblomSöderkulla, Finland
+358 40 302 4069sami.j.soderblom@teliacompany.com
sami.soderblom@gmail.com@pr0mille
"the adventures of a space monkey“
39 yrs, wife Malin, 3 yr old Vilja, 2 cats, jujutsu/BJJ,
disc golf, whiskies, etc.
26 yrs in work, 13 yrs in testing/quality work, 15+
business domains, 30+ projects, 500+ trained/coached
souls, etc.
Co-founder of Software Testing Finland and Happy
Monkey, DevOps Diplomat at Telia Finland.

5. EXPLICIT
KNOWLEDGE
TACIT
KNOWLEDGE
Data
Documents
Records Files
Experience
Thinking
Competence
Commitment
Deed
Intuition
Values
Context
Nuances
Community
Creativity
Understanding

8. Inverted Agile Manifesto
Processes and tools over individuals and interactions.
Comprehensive documentation over working software.
Contract negotiation over customer collaboration.
Following a plan over responding to change.

9. Fragile Robust Antifragile
Methodology “Spaghetti” ITIL DevOps
Attitude to change Fear Resist Embrace
Response to change Break Repel Adapt
Rate of change Ideally never Slow Rapid
Change initiation CTO approves Board User
Disaster recovery Days Hours Minutes
Method of recovery Find a person to fix Find & fix, rollback Self-heal, auto-rebuild
Focuses on Survival Process Business value

10. What is DevOps?
development
/dɪˈvɛləpm(ə)nt/
noun
The process of developing or being developed.
operation
/opəˈreɪʃ(ə)n/
noun
The action of functioning or the fact of being active or in effect.

11. What is DevOps?
DEV OPS

12. What is DevOps?
DEV OPS

13. Architecture and
technologies
appropriate. They enable
reaching business
targets efficiently.
Data collected from
product development
process are used as
basis for improvement.
(A)TDD/BDD and
exploratory testing in full
swing.
Development
organization
stakeholders meet
regularly. Metrics speed
up feedback cycle.
Continuous releases.
Predicted migration and
recovery processes.
Teams communicate and
work together
seamlessly, incl. IT
Operations.
Real-time data from
development supports
decision making and
tracking strategic
targets.
Technologies modern or
well supported.
Interfaces well
documented and exist
for key functionalities.
The status of
requirements can be
traced back to tests and
released features in real-
time.
UX/CX critical features
covered with automated
tests. (Exploratory)
testers also in dev
process.
Integration covers the
product and is
connected to UAT.
Dependencies known
and managed.
Environments installed
and configured
automatically. Build &
release process
automated.
Teams have liability for
Development and
Testing of product
features.
Easy to start new
development initiatives,
and they’re tied to
strategic targets.
Technologies growing
old. Architecture only
partially adaptive.
Interfaces lacking.
Visibility on code
integration, unit testing
and code analysis.
Unit testing and static
code analysis in place
for some parts.
Process automatic after
every change. Shared
tools. No testing in
integration.
System modular,
compiling environment
known, some releases
automated.
Work done in teams, but
Development and
Testing still separate.
Practices in place for
starting and steering
development initiatives.
Technology & tools
obsolete and not fit for
current requirements.
Reports made by hand
when necessary.
Testing conducted
manually and mainly
after development.
Product integration
automatic. Config and
deployment manual. No
artifact and change log
mgmt.
Products environment
specific and compiled
manually. Envs installed
and configured
manually.
Development,
Operations and Testing
as separate entities.
Communication mainly
in writing.
Development separated
from business. Hard to
start development
initiatives.
Architecture Visibility Testing Builds & CI Releases Culture Leadership

15. Tester
Business
ManagerDesigner
Developer
Monitoring
Support
Analytics
Infra

16. Cynefin
[ki-neh-vin]

17. Why DevOps?
Need
emerges
L E A D T I M E
P R O C E S S T I M E
Work
starts
Need
fulfilled
State of DevOps reports:
2016: 2555x faster
2017: 440x faster
Only about one-third of well-designed,
well-researched features in mature
products deliver top-line value to
organizations.

18. Why DevOps?
Continuous software
delivery over big
releases
Less complexity
Faster recovery from
problems
Happier, more
productive teams
Higher employee
engagement
Greater professional
development
opportunities
Faster delivery of
features
More stable operating
environments
Improved communication
and collaboration
More time to be
productive and innovate

19. Sample case
Source: Forecasting The Value Of
DevOps Transformations by DORA

21. W r a p u p

22. +358 40 302 4069
sami.j.soderblom@teliacompany.com
sami.soderblom@gmail.com
@pr0mille