This presentation summarizes implementation roadmap of DevOps in 104 years old organization.

1. WorkSafeBC - DevOps Journey
Andre Kaminski

2. Today’s Objectives
2
Why DevOps Future
3
1
WSBC DevOps
Journey
2

3. Why DevOps

4. Dev & Ops: Traditionally Opposite Goals
Working
Software
of
BUSINESS
Value
4
How can we deliver
valuable, working
software when
Development &
Operations have
opposite goals?
?

5. Problems
• Long delivery cycles
• Mindset (tell me what to do)
• Low engagement
• Lack of innovating thinking
• Limited engagement of customers
• Focus on process rather than people
• A lot of manual and repetitive steps
• Congestion in environments
• Many applications based on outdated technologies
• Rigid financial funding
• Siloed departments / hand-offs
• Poor response to changing customer needs and market environment
5

6. 6

7. What’s the Answer?

8. DevOps is the practice of development, operations and security engineers
participating together in the entire service lifecycle, from design through the
development process to production support.
8
What is DevOps?

9. 200x more frequent
deployments
2,555x shorter
lead times
3x lower change
failure rate
29% more time on new
features & code
2.2x more likely to
recommend as a great
work place
22% less
unplanned work &
rework
50% less time remediating
security issues
24x MTTR
State of DevOps Reports 2016 & 2017
Why DevOps?

10. •Mindset
•Automation
•Agility
•Feedback
•Safety
Key Principles
10

11. Tools & Practices: DevOps Practices
Unlike Waterfall or Incremental development, DevOps enables continuous
development, testing, integration, deployment & monitoring. Practices may include:
People
• Servant leadership
• Autonomous teams
• Systems thinking
• Continuous learning
• Continuous improvement
• Integrated teams
• Job rotation
• Joint meetings
• Full stack engineers
Information
• Common metrics
• Shared toolsets, codes
• Shared patterns
• Measurement/Analytics
Process
• Lean flow
• Small batches
• Limited WIP
• Visibility
• MVP
• CI / CD
• Domain-driven design
• Amplified feedback loops
• Version everything
• Test-driven dev, deployment
• Continuous testing
• End-to-end testing
• Test everything
• Automated test, build, deploy
• Canary-rollouts
• Feature toggles / dark launches
• Reduce technical debt
• Fast recovery
• Fast fix-forward
• Threat modeling
Technology
• Infrastructure as code
• Developer self-service
• Desired state management
• Integrated toolchains
Mind-
set

12. WSBC DevOps Journey

13. 104Years
WorkSafeBC is a statutory agency providing no-fault insurance to the workers
of British Columbia
• Established in 1917
• Key major pillars of the organization:
• Prevention – officers who visit places of employment to validate compliance with safety requirements
and address corrective actions/penalties when necessary
• Assessments – providing a service assessing and reporting employers’ income and payment rates
• Claims – helping injured workers with rehabilitation, insurance payments and returning to work
• We employ almost 3,000 people, and
• We serve 200,000 employers and 2.3M workers in British Columbia
13

14. The pace of disruption will dramatically impact our stakeholders and the way we work with them
Unprecedented
forces
of
disruption
WSBC & Our Stakeholders Face Disruptive Forces
Employers
Healthcar
e
services
Workers
Forces Stakeholders Impacts
Global Connectivity
Automation
Artificial Intelligence
Internet of things
Demographic shift
Collaborative economy
Urbanization
Environmental changes
Job transformation across
sectors
• New job types
• Some jobs phasing out
Increased service expectations
• New channels
• More information
More independent workers
14

15. 15
2016 - Org Commitment
• Reduce Technology Risks
• Planned move to Cloud
• Planned to spin up DevOps
pods
• Developed architectural &
infrastructure backbone
• 10 people
May 2017 - Implementation
Started
• First pod spun up for business
• Innovation pod spun up
• Agile foundation & coaching
• 40 people
Nov 2017 - Farther Down
the Road
• 5 DevOps pods spun up
• Scaling Agile, PI Planning,
All-team Retros
• First production deployment
during office hours
• 70 people
2016 - Org Commitment
• Reduce Technology Risks
• Planned move to Cloud
• Planned to spin up DevOps
pods
• Developed architectural &
infrastructure backbone
• 10 people
Aug 2018 - Well on Our
Way
• 6 DevOps pods spun up
• 4 Shared Services teams
• QA, Release, RTE, UX,
People Dev, Training
• Our own Agile Coach hired
• Agile Flavor
• DevOps Strategy
• 100 people
May 2017 - Implementation
Started
• First pod spun up for business
• Innovation pod spun up
• Agile foundation & coaching
• 40 people
Nov 2017 - Farther Down
the Road
• 5 DevOps pods spun up
• Scaling Agile, PI Planning,
All-team Retros
• First production deployment
during office hours
• 70 people

16. 16
Dec 2018 - Growing
• Service Reliability
Engineering pod
• 2 new DevOps pods for
business in Oct
• Our first Hackathon
• Integrated demos
2019 - Expanding
• Full rollout of Scaled Agile (SAFe) - 200
people trained and certified
• 2nd two day Hackathon – 170 participants
• Portfolio Implementation
• MS Teams rolled out
• Developed set of analytical tools
• Lord of Scrums game – cultural change
• Isolation of environments – Service
Virtualization
• TDD
• Microlearning
• Product Management
2020 - Hardening
• 4 Agile Release Trains (16 teams)
• PI Planning – 200 people in the room
• RTE functions
• Immutable pipeline implementation
• Software Engineering Practices
• Dojos (TDD, Vertical Slicing)
• Separate Deployment from Release
• Release VS optimization
• InnoFest
• Crank It Up Board
• Portfolio Mgt
• 10 CoPs
• Culture Deck
• Report automation
• SAFe certification for everyone – trained 350
people
• Remote work – iObeya (Business Objectives, Env
Outage, Dependency)
Dec 2018 - Growing
• Service Reliability
Engineering pod
• 2 new DevOps pods for
business in Oct
• Our first Hackathon
• Integrated demos
2019 - Expanding
• Full rollout of Scaled Agile (SAFe) - 200
people trained and certified
• 2nd two day Hackathon – 170 participants
• Portfolio Implementation
• MS Teams rolled out
• Developed set of analytical tools
• Lord of Scrums game – cultural change
• Isolation of environments – Service
Virtualization
• TDD
• Microlearning
• Product Management

17. Crank It Up
17

18. WorkSafeBC’s DevOps Strategy
We are working towards maturing WorkSafeBC’s DevOps delivery model
according to a strategy designed to take us to the next level
18
Culture
Inception
Development
Deployment
Release
Operating
People
Practices &
Standards
Analytics
Technology &
Assets
Continuous
Improvement

19. Maturity Levels
19
Crawl
Walk
Run
Fly
Maturity levels are defined for lifecycle phases & support processes
∞Kaizen
• Goal: Mature all to Fly level, but
• Never finish: aim to continuously improve
(Kaizen)

20. The People of Cloud & DevOps
20
PO BE SM SWD QAE
SWD
WorkSafeBC has 10 DevOps Business Value Delivery pods
within 4 ARTs
CSE SEC DBA INT
o Assessments
o Claims
o Prevention
o Enterprise
PM SRE UX

21. 21
We Plan Together

22. Plan for 2021

23. 2021 – Amplifying
• Digital Transformation of entire I&T
• Train I&T Leadership Team in SAFe and
business agility
• Product Management Training – Hypothesis
Testing, Customer Centricity, move from
Projects to Products thinking
• Behavior Driven Development
• Working Code Everyday
• Raise the bar in Crank It Up board
• Application resilience and self-recovery
• Continue SAFe and technology skill
enhancements
• Extending Portfolio to entire I&T – alignment
with organizational goals
• Foster innovation
• SRE – Chaos Monkey
• WSBC Technical Blog on GitHub
2021
wsbctechnicalblog.github.io

24. Andre Kaminski
Thank you!
24
Andre.Kaminski@worksafebc.com
Andrekaminski
@andrekaminski
DevOps Vancouver Meetup