Interested in DevOps but not sure how to get started? Join us to explore the real meaning behind DevOps and how to begin your own DevOps Journey. Every organization is different, but DevOps is a universal concept, and it can be applied anywhere. We'll explore some common patterns and approaches, both technical and cultural that can get your organization started on their own adventure!

1. NOVEMBER 6, 2019
Fabian Iannarella
DevOps is a Journey:
Choose your own
adventure

3. DevOps is a Journey :
Choose your own adventure

4. About
Fabian Iannarella
fabian.iannarella@460degrees.com
:@fiannarella
: /in/fabianiannarella/
DevOps Champion
@ 460degrees

5. Today’s Adventure!
What is DevOps?
How to get started with DevOps?
A real life example!
AND inspire you to start your journey!
What will we discuss?

6. Why is DevOps
important to you ?
Common answers I have heard
I’m too busy to talk about this right now!
Production releases are painful!
Everyone else is doing it!
There’s a DevOps team and nobody understands
what they do

7. (Developers + Operations)
DevOps =
Collaborating

8. What is
DevOps about?
Is it about technology?
Continuous Integration (CI)?
Software delivery?
The cloud?
Automation and tooling?

9. DevOps is a
way of
working
enabled by
technology
● Creating Cross Functional
Teams
● Delivering Customer Value
● Continual Improvement
● Feedback
It’s all about:

10. Build a Plan
& Start Small
Focus on :
● Pain Points
● Automation
● New Projects

11. Build a Plan
& Start Small
Then :
● Set some goals
● Measure them
● Enable teams
● Establish Collaboration

12. Build a Plan
& Start Small
Remember :
● Keep it simple
● Start small
● Share everything
● Find more Adventures

13. VehicleTelemetry
INTERNET
API
GPS
Frontend
Listener
IOT Device

14. MEETTHETEAMS
Infrastructure
Team
Tools used:
Testing
Team
Operations
Team
Software
Developers
Tools used:
Embedded
Team
Tools used:
EMBEDDED LINUX

15. ● Product delivery times
● We need to scale our product
● Data integrity
● Reliability
● Security
What’s
Important

16. Developers Build
Features
Release Created
Artifacts are handed
over to Infrastructure
Environment built and
handed over toTesters
Test specific new or modified
features. All tests are manual
Hand backs
if errors discovered
Successful Release, handed to
infrastructure.
Operations are notified and
assist in production releases.
Time ? 1 DAY 2 DAYS 5 DAYS
Manual Process = 8 days
Software Deployment & SupportSoftware Deployment & Support
2 DAYS
Software
Repository
Build issues

17. TECHNOLOGY
Opportunities for improvement
Quick Wins:
- Automate the build process
- Self service environment builds for Devs andTesters
Longer-term
- Build a framework to automate tests
- Load testing
Even Longer-term
- Platform re-architecture
- Micro Services or Serverless event driven system
- Containerisation

18. CULTURE
How to drive those improvements
CreateTeam(s) to build new capabilities
● Cross functionality: Include people from different teams
● Complement them with consultants or new starters
● Build these NEW capabilities using a customer centric approach
● Showcase your product!
**WARNING**
These teams could become another siloed team!

19. DeveloperInfrastructure
Tester
Consultant or
new starter
MeetThe CapabilitiesTeam
Building things to help other teams go faster

20. Meet the Actual CapabilitiesTeam
On Demand
DevelopersInfrastructure
Testers
Consultants
Test
Automation
DevOps DevOps
Test
Automation
On Demand
On Demand

21. Risks:
- Regression when contractors leave
- Experiences and Knowledge is not transferred other teams
Countermeasures:
- Place permanent staff member in charge of the initiative
- Regular showcases
- Constant communication and conversations
CULTURE
Risks and Countermeasures

22. Infra Code
& Config
Commit
Create
Cloudformation
Provision Env
Building Infrastructure pipelines
Keeping it simple
1 2 3

23. Code
Commit
Build Provision
Test Env
Building software pipelines
Keeping it simple
1 2 3

24. Code
Commit
Build Provision
Test Env
E2E
Testing
Load
Testing
Building pipelines
Extended
1 2 3 4 5

25. Manual vs Automated
2 daysTotal 10 Days 1 Day 5 days
Total 2 Days
1.75 hrs
Manual Process = 8 days
Automated Process = 1.75 hrs
15mins 30mins
2 days
2 days30mins30mins
Code
Commit
Build Provision
Test Env
E2E
Testing
Load
Testing
1 2 3 4 5
Manual

26. Lets Recap
● Work out what’s important
● Measure your progress
● Build a team & encourage collaboration
● Start small and iterate
● Share everything
● Choose your next adventure

27. Fabian Iannarella
fabian.iannarella@460degrees.com
: @fiannarella
: /in/fabianiannarella/
DevOps Champion
@ 460degrees