<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Niko Kivelä on Medium]]></title>
        <description><![CDATA[Stories by Niko Kivelä on Medium]]></description>
        <link>https://medium.com/@niko.kivela?source=rss-4fd9db0c99c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BDZBSvbUOv-dEyNdbf47ww.jpeg</url>
            <title>Stories by Niko Kivelä on Medium</title>
            <link>https://medium.com/@niko.kivela?source=rss-4fd9db0c99c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:19:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@niko.kivela/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tech Radar Update]]></title>
            <link>https://medium.com/s-group-dev/tech-radar-update-e2a56f184183?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2a56f184183</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Mon, 26 May 2025 06:06:26 GMT</pubDate>
            <atom:updated>2025-06-03T11:09:11.567Z</atom:updated>
            <content:encoded><![CDATA[<h4>Technology</h4><h4>We use technology radars for transparent technology decisions at SOK. It’s a visual tool for engineering teams to select the best technologies. It sets out the changes in technologies that interest software development and what engineering teams should pay attention to.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ylB9_s_3W6jo5L7jXqQQA.png" /></figure><p><em>All important things need to be nurtured, especially our culture. It’s crucial to our company’s success. Studies indicate a strong correlation between culture and success; culture ultimately determines our success or failure.</em></p><p>This is how I started my previous article about <a href="https://medium.com/s-group-dev/development-guidelines-a-democratic-approach-to-software-development-5b8e16c4eb30">SOK Development Guidelines</a>.</p><p><a href="https://medium.com/s-group-dev/development-guidelines-a-democratic-approach-to-software-development-5b8e16c4eb30">Development Guidelines: A Democratic Approach to Software Development</a></p><p>Recently, I participated in a seminar, where I saw my friend <a href="https://www.linkedin.com/in/tomas-lehtinen/">Tomas Lehtinen</a>, Head of Data, <a href="https://www.hel.fi/en">City of Helsinki</a>, talk about how they have had their <a href="https://www.hel.fi/en/decision-making/information-on-helsinki/maps-and-geospatial-data/make-better-use-of-geospatial-data/open-geographic-data">data available publicly</a> for the last 14 years. The talk sparked another discussion by another delegate asking me if they remembered correctly that SOK has also open-sourced many of their libraries, guidelines, and technology choices. “Yes, I made a new release of our Tech Radar yesterday,” I answered.</p><p>We think our <a href="https://s-group-dev.github.io/tech-radar/">Tech Radar</a> as supercharged and compressed knowledge combining all our teams’ technology choices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tEoahzf4arEKDfjfwL8O5g.png" /><figcaption>Screenshot from our GitHub | <a href="https://s-group-dev.github.io/tech-radar/">https://s-group-dev.github.io/tech-radar/</a></figcaption></figure><h4>Why Use Tech Radar?</h4><p>Tech Radar addresses several key needs for our teams:</p><ul><li>Documents technology choices and reasoning in a centralized, open place</li><li>Creates visibility across teams about what technologies are in use</li><li>Builds community around technology decisions</li><li>Supports our economy of scale through shared knowledge</li></ul><p>We are using <a href="https://opensource.zalando.com/tech-radar/">Zalando Tech Radar</a> open-sourced library, based on the pioneering work of <a href="https://www.thoughtworks.com/radar">ThoughtWorks Technology Radar</a>. It’s an easy-to-use tool to visualize our choices.</p><p>No one says it better than my ex-colleague <a href="https://www.linkedin.com/in/andrablaj">Andra Blaj</a>, Engineering Manager at Medic. To learn more, watch her excellent LeadDev talk: <a href="https://www.youtube.com/watch?v=P8chnYN7pp0">Why Tech Radar Matters</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FP8chnYN7pp0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DP8chnYN7pp0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FP8chnYN7pp0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/034e50e236c2da5596c76387b3663959/href">https://medium.com/media/034e50e236c2da5596c76387b3663959/href</a></iframe><h4>How Tech Radar Works?</h4><p>We have two versions of our Tech Radar: internal and external/public. The data shown in our internal Tech Radar isn’t just anyone’s opinion. It’s an average of all teams that have evaluated their technological choices. The radar takes all inputs from all teams and calculates the median for each individual choice.</p><p>It’s also important to notice, that there are only lines about technologies that teams are already using and have in their codebases. It doesn’t have choices, that teams would like to use, and would like to avoid, but choices that teams want to keep using or want to get rid of.</p><blockquote>Do you know SOK Development Guidelines (<a href="https://medium.com/s-group-dev/development-guidelines-a-democratic-approach-to-software-development-5b8e16c4eb30">overview article</a>, <a href="https://github.com/s-group-dev">GitHub repo</a><a href="https://confluence.sok.fi/spaces/SEH/pages/74877463/Development+Guidelines">)</a>. Tech Radar is a logical extension maintained by the same developer community.</blockquote><p>This is how it works:</p><ul><li>Each choice is put into one of four categories:</li><li>&gt; Languages</li><li>&gt; Infrastructure</li><li>&gt; Frameworks &amp; Tools</li><li>&gt; Data Management</li><li>Additionally, each choice is assigned to a ring</li><li>&gt; ADOPT</li><li>&gt; TRIAL</li><li>&gt; ASSESS</li><li>&gt; HOLD</li><li>Each section is limited to 15 for readability</li></ul><p>From our <a href="https://s-group-dev.github.io/tech-radar/">public radar</a>, we’re removing all choices that only occur once. Since we’re revealing the whole company’s choices, we want to keep it consistent. We are also removing some choices, that we do not want to display in tech radar. Reasons could be that they are so legacy that teams’ cannot really make a decision or that we don’t want to reveal our internal tooling.</p><h3>Evolution of Our Tech Radar</h3><p>In the fast-paced world of technology, keeping up with changes in our tools, frameworks, and languages is essential for staying competitive.</p><p>This quarter, we noticed important changes in our technology that reflect our new priorities and the demands of the market. These include shifting towards data management and infrastructure approach, AWS native solutions and security tools, and moving away from some of our core technologies with more specialized alternatives.</p><p>Unfortunately, more detailed takeaways, full listings, and team-specific listings can only be seen by our employees. Check out <a href="https://www.s-group.dev/">s-group.dev</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oJ-hyIFQtAJPTT9yDecoQ.png" /><figcaption>Screenshot from our external landing page | <a href="https://www.s-group.dev/">https://www.s-group.dev/</a></figcaption></figure><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/tech-radar-update-niko-kivel%C3%A4-r8jif/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2a56f184183" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/tech-radar-update-e2a56f184183">Tech Radar Update</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Development Guidelines: A Democratic Approach to Software Development]]></title>
            <link>https://medium.com/s-group-dev/development-guidelines-a-democratic-approach-to-software-development-5b8e16c4eb30?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b8e16c4eb30</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Tue, 18 Mar 2025 07:44:59 GMT</pubDate>
            <atom:updated>2025-04-07T07:14:28.796Z</atom:updated>
            <content:encoded><![CDATA[<h4>Developer Experience</h4><h4><em>All important things need to be nurtured, especially our culture. It’s crucial to our company’s success. Studies indicate a strong correlation between culture and success; culture ultimately determines our success or failure.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*hWT7eBxvJtp6SwbijyujNg.png" /><figcaption>Cover pages from our <a href="https://github.com/s-group-dev/development-guidelines">GitHub</a></figcaption></figure><p>Culture within an organization can’t be bought; it can only be created from within by people. We use culture to align our ways of working with best practices that have been discussed, written down, shared, and aligned between all our cross-functional development teams. We call them SOK Development Guidelines. I’ve previously written <a href="https://medium.com/s-group-dev/sok-development-guidelines-f65de311f181">about this topic in 2022</a>.</p><p><a href="https://medium.com/s-group-dev/sok-development-guidelines-f65de311f181">SOK Development Guidelines</a></p><blockquote>Culture impacts your morale, commitment, and how far you are willing to go.</blockquote><h4>Why We Agreed on Common Guidelines?</h4><p>Here at SOK, our development community (teams) have created company-level Development Guidelines to agree on all the best practices in our ways of working. By doing this, we can maximize the benefits of aligning our approaches in software development, share know-how, share tooling, and keep solving the same problems.</p><p>One might ask, why did we do it? Doesn’t agreeing on common guidelines limit our various teams to a negligent compromise? <em>Yes, but no</em>.</p><p>There are at least two different views on this matter. Some could say, “The best standards are made by someone else.” The point is well justified if we consider how much time and effort one can spend developing a complete set of guidelines.</p><p>Wouldn’t it be easier to free our time for actual problem-solving and let someone else align our working methods? <em>Yes, and no.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*iyLSB678KwjC-AEpl_On_A.png" /></figure><h4>There Are No Vacuums</h4><p>No project works in a vacuum. How the current software ecosystem works is that you are tied to libraries and modules made by someone else, where you will inevitably inherit some of the conventions. Which will most likely conflict, eventually.</p><p>We’re extending the common knowledge. Adjusting, extending, and using our developers to do this is a very effective way of crowdsourcing the most important domain in our scope and assuring a painless adoption voluntarily.</p><p>While a simplified ruleset is easier to implement, it’s by no means limiting our developers in their work. We have a community of practice around this handbook, which is the whole point — no rules because of the sake of it, but a community that shares knowledge.</p><h4>They Work as a Checklist</h4><p>Even though we agree on guidelines, guidelines don’t tell you how to build your application. They tell us what to consider, respect, and remember.</p><p>Nowadays, software development is more complex than ever before, and you can’t possibly remember everything every time. In this case, Development Guidelines work as a checklist for our convenience.</p><blockquote>Our Development Guidelines is a living document.</blockquote><h4>Stop Reinventing the Wheel</h4><p>We don’t want every team to reinvent the wheel. Adhering to these guidelines encourages the widespread adoption of our work methods and software implementation.</p><p>Our teams can utilize existing tools and find answers to frequently asked questions about software development, as there are often multiple valid approaches to implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*AQWE8QFFHUeGzZ5NhD1tFQ.png" /></figure><h4>How Did We Create Them?</h4><p>Our Development Guidelines is a living document. Everything ever added to our documents is pressed through a democratic mechanism where everyone is equally important. That’s why we also wanted to give something back to the public and have <a href="https://github.com/s-group-dev/development-guidelines">open-sourced</a> our work.</p><blockquote>Growth never ends; it needs to be continuous. Once it stops and we stop changing, it’s game over.</blockquote><p>Anyone can suggest changes, which are then workshopped upon, tailored, and packed up with documentation by our developers. When everything looks good, we are ready for a voting meeting.</p><p>In a meeting, everyone has one vote for each particular guideline, and we expect you to vote yes or no. If we get the majority of votes democratically, we’ll add it to our main document.</p><h4>How Do We Use Them?</h4><p><a href="https://agilemanifesto.org/">Since</a> best architectures, requirements, and designs merge from self-organizing teams, instead of having someone to tell you how to do your software, we’ve taken ownership of our ways of working ourselves. To prove that this works, our teams are committed to these principles and do self-assessments regularly. These reports are then released into our internal dashboards, and we let public pressure and transparency do their magic.</p><p>It’s okay for a team to go against all our agreed guidelines, but that’s also public information.</p><h4>Radical Transparency</h4><p>Repeat: our teams are committed to these principles and regularly perform self-assessments to prove this works. As the saying goes, <em>measure or be measured</em>. SOK development communities have ultimately taken ownership into their own hands.</p><p>The same principle is applied to our voting meetings. What everybody votes for will also be published.</p><p>Teams can compare their progress based on measurements. We provide them with heatmaps based on their results to show the overall maturity of teams, business domains, and departments.</p><p>The ultimate goal is to cross-reference these results with other measurements we run across the company. We are not interested in whether teams are doing good or worse, but if there are large gaps between answers, we’d be keen to facilitate a discussion within your team to leverage misunderstandings.</p><h4>Examples</h4><p>Here are a few examples of our principles.</p><pre>MUST have a process for peer review<br>MUST agree on a coding standard inside a team<br>MUST have a repeatable infrastructure</pre><p>Our guidelines are quite easy to follow. They tell you what needs to be done but not how. We believe that teams know better and are experts in their domain.</p><h4>What Good Guidelines Consists of?</h4><p>When coming up with new guidelines, most of the time goes for preparing the outfit of a single principle. We want each guideline to say one thing so it’s easy to answer whether we are following it.</p><p>For example, the principle that each team should have implemented logging and put all the collected logs in a centralized location does not apply since it has two separate actions. Instead, it would be better formed as “MUST have monitoring” and “MUST have centralized logging.”</p><h4>Sharing is Caring</h4><p>Finland is a small country, but the industry is huge. Sharing knowledge is good for us all. Sharing is caring, but in this case, sharing equals acquiring it. We will get the information back in refined, better, and tested form.</p><p>I’ve discussed these in multiple meetups with different companies and about software development in general for university students. I know companies in Finland that were motivated by our work and do similar things.</p><p>This is only the tip of the iceberg. We have a ton of productized tooling, processes, documentation and personnel helping our teams around it. Guidelines work as a base of common ground and part of a larger handbook where we agree on even broader topics.</p><p>My personal take on readymade rules is that when we eventually reach the maturity it specifies, there is a chance we will declare ourselves done. No ruleset in modern software development can be static. While the world around us evolves, the ones not evolving with it are the ones facing regression. Guidelines is a living document.</p><h4>Why All This?</h4><p>“You Build It ,You Run It” was coined back in 2016, when the CTO of Amazon, <a href="https://www.linkedin.com/in/wernervogels">Werner Vogels</a>, said in an interview:</p><p>“You build it, you run it.” But we rarely see the whole citation. We do all this to empower our teams to reach customers faster. The first time your applications actually provide any value to our company is when the end users use them. We want our teams to do that better, faster, and more reliably.</p><figure><img alt="Image from TechCrunch" src="https://cdn-images-1.medium.com/proxy/1*fGJ_4Dj1-SocfU2lRrovnA.png" /><figcaption>Image from <a href="https://techcrunch.com/2023/11/30/amazon-cto-werner-vogels-on-culturally-aware-llms-developer-productivity-and-femtech/">TechCrunch</a></figcaption></figure><p>Another way to look at this is how you operate your service. You’re the only one who can affect it. Make the quality of your work count. Without quality, you are out of business.</p><blockquote>“While maturity models are very popular in the industry, we cannot stress enough that maturity models are not the appropriate tools to use or mindset to have.” — Accelerate.</blockquote><p>Our teams constantly improve their outcomes because our goals are moved further. We do this by constantly adding new guidelines and by removing obsolete ones. Extensive measurements also give us meaningful insights that we couldn’t detect otherwise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*qhJLPJaik8mE_CrPr85cqg.png" /></figure><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/sok-development-guidelines-democratic-approach-software-niko-kivel%25C3%25A4-pdbjf/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b8e16c4eb30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/development-guidelines-a-democratic-approach-to-software-development-5b8e16c4eb30">Development Guidelines: A Democratic Approach to Software Development</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Got Interviewed at AWS re:Invent]]></title>
            <link>https://medium.com/s-group-dev/i-got-interviewed-at-aws-re-invent-c4c50cafb9a3?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4c50cafb9a3</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Sun, 09 Feb 2025 21:16:58 GMT</pubDate>
            <atom:updated>2025-02-12T15:11:34.916Z</atom:updated>
            <content:encoded><![CDATA[<h4>Artificial Intelligence</h4><h4><em>Last year, I attended AWS re:Invent 2024 in Las Vegas, and there’s much to tell. This was not my first time there, and I can tell it gets better the more you go. Later, in another post, I will discuss the technology-focused side and focus more on going there as an AWS Community Builder for the first time. This post is about something else.</em></h4><figure><img alt="My interview in Finnish Magazine called TIVI (Tietoviikko)" src="https://cdn-images-1.medium.com/proxy/1*6ckervPtg0W3mvlgfFBADA.jpeg" /><figcaption>My interview in Finnish Magazine called TIVI (Tietoviikko)</figcaption></figure><p>Last year marked my third attendance at AWS re:Invent in Las Vegas, and as an in-person 2024 event, by far, the best!</p><p>The journey to re:Invent starts months in advance. This includes securing conference ticket, booking hotels, arranging flights, obtaining authorization to travel (<a href="https://apply.usvisaconnection.com/application/esta?gad_source=1&amp;gclid=CjwKCAiAnpy9BhAkEiwA-P8N4qgmc7z4hRJKJZayPp748-BoVg0gGsg3ZcSE4H1OLLuJOU7oHhTxoRoCKX4QAvD_BwE">ESTA</a>), selecting sessions, and doing <em>a lot of scheduling</em>. On top of that, I strongly recommend building some leisure time before or after the conference to take the most value out of traveling almost 9 000 kilometers.</p><h4>How the Interviews Happen at the Conferences</h4><p>As Head of DevOps at SOK, one of Finland’s largest Amazon Web Services customers, our participation in media interviews comes naturally. AWS keeps a pool of available interviewees, allowing reporters to choose their preferred subjects, with final arrangements dependent on mutual agreement.</p><p>I have been to <a href="https://medium.com/s-group-dev/devops-team-is-a-myth-b13d3fd517eb">magazines before</a>, so I don’t know why this felt different.</p><p><a href="https://medium.com/s-group-dev/devops-team-is-a-myth-b13d3fd517eb">CIOReview: DevOps-Team is a Myth</a></p><p>Despite my previous media appearances, this interview felt distinctly different. Maybe it was because it was abroad or a peculiar circumstance of being interviewed for a Finnish magazine. After the interview was done, it felt almost absurd. Just think about it. Two Finns fly to the other side of the world for a conversation that could have happened back home or even online.</p><h4>What I Think about AI</h4><p>I won’t copy the whole interview word-for-word here, but I will generalize my thoughts. You can read the original <a href="https://www.tivi.fi/uutiset/tekoalyn-halpuutus-alkaa/ae7fada9-16d3-40ec-8f42-53cbfa42e17c">text here</a> (in Finnish).</p><figure><img alt="Screenshot from their website https://www.tivi.fi/" src="https://cdn-images-1.medium.com/proxy/1*sPUIKoEcNmu1GOzLFb1NCw.png" /><figcaption>Screenshot from their website <a href="https://www.tivi.fi/">https://www.tivi.fi/</a></figcaption></figure><p>I believe that AI is the thing that increases developer productivity. AI represents the first significant technological leap in developer productivity we’ve seen in a decade. It can improve your team’s delivery performance, but only if your<a href="https://en.wikipedia.org/wiki/Value_stream"> Value Stream</a> doesn’t hinder it. Currently, we are limited by our focus on how AI-assisted code-completion tools work. While they’re promising, it merely scratches the surface.</p><p>At SOK, we’ve extensively integrated Microsoft’s Copilot into our application development workflow. While coding assistants have been found beneficial for individual developers, they might <a href="https://newsletter.getdx.com/p/2024-dora-report">reduce overall team productivity</a>, as noted in the latest <a href="https://cloud.google.com/devops/state-of-devops">State of DevOps report</a>.</p><p>This effect is believed to stem from the fact that AI can generate code more rapidly and in greater volume, increasing the workload for code reviewers and raising the likelihood of errors making it into production.</p><p>Despite this, I’m confident that assistants will remain valuable tools once we learn how to use them.</p><blockquote>While coding assistants have been found beneficial for individual developers, they might reduce overall team productivity.</blockquote><p>I also don’t believe that AI will replace developers, even though the nature of their work will evolve. Remember the times when you joined a new company, and before you could start coding, you needed to install servers and interpreters as a local development environment. This was 20 years ago. Anyhow, the process could take days + all the debugging.</p><p>The same thing happened to writing when pens, typewriters, and computers were invented. The same happened to photography with the invention of carbon prints, film, and digital cameras. None of this means that previous inventions are obsolete; they’re just replaced by productivity.</p><h4>GPT vs. Agents</h4><p>When discussing software development and AI, we typically refer to GPT (Generative Pre-trained Transformer). These large language models excel at understanding and generating human-like text. Think about it as an advanced autocomplete tool. The most well-known type of GPT is <a href="https://chatgpt.com/">ChatGPT</a> by <a href="https://en.wikipedia.org/wiki/OpenAI">OpenAI</a>. The AI editor version of this LLM is Microsoft’s <a href="https://github.com/features/copilot">GitHub Copilot</a>. They react to human interaction to generate text.</p><p>Agents, however, represent the next evolution and can take things a step further. Unlike GPTs, they can work independently. One example would be an agent that monitors the entire deployment pipeline and identifies bottlenecks over time, highlighting the areas that need optimization (see <a href="https://www.tocinstitute.org/theory-of-constraints.html">Theory of Constraints</a>).</p><h4>AI won’t replace developers; it will enhance their work</h4><p>Software Engineering is a people industry. New knowledge, innovation, and product development will always depend on humans. Sure, AI will replace some tasks and entire aspects of the current definition of software development, but that’s not necessarily a bad thing. That will free our time to do something even more meaningful.</p><blockquote>AI is one of the first things in a decade that can boost developer productivity with technology. It can improve your team’s delivery performance, but only if your Value Stream doesn’t hinder it.</blockquote><p>For it to work, one needs to focus on product-oriented systems thinking and constantly eliminate constraints.</p><p>AI is here to stay and will help you stay in the market. But please make an effort to use it right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4c50cafb9a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/i-got-interviewed-at-aws-re-invent-c4c50cafb9a3">I Got Interviewed at AWS re:Invent</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Productivity — What is it and Why Do We Need it?]]></title>
            <link>https://medium.com/s-group-dev/developer-productivity-what-is-it-and-why-do-we-need-it-a364c049b97e?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a364c049b97e</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Wed, 04 Dec 2024 07:30:10 GMT</pubDate>
            <atom:updated>2024-12-19T06:44:53.496Z</atom:updated>
            <content:encoded><![CDATA[<h4>Developer Productivity</h4><h3>Developer Productivity — What is it and Why Do We Need it?</h3><h4><em>Our team’s name is DevOps &amp; Developer Experience. The name is well thought out. DevOps is the </em><a href="https://www.donovanbrown.com/post/what-is-devops"><em>union of people, process, and products</em></a><em> to enable continuous delivery of value to our end user. Developer Experience (DevEx) </em><a href="https://microsoft.github.io/code-with-engineering-playbook/developer-experience/"><em>refers to how easily </em></a><em>a developer can perform essential tasks to implement a change.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V1sAtx4YDb_smq07uGGWwg.png" /></figure><p><a href="https://developer.microsoft.com/en-us/developer-experience">DevEx is about helping developers</a> write and write code in an environment optimized for writing code. DevEx also leans towards Developer Productivity (DevProd). Engineering teams who have good developer experience are more productive. They perform better in <a href="https://queue.acm.org/detail.cfm?id=3595878">business performance</a> through increased efficiency, product quality, and employee retention. It also affects developers’ efficiency, velocity, quality, onboarding, and adoption of processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*WM0FwpPca_3ob2F36g-2oA.png" /><figcaption><a href="https://queue.acm.org/detail.cfm?id=3595878">DevEx: What Actually Drives Productivity<br>The developer-centric approach to measuring and improving productivity.</a></figcaption></figure><p>We have hundreds of people working with code. With this economy of scale, we want to optimize the environment for the greatest value creation. Even the smallest optimization in development processes is multiplied by the number of developers. It also improves the onboarding of all new developers we recruit.</p><p>Examples of what we could and are doing:</p><ul><li>Create ready-to-use templates for tools and processes to prevent teams from starting from scratch, leading to better integration with existing systems workflows.</li><li>Equip teams with pipelines that automatically track wait times and deployments, providing data for improvement processes.</li><li>Enable service teams to promote their services as self-service, providing developers a one-stop solution for everything they need without duplicating efforts.</li></ul><h4>What Studies Say?</h4><p>You’re already focusing on user experience to keep your customers happy. You know that happy customers generate more revenue. It’s <a href="https://hbr.org/2019/08/the-key-to-happy-customers-happy-employees">evident</a> that engaged and happy employees result in better customer satisfaction.</p><p>Who’s taking care of your employee experience? And what about developer experience, which is a subset of the previous? Developer experience includes all activities that development teams engage in as part of their role in the software development process.</p><p>DevEx is important because of its impacts on everyday development. Better DevEx can be a <a href="https://queue.acm.org/detail.cfm?id=3639443">leading indicator</a> of the quality, reliability, maintainability, and even security of the systems. It’s been studied that developers who find their tools and work processes intuitive and easy to use feel they are 50 percent more innovative. Developers who report fast code-review turnaround times feel 20 percent more innovative and have 50 percent less technical debt. With all the time freed for deep work, they may feel 50 percent more productive than those lacking dedicated time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcdMahX-HMExJ31F2joCAg.png" /><figcaption><a href="https://queue.acm.org/detail.cfm?id=3639443">DevEx in Action<br>A study of its tangible impacts</a></figcaption></figure><p>But none of this happens by accident. Our team continuously measures all cross-functional teams in our company to find areas for improvement. We use data-driven tools to identify and improve key developer workflows. We aim to collect more for cross-referencing results to see what works and what does not. Think about it as a company radar focusing on creating value for our software functions. With this data, <a href="https://queue.acm.org/detail.cfm?id=3454124">we can predict</a> what gives us better developer productivity and provide our organization and developers with the ability to make higher-quality software — and make it more efficient. This data-driven approach helps us enhance developer workflows and predict productivity gains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDt68GFKjWmbCuVNnAXrQA.png" /><figcaption><a href="https://queue.acm.org/detail.cfm?id=3454124">The SPACE of Developer Productivity<br>There’s more to it than you think.</a></figcaption></figure><h4>Autonomy Requires Ownership</h4><p>Ownership is something you want to nourish; take care of quality and make long-term sustainable design choices. We want you to be able to do so, giving you the time and mental capacity to do so. We try to make tools more easily accessible and adoption effortless. We leverage processes and make your work as easy as possible so you can focus on your actual work, which is what you were hired to do: building software.</p><p>Optimizations at the right place and time make a huge impact. Automation, tools, processes, and perfect workflows empower Developer Experience, making them faster, happier, and more productive. <a href="https://newsletter.getdx.com/p/code-ownership">Lack of product ownership</a> negatively correlates with the number of bugs and defects.</p><h4>Summary</h4><p>We want to understand what DevEx is for our organization. Many organizations are just starting their DevEx journey, and so are we. There are no silver bullets or ready-made solutions since every company is unique, its abilities differ, capabilities are diverse, and maturity is always evolving.</p><ol><li>Better Developer Experience leads to better code quality and less defects. Code quality is a <a href="https://newsletter.getdx.com/p/developer-productivity-at-google">predictor</a> of productivity. Our business gets more with the same teams.</li><li>Better Developer Experience leads to better business performance through product quality and employee retention.</li><li>Better Developer Experience helps developers create maintainable and less technical systems. This frees time for innovation and focuses on more business-critical skills.</li></ol><p>Developer Experience needs hard work, but it pays off. Do you know what we need next? That’s what we are here to find out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a364c049b97e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/developer-productivity-what-is-it-and-why-do-we-need-it-a364c049b97e">Developer Productivity — What is it and Why Do We Need it?</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership Promises: I Do]]></title>
            <link>https://medium.com/s-group-dev/leadership-promises-i-do-eaf758072d92?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaf758072d92</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 09:47:58 GMT</pubDate>
            <atom:updated>2024-06-07T09:50:14.498Z</atom:updated>
            <content:encoded><![CDATA[<h4>Business Leadership</h4><h4>Job satisfaction is important to us. Our strengths lie in management and performance in particular. We have Group-wide leadership promises: I Dare, I Appreciate, and I Do. The purpose of these promises is to ensure good supervisory work and management for everyone and further develop the Group’s management culture.</h4><figure><img alt="Before the interview, I asked them to take a few pictures to use, well, in articles like this." src="https://cdn-images-1.medium.com/max/1024/1*gODbO3LdoGFFrS70ZmG-cQ.jpeg" /><figcaption>Before the interview, I asked them to take a few pictures to use, well, in articles like this.</figcaption></figure><p>I was interviewed in the company studio about one of our Leadership promises: “<em>I Do.</em>” Of all the three promises, this is my favorite. It’s about taking action and being held accountable for your doings so people expect you to do what you promise — key aspects of good leadership.</p><p>In the video, I discuss the topic of “<em>What is good leadership?</em>”</p><p>I’m super excited about the result, the atmosphere, and the feeling in the set, considering I only heard the questions just before the interview when the recording was made. What you hear comes from my heart, as was said at the moment.</p><blockquote><em>Every employee deserves good management</em></blockquote><h4>The Video</h4><p>The video is in Finnish, so here’s my free-form translation. Try to look for the following moments:</p><ol><li>To be there, be present.</li><li>To do so, lead by example.</li><li>Follow up by setting goals, motivate, repeat.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F870616947%3Fh%3D696bfda061%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F870616947%2F696bfda061&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1801362780-b553072df8e12029a4c8d4c427683c4a52b3a86cfe0e0d5cd88d3d4bb2a4ce3f-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/34b6e1725e6da3004c12d315cc5c3b13/href">https://medium.com/media/34b6e1725e6da3004c12d315cc5c3b13/href</a></iframe><blockquote><a href="https://vimeo.com/870616947/696bfda061"><em>00:00</em></a> <strong><em>What is good leadership?</em></strong></blockquote><p>Good Leadership is about having courage, boldness, and trust as a representative of my employer and between our teams. Nowadays, the significance of an individual team member might have diminished in the workplace. While one person can achieve great things, a team can achieve great things repeatedly and sustainably. Teamwork means everything to me because, without my team, I am nothing; I may not even have a purpose in this company.</p><blockquote><a href="https://vimeo.com/870616947/696bfda061?share=copy#t=46"><em>00:46</em></a> <strong><em>I Do</em></strong></blockquote><p>I have always believed that transparency is one of the most important values because transparency in teamwork builds trust. We share our successes, failures, and challenges within the team because it is during challenges and failures that we can improve and learn from our mistakes. We share our results and goals within the team but have also done so outside our team because of good spreads through examples. By doing so, we humanize ourselves and teach that to the company, which creates psychological safety. When people feel good, they continually strive for better, which benefits us.</p><blockquote><a href="https://vimeo.com/870616947/696bfda061?share=copy#t=101"><em>1:41</em></a> <strong><em>Transparency</em></strong></blockquote><p>My team is a functional team, and the best and only way to lead it is to be an expert among experts. I hold myself to the same standards I expect from my team, leading by example. If I don’t expose myself to human errors through transparency, I can’t expect that from my team. If I don’t lead by example, I can’t expect that from my team. If I don’t… it would simply be unfair.</p><figure><img alt="Leadership promises from s-ryhma.fi" src="https://cdn-images-1.medium.com/proxy/1*LO8hxj7EOOE_O8zApq5X0w.png" /><figcaption>S Group’s leadership commitments</figcaption></figure><h4>S Group in brief</h4><blockquote>We have more than 40,000 employees. We are the largest private employer in Finland, with locations across the country, from Hanko in the south to Inari in the north.</blockquote><blockquote>Job satisfaction is important to us. Our strengths lie in management and performance in particular. We have Group-wide leadership promises: I Dare, I Appreciate, and I Do. The purpose of these promises is to ensure good supervisory work and management for everyone and further develop the Group’s management culture.</blockquote><blockquote>— <a href="https://s-ryhma.fi/en/careers/why-work-for-s-group">https://s-ryhma.fi/en/careers/why-work-for-s-group</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaf758072d92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/leadership-promises-i-do-eaf758072d92">Leadership Promises: I Do</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m Mentoring Women In Tech Startups: Dedication For Inclusive Growth]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination-curated/im-mentoring-women-in-tech-startups-dedication-for-inclusive-growth-558011b97fa5?source=rss-4fd9db0c99c0------2"><img src="https://cdn-images-1.medium.com/max/600/1*zkyMaXXO-bpS_u2Up1gODQ.png" width="600"></a></p><p class="medium-feed-snippet">In the tech industry, women encounter barriers to success. I explain why I decided to work as a Startup Mentor to empower inclusivity.</p><p class="medium-feed-link"><a href="https://medium.com/illumination-curated/im-mentoring-women-in-tech-startups-dedication-for-inclusive-growth-558011b97fa5?source=rss-4fd9db0c99c0------2">Continue reading on Curated Newsletters »</a></p></div>]]></description>
            <link>https://medium.com/illumination-curated/im-mentoring-women-in-tech-startups-dedication-for-inclusive-growth-558011b97fa5?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/558011b97fa5</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Thu, 28 Mar 2024 18:52:46 GMT</pubDate>
            <atom:updated>2024-04-05T14:55:06.717Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Premiere: DevOps & DX In SPACE]]></title>
            <link>https://medium.com/@niko.kivela/premiere-devops-dx-in-space-28b9e65f4175?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/28b9e65f4175</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Mon, 19 Feb 2024 22:45:48 GMT</pubDate>
            <atom:updated>2024-03-05T13:32:09.548Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*uaoxSKJSwt0v-oLg3CHQgg@2x.jpeg" /></figure><p>I just had a premiere with my new talk: ”DevOps &amp; DX In SPACE” at <a href="https://teamit.fi/en/">Teamit</a>.</p><p>After exploring some of the most common definitions of DevOps, it’s clear that the most important things are collaboration and cultural philosophies around DevOps. However, the expectations for DevOps teams and engineers remain the same as we are getting from “traditional” Ops. The only difference is that now we’re voluntarily handing over the code instead of just throwing it over the operative fence.</p><blockquote>”The DevOps talk today was really great! Lots of difficult stuff chewed down into nice easy to consume bits. The information appeared to be really current as well.” – Teamit’s consultant</blockquote><p>In my presentation, I defined DevOps again through 4 theories:</p><ol><li>The Three Ways</li><li>Value Streams</li><li>The Theory of Constraint</li><li>Systems Thinking</li></ol><p>Think about it, and it starts making sense until you hit the obvious. The truth has been hiding on sight the whole time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*LHGUWvbLg8A2hZNk0oq2zg@2x.jpeg" /></figure><p>The concept of <a href="https://queue.acm.org/detail.cfm?id=3595878">Developer Experience</a> and its three core dimensions:</p><ol><li>Flow State</li><li>Feedback Loops</li><li>Cognitive Load</li></ol><p>…lie in the details of theories upon which I based my definition. These dimensions provide a framework with 25 sociotechnical factors to identify potential measurement areas.</p><p><a href="https://queue.acm.org/detail.cfm?id=3454124">SPACE</a> is a framework for understanding Developer Productivity. There is now a universal single metric for that. And it’s always personal.</p><p>I hope to elaborate on our industry and make it better for everyone. I want to inform our leaders that budget savings by reducing developers do quite the opposite if you don’t lessen the size of your backlog with the same volumes. By doing this, you burn out your developers, lower the quality of work, and pay the interest of technical depth in every future recruitment.</p><p>What if I say you can get more value from your team with the same money by focusing on the right things? Anything you do doesn’t produce any business value until your product is delivered to your customers.</p><p>I am looking forward to talking more about this! Conferences, podcasts, meetups, or any especially welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28b9e65f4175" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Manager: Guide to Forming High-Performing Software Teams]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://levelup.gitconnected.com/dear-manager-guide-to-forming-high-performing-software-teams-dab7c4bbf406?source=rss-4fd9db0c99c0------2"><img src="https://cdn-images-1.medium.com/max/1024/1*pjjIMjZgnbciIBEw3fx0Ow.png" width="1024"></a></p><p class="medium-feed-snippet">I share my insights and strategies from leading teams on how to form high-performing and scalable teams. It&#x2019;s all about operations.</p><p class="medium-feed-link"><a href="https://levelup.gitconnected.com/dear-manager-guide-to-forming-high-performing-software-teams-dab7c4bbf406?source=rss-4fd9db0c99c0------2">Continue reading on Level Up Coding »</a></p></div>]]></description>
            <link>https://levelup.gitconnected.com/dear-manager-guide-to-forming-high-performing-software-teams-dab7c4bbf406?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/dab7c4bbf406</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Sun, 28 Jan 2024 20:23:57 GMT</pubDate>
            <atom:updated>2024-02-11T08:56:09.386Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cracking the Dev Team Code: Their Actual Needs]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://levelup.gitconnected.com/team-needs-from-your-development-teams-a147006d2559?source=rss-4fd9db0c99c0------2"><img src="https://cdn-images-1.medium.com/max/1024/1*kB40bYiZSY7buFFHEfqn1g.png" width="1024"></a></p><p class="medium-feed-snippet">This article discusses how companies should focus on team capabilities instead of keep hiring more developers.</p><p class="medium-feed-link"><a href="https://levelup.gitconnected.com/team-needs-from-your-development-teams-a147006d2559?source=rss-4fd9db0c99c0------2">Continue reading on Level Up Coding »</a></p></div>]]></description>
            <link>https://levelup.gitconnected.com/team-needs-from-your-development-teams-a147006d2559?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a147006d2559</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[software-enginee]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Thu, 28 Dec 2023 08:32:17 GMT</pubDate>
            <atom:updated>2024-03-07T23:16:06.866Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CIOReview: DevOps-Team is a Myth]]></title>
            <link>https://medium.com/s-group-dev/devops-team-is-a-myth-b13d3fd517eb?source=rss-4fd9db0c99c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b13d3fd517eb</guid>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Niko Kivelä]]></dc:creator>
            <pubDate>Fri, 15 Dec 2023 13:46:06 GMT</pubDate>
            <atom:updated>2024-01-27T10:57:10.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWXRRGvt52Zjxg4bKyYDrg.jpeg" /></figure><p><em>I imported the article I wrote for CIOReview here because it is as relevant as ever. By following the industry, we see how many digital organizations are adopting agile, cloud, and DevOps to level up their game, which is somehow eventually and largely followed by constraints that create inertia to their speed. We fail to focus on eliminating constraints that do not lie at the core of delivering business value.</em></p><p><em>I lead people, and those people define me in good and bad. My job has always been to drive and support teams and then guide them with the expertise I’ve gained. By driving autonomous ways of working with end-to-end responsibility, do we understand what it actually means? Where are the team boundaries, and how do we apply them? In the early stages of my career, I wrote code, fixed bugs, automated tasks, did testing, handled infrastructure, implemented monitoring, responded to incidents, debugged, and kept services running for our customers. Sounds a lot like DevOps? Actually, it’s more like Systems Thinking, under the title Systems Developer.</em></p><p><em>The problem is that back then, there were 2 (major) servers to choose from, a few security scanners, a handful of message-brokers, 2 flavors of databases, and a few mature enough frameworks to choose from — you can now multiply that by 50–200 — all that with the same team.</em></p><p><em>Modern software development and IT operations continuously manage complexity with the ever-growing demand for faster development cycles and the need for stable, reliable systems. Software development has become increasingly complicated. It is no longer sufficient for teams to evolve; organizations must also change.</em></p><p><em>We, as an organization, should be maximizing human potential. Developers are usually the most expensive part of software development. Focus on that!</em></p><p>And now, the original article…</p><p>To prepare for the future, you must understand the past. To understand the term DevOps, we must deep-dive into the original ideology behind it. When Patrick Debois first introduced the term “DevOps” in 2009, it was simply a re-arrangement of Development and Operations teams, to work towards common and non-conflicting goals. Since then, practicing DevOps has evolved, and its implementation now addresses the entire software development lifecycle management. Still, nobody seems to agree on what DevOps means. As a conceptual and holistic approach, it’s about culture, automation, lean, measuring and sharing (CALMS). The foundation for DevOps should start by establishing teams with full autonomy inside their domain to nourish the culture of ownership and innovation.</p><p>DevOps emerged to streamline software development in both the productivity of developers and the reliability of operations. Promoting a better understanding of service quality, security and foremost end-to-end accountability, it’s not about creating new teams or roles, but rather a cultural shift that impacts the entire organization. However, what started well, some organizations have regressed by creating DevOps roles and teams and delegating responsibility for infrastructure, tools, and software delivery capabilities to someone else. Where did we go wrong?</p><h3>DevOps Delegation Downfalls</h3><p>A typical challenge is understanding that DevOps is not a position, a tool, or even a process. For years, companies used to buy DevOps engineers, tools, and platforms from vendors and consultants that were trying to make a market around it. Finally, we’re ready to call it DevOps transformation, which is a cultural change in people rather than a solution you can buy. People create new habits, processes, and tools, not organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nLMlceklOolmPt0tfvr0Cg.png" /></figure><p>During my career, I’ve worked on different teams like CI (pipeline before DevOps), Platform, Microservices, and Cloud Operations, all of which were eventually referred to as DevOps teams by others. The common thing is that all these teams support other teams, and I think what happened is that old service teams are now rebranded as DevOps. Similarly, most Ops professionals who can read code are now called DevOps Engineers. What happened?</p><h3>Scaling the Human Challenge</h3><p>The problematic assumption in DevOps is, that product teams with full autonomy are expected to have end-to-end responsibility. No single product team is truly responsible for the production environment but managing their application in a production environment. With the accelerated speed of cloud computing, emerged compliance regulations and raised several integrations and technologies, no team can master them all. To manage this complexity, the product team would need very capable people with different skills, from developers to hardware experts and from QA engineers to network specialists. Having a big team with conflicting interests is hard because the slowest factor in software development is us, humans, and in the end our memory is limited. We can work asynchronously, but we scale badly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJvKcgTnyutsNOKyy2lYtw.png" /></figure><blockquote>DevOps is a culture based on a service mindset and a role, that promotes developer productivity. DevOps is not a job, but it’s an organizational strategy. Ultimately, DevOps is all about communication and in one doing.</blockquote><p>For the human mind, it’s logical to limit the scope of work by setting artificial boundaries. This is where service teams come in. They exist for a reason and are healthy for the developer experience. However, service teams should be helping product teams, not making things on-behalf of them. The best way to do it is to provide self-service solutions. One of the best examples is how public cloud providers work: they offer on-demand resources through self-service provisioning.</p><h3>Balancing Efficiency and Responsibility</h3><p>Different organizations need different team structures and capabilities for effective DevOps. Calling your rebranded Operations team or dedicating tools team “DevOps” is a huge anti-pattern. Embedding Ops people into product teams can work, but they will ultimately work from a different backlog with different priorities for stability, while businesses may prioritize speed.</p><p>If DevOps is culture and not a team, why a service team is doing things for you, on your behalf, is a huge DevOps anti-pattern? Because it violates the responsibility in the “you build it, you run it” mindset. By delegating part of your operations to another team, you’re also transferring part of the responsibility.</p><p>If product teams are expected to be responsible for all aspects of their applications and connected services, it could potentially make them too big and inefficient. This would lead to a waste of time on tasks such as updating dependencies, maintenance, and learning individual services, taking focus away from their core product. Using service teams is a must to retain software development speed and stay competitive. Same way, if every product team would implement duplicate copies of the same services other teams are using, it would not only be ineffective but create unnecessary silos.</p><h3>The Evolution of Service Teams</h3><p>Service teams often evolve into platform teams, but they have a long reputation for being inflexible, costly and a single point of failure. It’s important to treat them as a real product team with user-driven development having a visible roadmap, and clear priorities. Platform teams are an essential part of DevOps and can greatly enhance the developer experience.</p><p>Service teams working for product teams are good, but sometimes that doesn’t cover all the required knowledge. Welcome to DevOps advocacy! Our DevOps &amp; Developer Experience team helps and enables product teams and leaves ownership and knowledge to them. We provide hands-on support, do coaching, workshops, and tooling and share knowledge. To be able to support and spread awareness and practices throughout the organization, our team includes DevOps professionals, Advocates, and Security and SRE leaders with diverse backgrounds. Our team does not have an expiration date, but as product teams mature, we will work towards making ourselves redundant and transition to other areas.</p><h3>DevOps: Improving Developer Effectiveness</h3><p>Our focus is to make developers more effective and spread good practices from team to team. While it’s not feasible for product teams to possess expertise in all areas, we assist them in achieving that goal. And that’s what DevOps is all about continuous learning, and we strive to foster that mindset within our organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VtrnQ-oVXz3Bnfq9pHli2A.png" /></figure><p>For me, DevOps is a culture based on a service mindset and a role, that promotes developer productivity. DevOps is not a job, but it’s an organizational strategy. Ultimately, DevOps is all about communication and in one doing. DevOps means different things for each company and it’s a good thing, but eventually, practices will standardize. Someday, DevOps will be ready, and we will move on to the next buzzword, which might already be here… Have you heard about Developer Experience?</p><p><em>Originally published at </em><a href="https://devops.ciorevieweurope.com/cxoinsight/devopsteam-is-a-myth-nwid-1374.html"><em>https://devops.ciorevieweurope.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b13d3fd517eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/s-group-dev/devops-team-is-a-myth-b13d3fd517eb">CIOReview: DevOps-Team is a Myth</a> was originally published in <a href="https://medium.com/s-group-dev">S Group Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>