A quick look at how software development organizations have been typically organized over the decades, where we are going, how DevOps fits in the journey, and what DevOps feels like for the people involved.

1. Foodforthoughtpresents:
What the DevOps?
A view to developments in the software industry in the last decades
And
What does it mean for an engineer to DevOps?
Towo Toivola / Ferrix Hovi

2. © F-Secure Confidential2
 This presentation is based on
similar grounds as Dr. Royce’s
article, but more of it.
TowoToivola
Junior programmer, system administrator, lead
test engineer, Scrum Master, team manager,
organizational efficiency director

3. © F-Secure Confidential3
FerrixHovi
Senior software engineer, test automation engineer, live-team engineer, Scrum Master

4. Worldinthe1980’s
© F-Secure Confidential4
Intentions
System

5. © F-Secure Confidential5

6. Splittheelephant
© F-Secure Confidential6
I am the
customer
I sell you
software
I manage the
product
I run the
system
I test
software
I program
software
I define
architecture
I support the
product
$

7. Excellent!
Splittheproblemto
understandablepieces.
Leveragethepowerof
specialization.
© F-Secure Confidential7

8. Not so
excellent..
© F-Secure Confidential8

9. Each gap from a specialized group to another causes:
 Breakdown of communication and understanding about the system
 Detailed documentation was no cure
 Slower feedback for work products
 How soon will you really know if you were successful?
 Responsibility taking on only own part of the chain
© F-Secure Confidential9
Disadvantagesof
traditionalorganization

10. Systemunderstanding
Systemresponsibility
Feedback
© F-Secure Confidential10
=PAIN

11. Newpain
© F-Secure Confidential11
I am the
customer
I sell you
software
I run the
system
I test
software
I program
software
I define
architecture
I support the
product
$
PAIN
PAIN
PAIN
PAIN
PAIN
PAIN
I manage the
product

12. What causes
the pain
between
boxes?
© F-Secure Confidential12

13. Different process,
different boss,
different room,
different goals,
different priorities© F-Secure Confidential13

14. We have made a
number of
improvements
over the years
© F-Secure Confidential14

15. Webringprogramming
andtestingtogether
© F-Secure Confidential15
I am the
customer
I sell you
software
I run the
system
We develop
software, ensuring
quality
I define
architecture
I support the
product
$
PAIN PAIN
PAIN
PAIN
PAIN
I manage the
product

16. Webringproduct
ownershipneartheteam
© F-Secure Confidential16
I am the
customer
I sell you
software
I run the
system
We develop
software, ensuring
quality
I define
architecture
I support the
product
$
PAINPAIN
PAIN
PAIN
I manage the
product with
engineers

17. Webringarchitecture
ownershiptotheteam
© F-Secure Confidential17
I am the
customer
I sell you
software
I run the
system
We design and develop a
complete software product,
ensuring quality
I support the
product
$
PAIN
PAIN
PAIN
I manage the
product with
engineers

18. Weenableownershipofa
serviceinateam
© F-Secure Confidential18
I am the
customer
I sell you
software
We design and develop a complete
software system, ensuring quality of the
service
I support the
product
$
PAIN
PAIN
I manage the
product with
engineers

19. Can you see
where this is
going?
© F-Secure Confidential19

20. Where is this
easy?
© F-Secure Confidential20

21. Smallcompanies
© F-Secure Confidential21
I am the
customer
...sell, define, design and develop a
complete software system, ensuring quality
of the service, supporting our users
$
We are not too many people, so
we better all work together,
with our expertize, to..

22. Where is this
hard?
© F-Secure Confidential22

23. In our
companies
© F-Secure Confidential23

24. Our size,
Our legacy
thinking
© F-Secure Confidential24

25. Summasummarumpart1:
Thisisapartofanon-going
trektofigureoutand
rationalizesoftwaremaking
organizationsandprocess
© F-Secure Confidential25

26. Summasummarumpart2:
Weshouldstillleverage
specialization,butweneed
toensurethewholeworks
togethersmoothly
© F-Secure Confidential26

27. And now to
concretia..
© F-Secure Confidential27

28. IT HURTS
How does it feel to DevOps

29. DEVOPS IS
NOT ONLY A
PROCESS.
IT IS A
CHALLENGE.
© F-Secure Confidential29

30. IT IS
SUPPOSED
TO HURT. IT
IS A
MINDSET
CHANGE.© F-Secure Confidential30

31. WE ARE ALL
WRONG
WE ARE ALL
RIGHT
© F-Secure Confidential31

32. WE LACKED THE
CULTURE TO
RECRUIT WHO
WE NEED NOW
© F-Secure Confidential32

33. PERSPECTIVE
DISTANCE
© F-Secure Confidential33
Architect Developer Tester Sysadmin Support

34. FOR
OPERATIONS:
ETERNAL
SEPTEMBER
© F-Secure Confidential34

35. SEPTEMBER
 Who let these n00bs in as root?
 They have access and they won’t behave
 They have access and they won’t understand
 They have access and they mess things up
 THEY are in my backyard ruining my garden
They are not going anywhere, we need to change!
© F-Secure Confidential35

36. FROM
COMPLAINER
TO DESIGNER
© F-Secure Confidential36

37. FOR
DEVELOPERS:
ONE NIGHT
MIRACLE
© F-Secure Confidential37

38. MIRACULOUS
 What is this Linux anyway?
 What is hardening?
 I think we need a firewall.
 This monitoring could be better
 This deployment is actually tedious
© F-Secure Confidential38

39. FROM WORKS
ON MY
MACHINE TO
IMPROVING THE
SERVICE
© F-Secure Confidential39

40. FOR TESTERS:
ALL THESE NEW
REQUIREMENTS
© F-Secure Confidential40

41. REQUIREMENTS
 The environments have to work in production
 I need to fix what I find
© F-Secure Confidential41

42. FROM
CRITIC TO
OWNER
© F-Secure Confidential42

43. ALL WORK
NEEDS TO
HAPPEN IN THE
SAME AMOUNT
OF TIME
© F-Secure Confidential43

44. AMOUNT OF
USEFUL WORK
REMAINS THE
SAME
© F-Secure Confidential44

45. © F-Secure Confidential45
THEY COULD
HAVE DONE IT
ALL ALONG

46. NOW THEY
MUST CREATE
THE TOOLS
© F-Secure Confidential46

47. TAKE THE
PERSPECTIVE
… SUCCESSFULLY
AND ACT ON IT
© F-Secure Confidential47

48. © F-Secure Confidential48