This document discusses DevOps and continuous delivery approaches. It notes there is a perfect storm forming around programmable infrastructure, adaptable applications, and new processes like Lean and DevOps. Continuous delivery aims for just-in-time deployability without long wait times. DevOps breaks down silos between development and operations for more consistent environments, less manual testing, and faster approval processes. The document outlines continuous delivery and deployment processes and how enabling DevOps requires embracing new cultures. It identifies key DevOps challenges around organizational complexity, roles, and downstream systems and provides tips for overcoming obstacles.

1. DevOps & Continuous Delivery
A software craftsman approach

2. bsimioni@ciandt.com
medium.com/@brunosimioni
medium.com/citcommerce
brunosimioni.com

3. IT transformation
Lean, Devops & Lead Time: facing the brutal facts

5. There is a perfect storm forming in IT industry
● programmable infrastructure: cloud, configuration
management, tooling and containers
● development of adaptable application: microservices,
distributed message/log processing, and event-driven
apps
● emergence of new processes/methodologies: Lean and
DevOps
CONTAINER ORCHESTRATION AND SCHEDULING: HERDING COMPUTATIONAL CATTLE

6. ciandt.com

7. Adoption cycles, Simon Wardley
“The technology adoption
route for IT departments:
Ignore, prevent, tolerate,
allow, integrate.”
Joe Drumgoole, MongoDB

9. It’s all about
● fail fast, fail often
● measure actions and features precisely
● react properly, with feature rollout and kill switch
PaaS, Microservices, SMAC and Digital helps your company to react quickly

10. Continuous Delivery
Just-in-time deployability, where
deployment is not continuously possible

11. DevOps and Agile
Big-bang, turning-key deployment
● Redundant silos
● Wait time
● Provisioning Time
● Inconsistent envs
● Manual testing
● Heroes
● Long approval processes

13. BUILD
ACC
TESTING
PACKAGE
INTEGRATION
STAGING PROD
BUILD
BUILD
ACC
TESTING
ACC
TESTING
BUILD & BURN
TEST, RELEASE, DELIVER & SCALE
CONFIGURATION
REPOSITORY
FEATURE FLAG
REPOSITORY
LOG
HARVESTING
INFRA
MONITORING
TRANSACTION &
COMMUNICATIONS
MONITORING
MANUAL
TESTING
MANUAL
TESTING
AUTOMATIC
INFRASTRUCTURE
PROVISIONING AND
HORIZONTAL
APPLICATION
SCALLING
UNIT & MOCKED
TEST ACCEPTED
12FACTOR
ADVISED
REAL INTEGRATION
& REGRESSION TEST
ACCEPTED
BG TESTING
ROLLOUT
SOURCE
CODE
TBD
PRODUCT
BACKLOG
SPRINT
BACKLOG
TBD
TBD
FEATURE ROLLOUT
Continuous Deployment
AGILE PROCESS DEVOPS PROCESS
BREAKING THE BUILD
ALTERNATIVE
SCENARIOS

14. Continuous Delivery vs Continuous Deployment

15. Enabling Devops & Delivery
Embracing a new culture

17. What is DevOps?

18. Ideation Priorization Planning Burn Quality Assurance Deploy & Ops
Envisioning Build, Test & Go to production
Deployment
Measure, Analysis & React
DevOp Engagement
Initiation
Shippable
NFR, Infra, Sec, Frwl, DB, Automation Business Input, Disaster Recovery, Frwl, Backups Monitoring, Scaling & Measurement
PRODUCT OWNER
TECH LEADER
DEVOP
App Perf
time
engagmen
t
level
Q
A
SCRUM MASTER

19. To Avoid
● Devops != One-Click deploy
● Devops != Set of automation tools
● Automate everything from scratch
● Create a silo of initiative
● Sftw: Long-lived feature branches
● Sftw: Branch per environment

20. Achieving
● Have a plan. It’ about changing culture and process.
● Increment the process. Accomplish maturity
● Be realistic about your systems
● Document the process, evolve people

21. Achieving
● Microservices: for small deployments and testability
● PaaS: for smart infrastrucuture provisioning
● Log Harvesting: for measurement
● Comprehensive automated test to give confidence
● Hide unfinished features with feature toggles
● Small, incremental changes over big bang changes

22. DevOps: Five Key Challenges and Five Tips
DevOps adoption, challenges, & tools..
Common Obstacles
● Organizational complexity (people and depts)
● Roles, responsabilities and complex silos across devs & ops
● Product, service and development lifecycle complexity
● Complex downstream systems
● Lack of understanding by business teams
● Failed changes and systems outages
● Security, Audit and compliance

23. At the end of the day, DevOps only
matters if the business needs are met.

24. Thank you
bsimioni@ciandt.com