<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Background on Kosli&#39;s Software Development Lifecycle</title>
    <link>https://sdlc.kosli.com/background/</link>
    <description>Recent content in Background on Kosli&#39;s Software Development Lifecycle</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://sdlc.kosli.com/background/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Governance Bottleneck</title>
      <link>https://sdlc.kosli.com/background/governance-bottleneck/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://sdlc.kosli.com/background/governance-bottleneck/</guid>
      <description>&lt;h1 id=&#34;why-software-delivery-governance-matters&#34;&gt;&#xA;  Why Software Delivery Governance Matters&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#why-software-delivery-governance-matters&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;The modern world runs on mission-critical software. Organizations building this&#xA;software face a paradox: they need to move fast to stay competitive, but they&#xA;also need rigorous governance to manage risk.&lt;/p&gt;&#xA;&lt;p&gt;Engineering teams have spent over a decade investing in DevOps and cloud&#xA;technologies, automating their way to multiple deployments per day. Meanwhile,&#xA;governance processes remain stubbornly manual and slow. A single line of code can&#xA;require dozens of manual steps, multiple approvals, and weeks of waiting — all&#xA;while providing little actual risk reduction.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Controls Engineering</title>
      <link>https://sdlc.kosli.com/background/controls-engineering/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://sdlc.kosli.com/background/controls-engineering/</guid>
      <description>&lt;h1 id=&#34;controls-engineering&#34;&gt;&#xA;  Controls Engineering&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#controls-engineering&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;Controls Engineering is the application of modern software engineering practices&#xA;to the domain of governance, risk, and compliance. Think of it as asking: &amp;ldquo;What&#xA;would happen if we applied software engineering to compliance and risk&#xA;management?&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;This is analogous to how Google created Site Reliability Engineering (SRE) by&#xA;asking what would happen if software engineers did operations work. Controls&#xA;Engineering asks the equivalent question for governance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
