{"id":32497,"date":"2019-10-31T21:47:23","date_gmt":"2019-10-31T18:47:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/devopsforum-2019-vnedryat-devops-nelzya-zhdat\/"},"modified":"2019-10-31T21:47:23","modified_gmt":"2019-10-31T18:47:23","slug":"devopsforum-2019-vnedryat-devops-nelzya-zhdat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","title":{"rendered":"DevOpsForum 2019. You can't afford to wait to implement DevOps.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Recently, I attended DevOpsForum 2019, organized by Logrocon. At this conference, participants sought solutions and new tools for effective collaboration between businesses and developers, as well as IT service specialists.<\/p>\n

\"DevOpsForum
\n
\nThe conference was a success: there were plenty of valuable presentations, interesting formats, and lots of interaction with the speakers. Most importantly, no one tried to sell me anything, which is a common issue with speakers at larger conferences lately.<\/p>\n

Highlights from the presentations by Raiffeisenbank, AlfaStrakhovanie, Mango Telecom's experience in implementing automation, and other details are below. <\/a><\/noindex><\/p>\n

My name is Yana, I work as a tester, focusing on automation, and I love attending conferences and meetups. In the past two years, I've been to conferences organized by Oleg Bunin (HighLoad++, TeamLead Conf), events like Jug (Heisenbug, JPoint), TestCon Moscow, DevOps Pro Moscow, and Big Data Moscow. <\/p>\n

First and foremost, I pay attention to the conference agenda. I focus less on the topics of the presentations and more on the speakers. Even if a presentation is very technical and interesting, it's not guaranteed that you'll be able to apply any best practices from it in your own company. That's when you need a speaker.\n<\/p><\/blockquote>\n

The light at the end of the pipeline at Raiffeisenbank<\/h2>\n

\nTypically, I go hunting for speakers that interest me in the corridors. At DevOpsForum 2019, I found a speaker from Raiffeisenbank \u2013 Mikhail Bizhan. During his presentation, he shared how they gradually onboard their teams onto DevOps, why they need it, and how to sell the idea of DevOps transformation to the business. Overall, he talked about how to see the light at the end of the pipeline.<\/p>\n

\"DevOpsForum
\nMikhail Bizhan, Director of Automation at Raiffeisenbank<\/i><\/p>\n

Currently, they don't have 'true DevOps' in their company. It is true in some teams, but not all. When implementing DevOps, they rely on the readiness of the teams, considering both the specific engineers involved and the product's needs and the maturity of the platform on which that product is built. Misha explained how to convey to the business why DevOps is necessary. <\/p>\n

The banking sector has several growth drivers: service costs and expanding the client base. Increasing service costs is not a very good driver, while growing the client base is the opposite. If competitors release a truly outstanding product, all clients flock there, but over time the market stabilizes. Therefore, launching new products and the speed of their launch are the main focus for banks. This is exactly why DevOps is needed, and businesses understand this.<\/p>\n

Another important point: DevOps does not always reduce time to market. DevOps cannot operate alone; it is just one part of the entire process of creating and bringing a product to market from development to production (from code to client). Everything before the code has nothing to do with DevOps. Marketers can spend years studying the market and always lag behind competitors. It is essential to quickly understand what the client needs and to plan the implementation of specific features\u2014often what is lacking for DevOps to work effectively and for the company to achieve its goals. Therefore, at Raiffeisen Bank, an agreement was reached with the business on the need to learn how to utilize DevOps. Automation for the sake of automation won't significantly help in the quest for new clients.<\/p>\n

Overall, Misha believes that DevOps should be implemented wisely. One must be prepared for the fact that at the beginning of the transformation, the team's productivity will decline, and they will earn less money, but in the long run, this will pay off.<\/p>\n

Test automation at Mango Telecom<\/h2>\n

\nAnother interesting presentation for me as a tester was given by Egor Maslov from \"Mango Telecom\". The presentation was titled \"Automation of the Full Testing Cycle in a SCRUM Team\". Egor believes that DevOps is designed specifically for SCRUM, but at the same time, implementing DevOps in a SCRUM team can be quite problematic. This is because the SCRUM team is always rushing, leaving no time to focus on innovations and restructuring the process. There is also the issue that SCRUM does not involve dividing the team into sub-teams (such as a testing team, a development team, etc.). Furthermore, automation of the existing process requires documentation, and in SCRUM documentation is often completely absent \u2014 \"the product is more important than some writing.\"<\/p>\n

After transitioning to SCRUM, testers began consulting with developers on how to test features. Gradually, the volume of functionality increased, documentation was nonexistent, and they began to encounter many bugs in features that were not covered by tests, and it was unclear who tested them and when. In short \u2014 disarray. They decided to move to test automation. But even then, it ended in complete failure. They hired outsourcing specialists for automation who used a stack unfamiliar to the in-house testers. The framework for automated tests worked, but after the outsourcers left, it lasted two weeks. Then there was an attempt to introduce automation number two. It started with the understanding that everything needed to be built internally, by their own efforts (a correct direction: build expertise in-house), within SCRUM, and to create documentation in the process. The automation stack should match the product stack (which I completely agree with; don\u2019t test a project in JavaScript using something else). At the end of the sprint, they held demos of how the automated test worked, involving the entire team (useful). This way, it increased the involvement of all team members in the automation process, as well as trust in the automated tests and the chance that this automated test would indeed be used (rather than commented out after a month due to constant failures).<\/p>\n

By the way, at DevOpsForum 2019, there was an open microphone \u2014 a well-known and, in my opinion, useful format for presentations. You walk around, listen to the talks, and then decide that within the conference, it's worth discussing a certain topic or problem, sharing relevant experience in solving a task.<\/p>\n

I also noticed that the organizers created a stream of short presentations. Each presentation lasts no more than 10 minutes, followed by questions. This way, many topics can be covered at once, and attendees can pose questions to speakers they find interesting.<\/p><\/blockquote>\n

\"DevOpsForum
\n\"DevOpsForum
\nBetween the presentations, I strolled through the partner booths and snagged\/won a lot of various goodies. Ah, I love the swag!<\/i><\/p>\n

Round table and questions on DevOps with the Director of Development at AlfaStrakhovanie.<\/h2>\n

\nThe cherry on top of DevOpsForum 2019 for me was the one-hour plenary session with DevOps experts. Four session participants were invited to look at DevOps from different perspectives: Anton Isanin (AlfaStrakhovanie, Director of Development), Nailya Zamashkina (Fintech Lab, Operations Director), Oleg Egorkin (Rostelecom, Agile Coach), and Anton Martyanov (an independent expert, viewing DevOps from a business perspective). <\/p>\n

The experts sat closer to the attendees and thus began: for a whole hour, participants from the audience asked their questions, and the experts responded. Sometimes it turned into real debates. The questions were varied, for instance: do we really need DevOps engineers, why can\u2019t we grow them from system administrators, should everyone be offered DevOps, what is its value, and so on.<\/p>\n

Afterward, I spoke with Anton Isanin personally. We discussed the need to bring DevOps culture into every home and revealed the dark side of DevOps transformation.<\/p>\n

Imagine that everyone gathered and decided that DevOps is needed for both the product and the business and the team. They rushed to implement it. Everything worked out. They breathed a sigh of relief. DevOps brought us closer to the client, and now we can quickly meet all their requests. As a result, we have a large Ops department with strict regulations and requirements, and it constantly churns out defects on the product, creating a ton of tickets. Moreover, all defects are marked as \"urgent\", even if the client suddenly wants to change a button color from green to yellow. The project is growing, the number of releases is increasing, and accordingly, the number of defects and misunderstandings about the new functionality grows among clients. Ops hires 10 more people to keep up with reporting defects, while development hires 15 more to manage closing them. Instead of rolling out new features, the team is stuck with endless tickets, explaining functionality to the user and to support at the same time. As a result, both Ops and development are busy, but the client and the business are unhappy: new features get delayed. It seems that DevOps is in place, yet it also feels like it's absent.<\/p>\n

Regarding the necessity of implementing DevOps, Anton clearly stated that it directly depends on the scale of the business. If servicing one client a year brings in a billion for the company \u2014 DevOps is not needed (provided that you do not need to roll out new changes for this client regularly). Everything is already great. But if the business is growing and more clients appear, then you need to keep up. Typically, a solid Ops team is not present in the company initially. First, we build the product, and only later do we realize that for the product to work, we need to monitor supply. servers<\/a>, keep an eye on deliveries. That is when Ops arises. It remains to understand that Ops, as a separate division, will start creating numerous barriers for development, and all deliveries will begin to stall. So, in this case, the DevOps culture is already relevant, but we must not forget about its dark side.
\n
Source: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon. \u041d\u0430 \u044d\u0442\u043e\u0439 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u0438 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u043f\u044b\u0442\u0430\u043b\u0438\u0441\u044c \u043d\u0430\u0439\u0442\u0438 \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0438 \u043d\u043e\u0432\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0434\u043b\u044f \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u043e\u0432 \u043f\u043e \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u0438 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u043e-\u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u043c\u0443 \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u044e. \u041a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u044f \u0443\u0434\u0430\u043b\u0430\u0441\u044c: \u0431\u044b\u043b\u043e \u0440\u0435\u0430\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0445 \u0434\u043e\u043a\u043b\u0430\u0434\u043e\u0432, \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0430\u0442\u044b \u0432\u044b\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u0439 \u0438 \u043a\u0443\u0447\u0430 \u043e\u0431\u0449\u0435\u043d\u0438\u044f \u0441 \u0434\u043e\u043a\u043b\u0430\u0434\u0447\u0438\u043a\u0430\u043c\u0438. \u0418 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432\u0430\u0436\u043d\u043e, \u0447\u0442\u043e \u043c\u043d\u0435 \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u043f\u044b\u0442\u0430\u043b\u0441\u044f \u043f\u0440\u043e\u0434\u0430\u0442\u044c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24300,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32497","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47DevOpsForum 2019. You can't wait to implement DevOps | ProHoster","description":"Recently, I attended DevOpsForum 2019, organized by Logrocon.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47DevOpsForum 2019. \u0412\u043d\u0435\u0434\u0440\u044f\u0442\u044c DevOps \u043d\u0435\u043b\u044c\u0437\u044f \u0436\u0434\u0430\u0442\u044c | ProHoster","og:description":"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:47:23+00:00","article:modified_time":"2019-10-31T18:47:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32497","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-19 09:14:07","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:57:23","updated":"2026-02-19 09:14:07","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/32497","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=32497"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/32497\/revisions"}],"predecessor-version":[{"id":161790,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/32497\/revisions\/161790"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/24300"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=32497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=32497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=32497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}