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!

2. DevOps is a Journey :
Choose your own adventure

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

4. Why is DevOps
important to you ?
Because :
We want to deliver value to our customers
We struggle with timely production releases
Everyone else is doing it!
There’s a DevOps team and nobody understands
what they do

5. What is
DevOps about?
Is it about technology?
CI/CD?
Software delivery?
The cloud?
Automation?
Puppet, Chef, Ansible, Jenkins,
kubernetes….?

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

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

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

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

10. Vehicle Telemetry
INTERNET
API
GPS
Frontend
Listener
IOT Device

11. MEET THE TEAMS
Infrastructure
Team
Tools used:
Testing
Team
Operations
Team
Software
Developers
Tools used:
Embedded
Team
Tools used:
EMBEDDED LINUX

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

13. Devs Builds Features
and pushes new code to
Software repo
The release is created
and the artifacts are built,
manually.
Artifacts are handed over
to infra to provision a
new test environment
Using Cloud formation,
PowerShell and some
manual processes Infra
build a new environment
and hand it to the testers
Testers only test specific new or
modified features to save time.
All tests are manual
Hand backs to
Developers and/or
Infrastructure, if issues are
found
Successful Release goes back to
infrastructure for production
release. A new release requires a
full rebuild and about a 20
minute outage.
Releases are manually staged
across different customers
Operations are notified of the
release schedule
Time ? 1 DAY 2 DAYS 5 DAYS
Manual Process = 8 days
Software Deployment & SupportSoftware Deployment & Support
2 DAYS
Software
Repository

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

15. CULTURE
How to drive those improvements
Create Team(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!

16. DeveloperInfrastructure
Tester
Consultant or new
starter
Meet The Capabilities Team
Building things to help other teams go faster

17. Meet the Actual Capabilities Team
On Demand
DevelopersInfrastructure
Testers
Consultants
Test
Automation
DevOps DevOps
Test
Automation
On Demand
On Demand

18. Building Pipelines : Keep It Simple
MVP Code
Commit
pipeline Manual
Test
Env
Provision
Test Env
Code
Commit
pipeline pipeline
Build
(run unit
Tests)
Improved
Build
(run unit
Tests)
Execute
Infra tests
Code
Commit
pipeline pipeline
Provision
Cloud
Formation
Infrastructure
Pipeline
Deploy

19. Automated Builds and Test Environments
Extending the pipelines
Provision
Test Env
Code
Commit
pipeline
Build
(run unit
Tests)
E2E
Testing
Load
Testing
pipeline pipeline pipeline

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

21. ● Work out what’s important
● Measure your progress
● Build a team and encourage
collaboration
● Start Small and Iterate
● Share everything
● Choose your next Adventure
Getting Started

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