Berk Dülger is an IT Professional worked as a pure developer, software development engineer in test, consultant, account manager and DevOps practitioner.
He had diverse experiences in international and local projects in telecommunication, media, e-commerce, retail, insurance and banking sectors. Currently, leading more than twenty engineers in Keytorc for three different clients.
He believes that total quality improvement can be achieved only with focus on both managerial and engineering agility. Thus, very excited with the DevOps movement in last few years. He is using DevOps/Continuous Delivery practices both in industrial track and academic researches for Master’s Thesis in Industrial Engineering Department.
Linkedin Profile: tr.linkedin.com/in/berkdulger
DevOps is a state of art describing each software development step as a repeatable, automatable and deterministic process excluding error-prone human factor first time in the history of software development. The model defines the entire value chance from concept to concrete product. It is an evolutionary end for the models of software development and agile movement. But, there is a problem with the concept; though described easily, implemented a little hard.
DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, our model indicates concrete activities rather than general statements.
Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
In the session, it is planned to demonstrate “DevOps Tactical Adoption Theory” with focus on Delivery Pipeline/Testing Practices sectioned "Continuous Testing in DevOps".