In 2009 Patrick Dubois coined the term "DevOps" when he organised the first "DevOpsDays" In Ghent, Belgium. Since then the term has become a term to explain the collaboration between all organisational stakeholders in IT projects (developers, operations, QA, marketing, security, legal, …) to deliver high quality, reliable solutions where issues are tackled early on in the value stream.
But reality shows that many businesses that implement "DevOps" are actually talking about a collaboration between development, QA and operations (DQO). Solutions are being provided but lack the security and/or legal regulations causing hard-to-fix problems in production environments.
In this talk I will explain how the original idea of Patrick to include all stakeholders got reduced to development, QA and operations and why it's so difficult to apply security or compliance improvements in this model. I will also talk about ways to make the DQO model welcoming for security experts and legal teams and why "DevSecOps" is now the term to be used to ensure security is no longer omitted from the value process.
Finally we'll have a vote if we keep the term "DevOps" as an all-inclusive representation for all stakeholders or if we need to start using "DevSecOps" to ensure the business understands can no longer ignore the importance of security.
2. MICHELANGELO VAN DAM
I'm a senior #php architect, co-founder
and #ceo of @in2itvof, #community leader
at @phpbenelux, coach
at @CoderDojoBelgium, #MVP, #digitalnomad,
likes #coffee.
Follow me on Twitter: @DragonBe
4. PATRICK DEBOIS
Patrick Debois coined the term
“DevOps” at the first DevOpsDays in
Ghent (Belgium) and started a very
important movement in the tech industry.
6. THE THREE WAYS
THE PRINCIPLES UNDERPINNING DEVOPS
System thinking: performance of complete system
7. THE THREE WAYS
THE PRINCIPLES UNDERPINNING DEVOPS
System thinking: performance of complete system
Amplify feedback loops: notify issues early in the process
8. THE THREE WAYS
THE PRINCIPLES UNDERPINNING DEVOPS
System thinking: performance of complete system
Amplify feedback loops: notify issues early in the process
Culture of continuous learning & experimenting
12. DEVOPS
Unifying software development & operations
Automation & monitoring of software construction
Shorter development cycles, increased deployment
frequencies & produce dependable releases
23. SHORTER DEVELOPMENT CYCLES, INCREASED
DEPLOYMENT FREQUENCIES & DEPENDABLE RELEASES
10, 100, 1K, 10K commits a day
24. SHORTER DEVELOPMENT CYCLES, INCREASED
DEPLOYMENT FREQUENCIES & DEPENDABLE RELEASES
10, 100, 1K, 10K commits a day
Each N commits results in a deployment (could be 1)
25. SHORTER DEVELOPMENT CYCLES, INCREASED
DEPLOYMENT FREQUENCIES & DEPENDABLE RELEASES
10, 100, 1K, 10K commits a day
Each N commits results in a deployment (could be 1)
Each release is better than the previous
26. TRUST ME, I’M A PROFESSIONAL
Each commit has the potential of
introducing a new risk or break the
system. Without any safeguards,
we’re just increasing the speed of
creating a Pandora’s Box.