Embed Size (px)
Citation preview
DevOps TacticalAdoptionTheory
Ignite Talk
Berk DülgerProfessionalConsultant & Account Manager, 2013- ….. Software Engineer in Test, Atos International 2011-2013Software Engineer, Huawei Telecommunication 2009-2011Software Engineer, FreeLance 2008-2009Intern, Microsoft, Turk.Net 2007-2009
AcademicMsc. Management, Boğaziçi University, 2016Bsc. Computer Engineering, Dokuz Eylül University, 2009Karşıyaka Anadolu High School, 2005
George Orwell’s1984
vsAldous Huxley’s
Brave New World
In 1984, which is a popular dystopian novel, Orwell feared what we hate will ruin us. People are controlled by inflicting pain.
In ‘Brave New World’, another popular dystopian novel, Huxley feared what we love will ruin us.People are controlled by inflicting pleasure.
"We live ‘more’ in a Brave New
World"
Newton's Laws of MotionLaw III: To every action there is always opposed an equal reaction: or the mutual actions of two bodies upon each other are always equal, and directed to contrary parts.
Do not force people,make them believe in
Your ManagersYour Colleagues
even Yourself
Sustainable success requires both bottom-up practices and top-down management support
Show the
Value to everyone
DevOps is not a goal, but a process of
continuous improvement
The idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
DevOps Tactical Adoption Theory hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step.
The reason behind the theory is to encourage(make believe) practitioners to
apply each step one-by-one and then having the benefits in projects.
Consequently, each step will be tested in terms of utility and proved method validity
for the further steps.
There is no DevOps without
Continuous Testing
Business Facing
Technology Facing
Unit
Integration
UI
High
Medium
Low
Low
Medium
High
Medium
Long / High
Short / Low
Test Type
Business Logic Coverage
Code Coverage Execution Time / Costs
A Tactical Adoption Example in
Continuous Testing
UI Testing(End-to-End Tests), where you test the entire system together to ensure it does what it is supposed to do under real life conditions.
Unit Testingaims to test small chunks of your code in isolation from the rest of the world.
You need both of these in most of projects, but at different times: unit testing during development (ideally from the very
beginning, TDD!!!), and ui testing later, once you actually have some complete end-to-end functionality.
If you already have a system running, having no tests, practically you have legacy code. Start to get the best test
coverage achievable with the least effort first, which means high level functional(end-to-end) tests.
Adding unit tests is needed too, but it takes much more effort and starts to pay back later.
