Lessons learned during 8 years experiencing Agile/DevOps transformation in Brazilian large organizations (Oil&Gas and Telecommunication industries). Common points that helped them to move from zero to a Continuous Delivery status for many applications.
What Goes Wrong with Language Definitions and How to Improve the Situation
From Zero to Continuous Delivery - Lessons learned in Big Organizations
1. Lessons learned in Big Organizations
FROM ZERO TO CONTINUOUS DELIVERY
Amanda Mattos | DevOps India Summit | Sep 2018
2. ABOUT ME
AMANDA MATTOS
DevOps Specialist since Nov 2016
Bachelor in Computer Science & Master of Science in
Computer Engineering.
Started as a Software Developer in 2001 and worked in +13
IT projects of many industry sectors since then.
software development lead, playing different roles
(SM/PO/Dev/DevOps) and applying Agile/Lean and
DevOps practices to deliver high quality products.
+8 years experiencing Agile and DevOps transformations
in Oil & Gas and Telecommunications industries.
DevOps India Summit 2018 | 2
@amandamattos
3. ABOUT ME
AMANDA MATTOS
DevOps Specialist since Nov 2016
Bachelor in Computer Science & Master of Science in
Computer Engineering.
Started as a Software Developer in 2001 and worked in +13
IT projects of many industry sectors since then.
software development lead, playing different roles
(SM/PO/Dev/DevOps) and applying Agile/Lean and
DevOps practices to deliver high quality products.
+8 years experiencing Agile and DevOps transformations
in Oil & Gas and Telecommunications industries.
DevOps India Summit 2018 | 2
I’m the mother of the most beautiful
Darth Vader in the world!!!
@amandamattos
4. THE IT CHALLENGE
DevOps India Summit 2018 | 3
Waterfall – Long phases
Many Silos – Functional areas
Bureaucracy
Can’t respond fast to changes
Delays
Quality Problems
Painful releases
Iterations
Cross-functional / Autonomous teams
Lean
Respond fast to changes
Better Quality
Feedbacks
Continuous Delivery
Time to Market
Competitiveness
5. ACCEPT! THERE IS NO MAGIC
DevOps India Summit 2018 | 4
IT TAKES TIME
Don’t look for revolutionary, look for
evolutionary.
SUCCEED FIRST
Experiment first, prove the benefits
and then scale (inspecting and
adapting).
OLD & NEW COEXISTS
Don’t force to replace. Don’t judge
the old. Engage for improvements.
REFERENCES x MODELS
Consider models as references. Find
your own way to continuous delivery.
With your organization’s people.
6. 1st ALLOWED TO EXPERIMENT
CHANGE AN AREA? CREATE A NEW AREA? CREATE A NEW COMPANY (STARTUP LIKE)?
AGILE/LEAN PRINCIPLES
+
DEVOPS PRACTICES
+
DIFFERENT CULTURE
• high executive decision – BUY IN
• AUTONOMY – Free from “This is
the way we work in this company”
• to PROVE that works
DevOps India Summit 2018 | 5
WILL NEED:
But…we have to bring
results interacting with
the traditional
7. 2nd A TEAM TO IGNITE CONTINUOUS DELIVERY
DevOps India Summit 2018 | 6
• Help to find better links between areas – Lean Release Process
• Consider the whole and bring them closer to development time (Business, QA,
Operations, Security…)
• Provide automation, patterns and tool engine to support CD
• Propose scalable and reliable solutions/architectures
• Coaching – help teams to increase their maturity level in different DevOps capabilities
• Engage to a continuous improvement mindset
• Experiment, then share best practices to the entire company
** http://web.devopstopologies.com/
8. 3rd ARCHITECTURE TO SCALE
AS SOON YOU PROVE THE BENEFITS, YOU’LL BE ASKED TO SCALE
• Simple to use (Developer Experience)
• Consider involved areas requirements (collaboration)
• Infrastructure to scale – Elastic, if possible. If not, projections
• Standardized pipelines – changes can be rapidly applied; better governance
• Flexibility – you may have different pipeline “flavours”
• Intelligent use of resources – on demand slaves (builds)
• Measure your CI/CD – Inspect and Adapt
DevOps India Summit 2018 | 7
57 applications with CI/CD in 17 months – +700 jobs
9. BUILD /
TEST
RELEASE
DEPLOY
MONITOR
CODE
CONTINUOUS INTEGRATION
~400 Builds/day
CODE QUALITY INSPECTION
AUTOMATED TESTS
PACKAGE (CONTAINER)
~40s - 10min
Every release is tagged and stored in a binary
repository, facilitating ROLLBACKS
CONTINUOUS DELIVERY – fully
automated deploys
~10
releases/day
~4s – 7min
1 2
3
4
CONTINUOUS MONITORING
improvements based on metrics
5
CI/CD ARCHITECTURE - EXAMPLE
DevOps India Summit 2018 | 8
10. 4th IT’S A LEARNING PROCESS – PEOPLE FIRST
AUTOMATION IS A KEY TO CONTINUOUS DELIVERY, BUT NOT SUFFICIENT…
DevOps India Summit 2018 | 9
• People have to be part of the change
• Evangelize / Advocate – Blameless; Empathy; Collaboration; Continuous Improvement Mindset
• Coach – Help them achieve better states by themselves
488
85
3741
% Cobertura Antes Depois
0 <= c <= 40 14 6
40 < c <= 80 5 5
c > 80 4 12
11. CONCLUSION
• Autonomy for experimentation - the agile environment separated from
the traditional part of the company was essential to bring innovation.
• Empowerment – a DevOps team with top down support made it possible
to communicate with other areas in highly hierarchized companies.
• Standardized CI/CD Architecture - easy to use, scalable and best
patterns.
• Sharing behavior – include traditional areas in each one of the initiatives,
listening and respecting them, and supporting them to achieve a
continuous delivery status.
SCALE TO ENTIRE COMPANY
DevOps India Summit 2018 | 10
12. CONCLUSION
• It’s easier to scale tech then teams – overwhelmed DevOps team points
to an model with many DevOps cells (keeping them closer to the teams
supported by them).
• Keep improving and sharing – as you scale, be careful to not just
support what exists. Reserve capacity to evolve!
• Whatever you do, try to do in an organic way.
• Continuous engagement – this is the biggest challenge! People come
and go. Companies changes their organizational structure. Keep both
botton up and top down initiatives to engage people.
CRITICAL
DevOps India Summit 2018 | 11
13. It’s a long road…be continuously improving in your journey.
ANY
QUESTION?
THANKS DevOps India Summit 2018 | 12
@amandamattos
amandamattos@gmail.com