<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cross-Team-Coordination on Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/cross-team-coordination/</link>
    <description>Recent content in Cross-Team-Coordination on Robert Terakedis</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Mon, 10 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.terakedis.dev/tags/cross-team-coordination/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When the Workflow Is the Bug: Rebuilding Multi-Team Processes in Jira</title>
      <link>https://blog.terakedis.dev/post/when-the-workflow-is-the-bug/</link>
      <pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.terakedis.dev/post/when-the-workflow-is-the-bug/</guid>
      <description>&lt;p&gt;I was asked to help figure out how we could be more proactive in notifying customers of changes. My first thought: &amp;quot;We already have a release process - we just need to layer communication on top.&amp;quot; Turns out it was more complicated. The problem was that multiple teams (engineering, product management, and customer support) needed to coordinate on &lt;em&gt;infrastructure and operational changes&lt;/em&gt; (changes outside the normal software development cycle), but there was no consistent, repeatable process to make that happen. Worse, customers were finding out about changes before anyone inside had a plan to notify them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
