<?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 Darije Ramljak on Medium]]></title>
        <description><![CDATA[Stories by Darije Ramljak on Medium]]></description>
        <link>https://medium.com/@darije.ramljak?source=rss-bab57e88eac9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*QOeTbkqwrxXiB1ndIeyd6g.jpeg</url>
            <title>Stories by Darije Ramljak on Medium</title>
            <link>https://medium.com/@darije.ramljak?source=rss-bab57e88eac9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:40:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@darije.ramljak/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[Agile portfolio management and the role of Enterprise Architect]]></title>
            <link>https://medium.com/@darije.ramljak/agile-portfolio-management-and-the-role-of-enterprise-architect-9dab789beba1?source=rss-bab57e88eac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dab789beba1</guid>
            <category><![CDATA[enterprise-architect]]></category>
            <category><![CDATA[portfolio-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[transformation]]></category>
            <dc:creator><![CDATA[Darije Ramljak]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 17:01:15 GMT</pubDate>
            <atom:updated>2023-04-03T17:01:15.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MfUUGIBh9KbvaamoWgA8-Q.png" /></figure><p>Why agile initiatives need portfolio management in the first place? Just imagine, what would happen if we were to run multiple agile initiatives without mutual alignment, control and not being able to figure out what is important to business.</p><p>To start with, there is a risk that the organization may not be able to achieve its strategic objectives, because it may be investing resources in projects that do not align with its overall strategy. Furthermore, without portfolio management, the organization may not have a clear understanding of its resource constraints and may end up overcommitting resources to projects, leading to delays, cost overruns, and potentially the failure of critical initiatives.</p><p>A list of key risks that an organisation running agile initiatives without proper portfolio management will face:</p><ol><li>Lack of alignment with business objective</li><li>Resource conflicts</li><li>Difficulty in prioritizing initiatives</li><li>Lack of visibility into project status</li><li>Limited scalability</li></ol><p>One of the scaled agile frameworks that I really like is SAFe (Scaled Agile Framework), a popular approach to managing large-scale software development projects. Portfolio management in SAFe is focusing on strategic alignment of business initiatives with the enterprise’s goals and objectives. It focuses on effectively addressing those risks and enabling scalability of agile initiatives. In order to grow from one agile initiative to the enterprise agile program with multiple initiatives that affect the whoe enterprise, portfolio management is the key ingredient.</p><blockquote>The primary goal of portfolio planning is to <strong>allocate an organization’s limited resources to the various products in an economically sensible way</strong>.</blockquote><p>Delving deeper into portfolio management domain, we can observe that the Portfolio Vision describes the <strong>future state </strong>of a portfolio’s <strong>Value Streams </strong>and <strong>Solutions</strong> and describes how they will cooperate to achieve the portfolio’s objectives and the broader aim of the Enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZn9PevzjvEoPhgzY9c5bA.png" /><figcaption>SAFe Portfolio flow — connecting Portfolio Vision to Value Streams</figcaption></figure><p>So, how does Enterprise architecture fit in and what is EA’s key role?</p><p>Enterprise architecture, in general, is the process of translating the business vision and strategy into effective technology plans. It drives promotion of adaptive design and engineering practices to drive architectural initiatives (enabler epics) for the portfolio. In addition, it <strong>facilitates</strong> the <strong>reuse</strong> of hardware and software components and proven patterns across a portfolio</p><p>With the fast changing market conditions and enterprise environments, the changes to <strong>achieve</strong> the desired <strong>future state </strong>defined by the Portfolio Vision will require implementing <strong>large initiatives</strong> (Epics)</p><blockquote>The key concept introduced as a mini building-block to cover the foundational gaps required by large initiatives, or element that cuts across them is — an ENABLER.</blockquote><p>In SAFe, “enablers” refer to activities, events, or other types of work that support the delivery of solution and value to stakeholders, but don’t directly produce a usable solution.</p><p>The role of enablers in portfolio initiatives is to provide the necessary support to the delivery of value, such as governance, compliance, and architecture activities. Enablers can be cross-cutting activities, or specific to a particular initiative. They ensure that the solution is built in a manner that is aligned with the organization’s overall strategy and goals.</p><p>Enablers are related to the enterprise architecture domain because they help ensure that solutions are aligned with the organization’s overall architecture, and support the implementation of the architecture. This alignment helps to ensure that solutions are scalable, secure, and support the organization’s overall goals.</p><p><strong>Usually business epics</strong> directly deliver <strong>business value</strong>, while <strong>enabler epics</strong> are used to <strong>advance</strong> the <strong>Architectural Runway</strong> to support upcoming business or technical needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2mU2H8ZLhnw4Q3V2ssExA.png" /><figcaption>How architectural runway evolves to support business neds</figcaption></figure><p>The Architectural Runway consists of the existing code, components, and technical infrastructure needed to implement near-term features without excessive redesign and delay. It supports the continuous flow of value through the Continuous Delivery Pipeline, providing the necessary technical foundation for developing business initiatives and implementing new Features and/or Capabilities. The architectural runway is one of the primary tools used to implement Agile Architecture strategy. Since the development of new features and capabilities consumes the architectural runway, a continual investment must be made to extend it by implementing Enablers.</p><p>Some enablers address shortcomings with the current Solution, such as improving its performance or User Experience. Others provide foundational capabilities that will be used to support future functionality. These foundational capabilities are the elements of focus for Enterprise architect and they key mean of aligning business vision with technological roadmap.</p><p>The architecture of a system can either accelerate or impede the ability to provide frequent, independent releases for the business to meet its objectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dEXrqpcq3M0lGo0wwwYRzg.png" /><figcaption>Enterprise Architect’s responsibilities</figcaption></figure><p>Agile enterprise architects support business alignment by optimizing the architecture to support the end-to-end value stream. This enables the business to achieve its goal of continually delivering ‘value in the shortest sustainable lead time’. Agile enterprise architects lead this process by supporting “just enough” architectural runway to support evolving business needs.</p><p>To support the continuous flow of value through the Continuous Delivery Pipeline, Agile Enterprise Architecture:</p><ul><li>Evolves over time while supporting needs of current users</li><li>Avoids overhead and delays associated with phase-gate and Big Up Front Design (BUFD)- methods</li><li>Ensures the ‘system always runs’</li><li>Balances emergent design and intentionality</li><li>Takes a systems view across the full value stream</li></ul><p><strong>A final thought</strong></p><p>After getting some understanding why Portfolio management is a foundational element for properly running multiple agile initiatives within the enterprise, and getting introduced into a concept of enabler and the role it plays from Enterprise architecture perspective, we can summarize with the following point of view.</p><p>From an enterprise architect’s point of view, portfolio management involves the following:</p><ol><li>Align business initiatives with the enterprise’s strategy: Enterprise architects work with stakeholders to identify and prioritize initiatives that support the enterprise’s overall strategy and goals.</li><li>Assess risk and value: Enterprise architects assess the potential risks and benefits of each initiative, taking into account the organization’s resources, capabilities, and constraints.</li><li>Create a roadmap: Enterprise architects develop a roadmap that outlines the implementation of the selected initiatives over time, taking into account dependencies, milestones, and resource allocation.</li><li>Monitor progress: Enterprise architects monitor the progress of each initiative and track key performance indicators to ensure that the initiative is on track to deliver the expected outcomes.</li><li>Make course corrections: Enterprise architects work with stakeholders to identify and address any obstacles or issues that arise during the implementation of the initiative, making course corrections as needed.</li></ol><p>To conclude, portfolio management helps enterprise architects ensure that business initiatives are aligned with the enterprise’s goals, are executed efficiently, and deliver the expected outcomes. Potfolio management ensures we are doing the right thing, and enterprise architecture ensures we do the things right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dab789beba1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Human centricity in Agile EA]]></title>
            <link>https://medium.com/@darije.ramljak/human-centricity-in-agile-ea-622f7e0d54cc?source=rss-bab57e88eac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/622f7e0d54cc</guid>
            <category><![CDATA[human-centric-design]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[agility]]></category>
            <dc:creator><![CDATA[Darije Ramljak]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 16:31:01 GMT</pubDate>
            <atom:updated>2022-03-14T16:31:01.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*F72Y399nDmmZER4LgZ4itw.png" /></figure><p>Enterprise Architecture’s role and primary goal throughout the history of use has been very technically driven and oriented. Initiatives usually started with business context in mind, bridging the proverbial business-IT gap, but still the majority of the EA work focused on application/information and infrastructure layer.</p><p>This certainly should not be the case. Looking at the key EA mandate, it should be oriented towards helping organisations realize their future goals and objectives.</p><p>Simply checking the details of the first Phase in TOGAF Architecture — creation of Architecture vision, we can understand that:</p><blockquote>The Architecture Vision is essentially the architect’s “elevator pitch” — the key opportunity to sell the benefits of the proposed development to the decision-makers within the enterprise.</blockquote><blockquote>The goal is to articulate an Architecture Vision that enables the business goals, responds to the strategic drivers, conforms with the principles, and addresses the stakeholder concerns and objectives.</blockquote><p>But there is a twist. In order to create a great elevator pitch for decision makers, essentially our stakeholders, we primarily need to understand their challenges, desires and goals.</p><blockquote>Too often Architecture vision starts with immediate focus on specific business goals, drivers and addressing enterprise wide challenges.</blockquote><blockquote>In doing so, it fails to understand personal concerns and challenges of key stakeholders that should stand behind and support this vision.</blockquote><p>The key stakeholders and their concerns are addressed fairly late within Architecture vision building, when majority of the business goals and drivers are already identified. Significant drawback of this approach is that identification of those concerns and issues is already framed by a specific business goal and misses the point of addressing EA as key communication tool.</p><p>In Agile EA we need to strive for EA to be more people-centric, understanding key needs, objectives and challenges of our stakeholders and showing results fast. On top of this, we need to provide a way to link resolution of their personal objectives and challenges with broader context and enterprise wide initiatives. Having this human-centric focus, Agile EA effectively becomes a great communication tool or a sound board for new ideas.</p><p>A great technique that works well to start empathising with key stakeholders is Agile EA discovery workshop, derived from Business Framing Workshop in IBM Garage methodology.</p><p>This technique entails a set of fairly simplistic activities, performed in a design thinking workshop style:</p><ol><li>List your organisation stakeholders (roles)</li><li>Identify and list their key concerns and pain points</li><li>Ideate on how resolving those concerns and pain-points could benefit the organisation</li><li>Map the key ideas to EA domains as goals</li><li>Prioritise ideas/goals (Impact vs. Feasibility)</li><li>Outline EA goal statement for top three goals</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcdTmVijS1XB31ZThS2KMg.png" /></figure><p>Now the question is where and how to start with this practice. There are two distinct entry points where it could yield the best result:</p><ol><li>At the start of new EA initiative — multiple ideas to explore as initiatives</li><li>Finding improvement areas in the new EA cycle — resembling usual Scrum retrospective with finding one new thing to improve</li></ol><p>Start your new EA initiative or improve the new EA cycle with human-centric approach like this and you will experience better definition of your EA vision and better ownership of EA initiatives by your key stakeholders.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=622f7e0d54cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agility in Enterprise Architecture]]></title>
            <link>https://medium.com/@darije.ramljak/agility-in-enterprise-architecture-a15444739df5?source=rss-bab57e88eac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a15444739df5</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Darije Ramljak]]></dc:creator>
            <pubDate>Fri, 31 Dec 2021 17:10:08 GMT</pubDate>
            <atom:updated>2021-12-31T17:15:43.685Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to make the elephant dance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*sLag9FG5dEuIJuPcfFW2Mg.jpeg" /></figure><p>Thinking about Enterprise Architecture (EA) and the role it plays within the enterprise, I can’t think of a better analogy than of a dancing elephant. The sheer name of Enterprise Architecture evokes the idea of something large, complex, heavy and effort intensive.</p><p>Looking at the Gartner definition of EA though, it seems that it should be nimble enough to help organisation tackle disruptive changes on the market.</p><blockquote>Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analysing the execution of change toward desired business vision and outcomes. (Gartner)</blockquote><p>The sad reality was that very often Enterprise Architecture setup and implementation in the organisation became very rigid, kind of an “ivory tower” type of architectural governance. Instead of helping, it very often hindered development of new solution architectures even in the world of old-style waterfall or iterative/RUP (Rational Unified Process) software methodology frameworks. Complex EA models and sometimes heavy upfront investment required for introducing changes into business architecture, information system application or technology models started to be circumvented by solution delivery teams making EA obsolete and stale very quickly.</p><p>During the last decade we are experiencing steady adoption of agile culture, frameworks, and practices in mainstream software development. Proliferation of cloud native development practices, world of MVPs and agile deliveries, faster time-to-market and lean disciplines is introducing a mindset of focusing on customer value delivery with as minimum upfront planning and design as possible. The architectural model being used here is labelled as Emergent architecture</p><blockquote>It’s very natural to ask a question whether EA has any relevance in this kind of agile software development world where design itself cultivates a laissez faire approach.</blockquote><p>But what happens when large enterprises start adopting agile principles and soon find out that methodologies and techniques that worked perfectly fine for their new small product or service initiative are not scalable across the entire organisation and do not work on the long run? It turns out that missing ingredients for scaling call out for elements usually provided by EA, but likely need it in a different flavour and packaging. Let’s put a name on this “improved” EA and label it as Agile EA.</p><p>Agile Enterprise Architecture seems to be asking for a way to combine two architectural styles — Emergent architecture design and Intentional architecture design.</p><blockquote>Emergent design enables fast, local control so that teams can react appropriately to changing requirements without excessive attempts to future-proof the system (SAFE)</blockquote><p><em>Emergent design</em> aligns perfectly with the way architecture is constructed using agile delivery models, making local, fast design decisions and organically growing the solution complexity, but very often using this principle alone results in technical debt and waste as the solution grows in complexity.</p><blockquote>Intentional architecture design provides the guidance needed to ensure that the whole system has conceptual integrity and is fit for its purpose. (SAFE)</blockquote><p><em>Intentional architecture</em> on the other hand ensures that enough upfront analysis and design work has been made in order to link required business capabilities into architectural enablers that are robust to satisfy long term requirements and produce robust technical decisions and guidance for solution delivery.</p><p>Several scaled agile frameworks and methods already provide a good example where Enterprise Architecture became the core discipline, providing a structured way to ensure scalability of agile practices and operationalise enterprise business strategy.</p><p>Scaled Agile Framework (SAFE) or PMI Disciplined Agile are good examples that bring a lot of focus on EA role in translating business vision into tactical business and technology roadmaps (backlog) although they need to be better aligned with regular EA frameworks that organisations widely use (e.g., The Open Group Enterprise Architecture Framework — TOGAF).</p><p>Additional improvements in this domain came with The Open Group introducing a new standard in September 2020, Open Agile Architecture. Naturally, first set of discussions questioned whether it would replace currently widespread used EA framework TOGAF or not. The answer was clear, it will complement it.</p><p>There is clearly a need for Agile EA, especially with larger organisations introducing agile culture and delivery models. It has to be simpler, fit for purpose, nimble and above all find a way how to democratise architectural work, i.e., balance emergent and intentional design.</p><p>In my past few consulting and larger solution delivery engagements I’ve used several techniques to make Agile EA work and will share few concepts and examples in the series of articles that will follow.</p><p>Let’s see how to make this elephant dance…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a15444739df5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>