<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Togaf on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/tags/togaf/</link>
    <description>Recent content in Togaf on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <copyright>2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Sun, 28 Sep 2025 07:05:57 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/tags/togaf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Implementing TOGAF using SCRUM methodology</title>
      <link>https://www.shafiq.in/blog/implementing-togaf-using-scrum-methodology/</link>
      <pubDate>Sun, 28 Sep 2025 07:05:57 +0000</pubDate>
      <guid>https://www.shafiq.in/blog/implementing-togaf-using-scrum-methodology/</guid>
      <description>&lt;p&gt;TOGAF is documentation-heavy and linear. Scrum is iterative and lightweight. Running them together means breaking the Architecture Development Method into sprint-sized chunks instead of treating it as a single pass from Phase A to Phase H.&lt;/p&gt;
&lt;h2 id=&#34;mapping-adm-phases-to-sprints&#34;&gt;Mapping ADM phases to sprints&lt;/h2&gt;
&lt;p&gt;The ADM doesn&amp;rsquo;t have to run in one direction. You can treat each phase as a backlog item and pull work through in sprints.&lt;/p&gt;
&lt;table&gt;
	&lt;thead&gt;
			&lt;tr&gt;
					&lt;th&gt;TOGAF Phase&lt;/th&gt;
					&lt;th&gt;Scrum equivalent&lt;/th&gt;
			&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tbody&gt;
			&lt;tr&gt;
					&lt;td&gt;Preliminary&lt;/td&gt;
					&lt;td&gt;Sprint 0 — governance, tools, team setup&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phase A: Vision&lt;/td&gt;
					&lt;td&gt;Product backlog epics for the EA vision&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phases B-D: Business, Data, Application, Technology&lt;/td&gt;
					&lt;td&gt;One domain per sprint&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phase E: Opportunities &amp;amp; Solutions&lt;/td&gt;
					&lt;td&gt;Backlog refinement for implementation&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phase F: Migration Planning&lt;/td&gt;
					&lt;td&gt;Roadmap prioritisation&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phase G: Implementation&lt;/td&gt;
					&lt;td&gt;Delivery sprints&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Phase H: Change Management&lt;/td&gt;
					&lt;td&gt;Sprint retrospectives&lt;/td&gt;
			&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id=&#34;roles&#34;&gt;Roles&lt;/h2&gt;
&lt;p&gt;The Enterprise Architect maps closest to Product Owner — they prioritise the architecture backlog. The Architecture Board shows up at sprint reviews. The Scrum Master facilitates the process and removes blockers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
