<?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 Stephen Crockett on Medium]]></title>
        <description><![CDATA[Stories by Stephen Crockett on Medium]]></description>
        <link>https://medium.com/@stephen-crockett?source=rss-8cd329cb306e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pEdvNMuFAzPGhkMV</url>
            <title>Stories by Stephen Crockett on Medium</title>
            <link>https://medium.com/@stephen-crockett?source=rss-8cd329cb306e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:02:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stephen-crockett/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[Evolving Architecture]]></title>
            <link>https://medium.com/prospa-technology/evolving-architecture-849e017fd345?source=rss-8cd329cb306e------2</link>
            <guid isPermaLink="false">https://medium.com/p/849e017fd345</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software-maintenance]]></category>
            <category><![CDATA[agile-architecture]]></category>
            <dc:creator><![CDATA[Stephen Crockett]]></dc:creator>
            <pubDate>Sun, 07 Apr 2024 08:52:12 GMT</pubDate>
            <atom:updated>2024-04-30T23:56:40.244Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Part 4 of the Agile Architecture Series</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UG5IHo1MfRfkNqhy" /><figcaption>Photo by <a href="https://unsplash.com/@jplenio?utm_source=medium&amp;utm_medium=referral">Johannes Plenio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When do we know that it is time to update or move on from an architecture or system that has served us well for many years?</p><p>Here are the signs to watch out for -</p><ol><li>Your best engineering capacity is used for maintenance and break-fix rather than new product features.</li><li>The Software you are using is not supported or is many versions behind the current release.</li><li>Non-functional requirements are no longer good enough. Information is not available when needed, and overnight batch updates are no longer good enough.</li><li>Something like AI Large Language Models comes by, smacks you in the back of the head, and creates an arms race between you and your competitors.</li></ol><h3>Predicting the Future can be Too Hard</h3><p>In the previous article in this series, <a href="https://medium.com/prospa-technology/agile-enterprise-architecture-0c24aa5d5085">Agile Enterprise Architecture</a>, I suggested that Enterprise Architecture could be used to predict the future.</p><p>Even if we find it too hard to predict the future and implement the perfect architecture, Architecture should be ready to change and adapt, even if we don’t know how it needs to change (yet).</p><p>You must be prepared to —</p><ol><li>Keep the Architecture Clean.</li><li>Keep the Architecture Current</li></ol><h3>Cleaning Our Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MScOvEOHUDvmHIv5" /><figcaption>Photo by <a href="https://unsplash.com/@mkjr_?utm_source=medium&amp;utm_medium=referral">mkjr_</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One of the ways that we get ready for change is to keep our Architecture contemporary and “clean”, many of you may have read <a href="https://amzn.to/4aBneEl">Clean Code by Robert C.Martin</a>. In “Uncle” Bob’s book, there are a couple of themes that we can learn from and apply to architecture as a whole.</p><ol><li><strong>First, write dirty code and then clean it</strong>. The architecture we produce will initially have Technical Debt; we can’t always afford (or even know) the perfect solution when we are building it. Be prepared to come back and clean it up.</li><li><strong>Successive Refinement.</strong> Just like a program module that started well but did not scale, an Architecture can become irrelevant or not meet our customers’ needs.</li></ol><h4>Change is Normal — Refactoring is Good</h4><p>If you were to look at your architecture now, what are the key problems consuming your precious engineering capacity, and how can architecture refactoring help. Here are some examples:</p><ul><li>Tight coupling between two of your systems means there needs to be more resilience when one system is unavailable. Can we re-architect the interfaces so there are fewer dependencies?</li><li>A system is strongly dependent on an outdated, expensive vendor solution. Can we implement an adaptor pattern that allows us to easily unplug and plug in a new provider?</li><li>Supporting an old system is complex and challenging. Can we uplift the monitoring and logging of the system to make it easier to detect and prevent issues?</li><li>The business is no longer happy to wait overnight for reports and key metrics from the core systems. Let’s introduce event streaming and replace some of the legacy batch processing.</li><li>There are many other examples; what’s your problem, and what can you do to solve it?</li></ul><p>Of course, this work must also compete with other essential features that the business has planned. So put on your best suit (or T-Shirt) and sell. Everyone loves a great story! Especially one that has a happy ending.</p><h3>Keep the Architecture Current</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*II5tAPfmhATB006C" /><figcaption>Photo by <a href="https://unsplash.com/@serhatbeyazkaya?utm_source=medium&amp;utm_medium=referral">Serhat Beyazkaya</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The best way to keep Architecture current is to keep it updated. I want to propose a simple architectural principle that encapsulates this concept: the<strong> N-1 Rule</strong>.</p><h4>The N-1 Rule</h4><p>The N-1 Rule (Principle) goes something like this -</p><p><strong>Principle: </strong>All software used should not fall behind more than one version from the Vendor’s major release cycle.</p><p><strong>Why is this important?</strong> It is quite easy to let vendor software, database versions, and frameworks get outdated. Continuous system updates are crucial for maintaining a robust and secure technology landscape. The rationale for doing this includes:</p><ul><li>Keep up to date with Security Enhancements and Software vulnerabilities.</li><li>Bug Fixing and improvement to system stability and performance.</li><li>Compatibility and Interoperability with other connected systems</li><li>Feature Enhancements in new releases can be leveraged.</li></ul><p>Using this principle is one of the easiest to follow. All (major) software vendors provide a timetable for their software release cycles — they don’t just announce it the week before. There is plenty of time to plan the cost of upgrades that can be included in your company’s budget cycles.</p><p>When your software is contemporary, you will have more choices and you can take advantage of investments that your vendors and SaaS providers are making.</p><h4>Consequences of doing nothing</h4><p>We’ve all seen the system that just keeps running. Perhaps the software is old, the source code is lost, frameworks and database versions are no longer supported.</p><p><strong>Step 1.</strong> The software just keeps running … until it doesn’t, there is a security breach, or the key person who maintains it leaves or some other calamity. Customer and business trust is broken!</p><p><strong>Step 2.</strong> In a panic management order a review of the system and find out that it has outdated software and needs updates and rewrites.</p><p>Usually, a one-off figure of a squillion dollars is needed to keep the system going. Starting an Evergreen program now could be a much better proposal (perhaps using the N-1 Rule as a guide).</p><h3>Summary</h3><p>Change is normal; don’t expect your architecture to live forever.</p><ol><li><strong>Watch out for signs that your architecture is outdated</strong>. Usually, that means that your engineering capacity is being consumed mostly by keeping the lights on.</li><li><strong>Look for Opportunities to refactor your architecture.</strong> And align these initiatives with the challenges that the business is having with this software system.</li><li><strong>Keep your Software and Vendor versions up to date. </strong>This is not only good hygiene, but it also allows you to quickly take advantage of new capabilities like AI LLM that vendors are starting to offer in their latest software releases.</li></ol><p><em>Thanks, and I hope you enjoyed this series on Agile Architecture. Other blogs in the series include:</em></p><p><a href="https://medium.com/prospa-technology/architecturally-significant-decisions-68ac47687277">Architecturally Significant Decisions | by Stephen Crockett | Technology @ Prospa | Medium</a></p><p><a href="https://medium.com/prospa-technology/emerging-vs-intentional-architecture-385071ae5d75">Emerging vs Intentional Architecture | by Stephen Crockett | Technology @ Prospa | Medium</a></p><p><a href="https://medium.com/prospa-technology/agile-enterprise-architecture-0c24aa5d5085">Agile Enterprise Architecture. Part 3 of the Agile Architecture Series | by Stephen Crockett | Technology @ Prospa | Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=849e017fd345" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prospa-technology/evolving-architecture-849e017fd345">Evolving Architecture</a> was originally published in <a href="https://medium.com/prospa-technology">Technology @ Prospa</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Enterprise Architecture]]></title>
            <link>https://medium.com/prospa-technology/agile-enterprise-architecture-0c24aa5d5085?source=rss-8cd329cb306e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c24aa5d5085</guid>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[big-rock]]></category>
            <dc:creator><![CDATA[Stephen Crockett]]></dc:creator>
            <pubDate>Sat, 27 Jan 2024 21:04:21 GMT</pubDate>
            <atom:updated>2024-01-28T23:34:34.478Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Part 3 of the Agile Architecture Series</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G236aob_gApge_Mf" /><figcaption>Photo by <a href="https://unsplash.com/@dbeamer_jpg?utm_source=medium&amp;utm_medium=referral">Drew Beamer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Making it to number 35 in the Top 100 superpower list is being able to predict the future (“Precognition” ign.com). Besides the obvious personal gains, it could be pretty valuable for product design and architecture work.</p><p>Wouldn’t it be great if, when we are making arbitrary design solutions while building out our brand-new product, we could predict the future and know which design will be the best in 5 years?</p><p>What if our software was truly agile, and we could tweak it to take advantage of market changes and user demand.</p><p>How about maximising our engineering capacity without too much backtracking and waste?</p><h3>Enterprise Architecture</h3><p>In the first two parts of the Agile Architecture Series, I’ve been focusing more on Solution Architecture. Solution Architecture is about developing the “best” design/architecture for a particular problem or project.</p><p>One of the things missing, however, is a guiding light that sits outside the project and helps us choose the right pathway or solution for the overall product and organisation. … something that has a longer-term view and is aligned with the big goals (or Big Rocks) that the organisation aspires to.</p><h4>Solution Architecture vs Enterprise Architecture</h4><p>If you are lucky to have a title (or role) of just “Architect”, how do you know if you are doing Solution Architecture or Enterprise Architecture? I use this simple rule.</p><ul><li>Solution Architecture is what your boss asks you to work on. Usually they are the important and/or urgent projects.</li><li>Enterprise Architecture is what you need to work out for yourself which is critical for the business’s long-term success.</li></ul><h4>Can Enterprise Architecture Predict the Future?</h4><p>Sure! In a way ... maybe.</p><p>Enterprise Architecture can help predict the future by enabling organisations to build in an agile way. By creating flexible frameworks and architectures that adapt to changes, businesses can anticipate and respond to emerging trends and challenges more effectively.</p><p>Enterprise Architecture promotes a structured approach to understanding an organisation’s current state, defining its desired future state, and charting a path. Through this process, organisations can identify potential risks, opportunities, and market shifts, allowing them to proactively adjust their strategies and operations.</p><h4>What are the Steps to Developing an Enterprise Architecture (that can predict the future)?</h4><ol><li>Identify the important stuff or Big Rocks.</li><li>Know your Current State &amp; Status.</li><li>Map out your Future State.</li><li>Govern your Future State.</li></ol><p>These things are familiar in the world of Architecture and Strategy. We sometimes forget about developing and using our Enterprise Architecture when we are neck-deep in Agile sprints.</p><p>Having Current State and Future State roadmap artefacts produced from an Enterprise Architecture practice can help us with context and meaning when planning our agile delivery.</p><h3>The Important Stuff — The Big Rocks</h3><p>There will always be Urgent and Important work to do.</p><blockquote>“If everything is important, then nothing is.” ― Patrick Lencioni</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sFqQjRKJOgrOlXhB" /><figcaption>Photo by <a href="https://unsplash.com/@heftiba?utm_source=medium&amp;utm_medium=referral">Toa Heftiba</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you are surrounded by lots of urgent and vital work, these things are not your Big Rocks. You will need to look harder.</p><ul><li>What is the company’s Vision / Strategy / Goals?</li><li>Who are your stakeholders? Who are the leaders with the long-term vision?</li><li>It’s effortless to identify (and get distracted by) the low-hanging fruit. Let someone else take the lead on those things. Keep your focus on the Big Rocks.</li></ul><h3>Know your Current State &amp; Status</h3><p>After you work out your Big Rocks, you must understand what you have and how it works. In the words of the great TV personality —</p><blockquote>“You can’t change what you don’t acknowledge.” — Dr. Phil McGraw</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lUcKQ-tSxhjCPLk-" /><figcaption>Photo by <a href="https://unsplash.com/@ricardoviana?utm_source=medium&amp;utm_medium=referral">Ricardo Viana</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Capabilities, not Processes or Systems.</h4><p>When building out your current state, it’s easy to list all the systems and connect them together. But it doesn’t always tell you what you need to know.</p><p>If I was to have something like Salesforce in my current state. What is that telling me? Is that the Customer Master? Is it the customer service platform? Is it the Sales platform…</p><ol><li>Lead with your capability (E.g. Customer Management, Product Servicing, Payments, etc.).</li><li>Map the system to the capability.</li><li>Make an assessment of the capability. What are the issues?</li></ol><h4>Fast-tracking this part</h4><p>In general, generating a current state architecture takes time and effort. But there are some things that you can do to fast-track the process.</p><ul><li>Usually, a new Enterprise Architecture initiative can be built on the remains of a previous Enterprise Architecture attempt. If you dig hard enough, you might find some valuable artefacts.</li><li>Does the organisation have a CMDB? (Configuration Management Database). A good CMDB will have all your systems, descriptions and business and technology contacts.</li><li>Use an industry framework to give you a head start. Personally, I like BIAN (<a href="https://bian.org/">bian.org</a>). It has a great capability model for banks and financial institutions. Using a framework like BIAN will help you understand what capabilities you are missing, capability areas that are underdeveloped, and capability areas that are duplicated.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bw0xFc8w1i_rrQ1Jq46CIg.png" /><figcaption>BIAN Service Landscape</figcaption></figure><h3>Map out your Future State</h3><blockquote>“Without a clear destination in mind, every decision becomes arbitrary” — Unknown.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JPmURoVXYkZYcPtQ" /><figcaption>Photo by <a href="https://unsplash.com/@anniespratt?utm_source=medium&amp;utm_medium=referral">Annie Spratt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What does a Roadmap look like?</h4><p><strong>Part 1 — The Basics</strong></p><p>These are the essential ingredients that come out of an Enterprise Architecture practice.</p><ol><li><strong>Principles. </strong>Just a few principles aligned with the company’s values are enough. Principles are the “does it make sense” test when evaluating solutions.</li><li><strong>Standards.</strong> Standards help build consistency in your technology stack.</li><li><strong>Patterns</strong>. Help you to be more agile and consistent.</li></ol><p><strong>Part 2 — The Specifics — Capability and Portfolio Roadmaps</strong></p><p>Now that you have your current state worked out and have understood the issues and challenges around it, visualise what it will look like in a few years.</p><ul><li><strong>Capability Journeys. </strong>Express the change needed for Automation Targets, addressing Operational Risk, Scalability, etc. Work out what is essential to improve a capability to meet the “Big Rocks”.</li><li><strong>Portfolio Roadmaps.</strong> Now that we understand the capabilities that need to be uplifted to meet our Big Rocks, have a good look at the Product portfolios and start to think in terms of “Invest”, “Retire”, and “Transform”.</li></ul><h4>Create some Marketecture.</h4><p><em>Marketecture = A non-technical document to explain your architecture to anyone.</em></p><p>Now that you have worked out what you currently have and your target state, summarise it on a one-pager. Carry the one-pager around with you and show it to everyone.</p><p>Your Marketecture will show —</p><ol><li>Your current systems and capabilities</li><li>Systems and capabilities that you are investing in.</li><li>Systems that have issues or are on the way out (perhaps colour-coded)</li></ol><p><em>It might be more than one page, but not more than four. (I used to do an origami fold that showed a few different views on a single A3)</em>.</p><h3>Govern your Future State</h3><p>In <a href="https://medium.com/prospa-technology/emerging-vs-intentional-architecture-385071ae5d75">Part 2 of the Agile Architecture Series</a>, I talk about “Trust but Verify”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PnZoPlFNoD9BwluS" /><figcaption>Photo by <a href="https://unsplash.com/@marekpiwnicki?utm_source=medium&amp;utm_medium=referral">Marek Piwnicki</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We want our Agile teams to run fast and build awesome stuff. We also don’t like them making arbitrary design decisions that don’t consider the organisation’s long-term “Big Rock” goals.</p><p>The Answer is (can be) simple.</p><ol><li>Ensure everyone knows the roadmaps, where we want our Capabilities and Product Portfolios to be in a few years.</li><li>Put some light governance in place to ensure that architecture and designs are reviewed before implementation.</li></ol><h3>Summary</h3><p>So, while Enterprise Architecture may not offer a crystal-clear view of the future, its emphasis on agility and adaptability empowers organizations to make informed decisions and navigate future challenges with greater confidence and resilience.</p><p>So —</p><ol><li>Know Your Big Rocks — What is truly important.</li><li>Understand your current state and status. (Think in terms of Capabilities)</li><li>Map out your Future State</li><li>Govern your Future State</li></ol><p><em>In the next and final part of the Agile Architecture series, I will address the issue of what we do with legacy and the need for Architecture refactoring.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c24aa5d5085" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prospa-technology/agile-enterprise-architecture-0c24aa5d5085">Agile Enterprise Architecture</a> was originally published in <a href="https://medium.com/prospa-technology">Technology @ Prospa</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emerging vs Intentional Architecture]]></title>
            <link>https://medium.com/prospa-technology/emerging-vs-intentional-architecture-385071ae5d75?source=rss-8cd329cb306e------2</link>
            <guid isPermaLink="false">https://medium.com/p/385071ae5d75</guid>
            <category><![CDATA[architecture-pattern]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[agile-architecture]]></category>
            <dc:creator><![CDATA[Stephen Crockett]]></dc:creator>
            <pubDate>Mon, 20 Nov 2023 06:28:42 GMT</pubDate>
            <atom:updated>2023-11-23T01:01:57.631Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Part 2 of the Agile Architecture Series</em></p><p>If you’ve seen <a href="https://medium.com/prospa-technology/architecturally-significant-decisions-68ac47687277">Part 1 of the series</a>, you may be able to recognise One-way or Two-way decisions when it comes to Architecture (or life in general). How do we go about architecting solutions now that we know how vital or “permanent” the decision is?</p><p>Let’s start with the two extremes of architecting; Emerging and Intentional.</p><h4>Emerging Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qn7AvH92tgb9Kyhm" /><figcaption>Photo by <a href="https://unsplash.com/@martijnbaudoin?utm_source=medium&amp;utm_medium=referral">Martijn Baudoin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Architecture is quite informal and is usually determined after the solution is built (or as part of building the solution).</p><p><em>Typical steps involved</em></p><ol><li>BUILD</li><li>Document Architecture (optional)</li></ol><h4>Intentional Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GQPKu6wAET1EiFSy" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Architecture is planned, documented, debated, approved, and then the solution is built.</p><p><em>Typical Steps involved</em></p><ol><li>Discuss / Debate Architecture</li><li>Document Architecture</li><li>Approve Architecture</li><li>Build</li><li>Document actual Architecture (optional)</li></ol><p><strong>spoiler alert:</strong> I don’t think Emerging Architecture or Intentional Architecture is Agile Architecture.</p><p>A quick summary of One-way and Two-way decisions. One-way decisions are difficult to change and should be more considered, whereas Two-way decisions can be changed (without a lot of impact) and should have a lighter governance touch.</p><ul><li>Intentional Architecture is still needed when looking at One-Way decisions. You need to get a consensus that you are making the right choices and that all the stakeholders have bought into the future state architecture.</li><li>We can’t always afford the effort of Intentional architecture for our Two-Way decisions. We also don’t want our architecture to just emerge based on a conversation in a one-hour sprint planning session.</li></ul><h3>Trade-offs</h3><p>Emerging vs Intentional Architecture appears to be about trade-offs that you need to make when you are designing a system.</p><h4>Sometimes Agile = Emerging Architecture or “Architecture Free”</h4><p>When I think about Agile, it is usually about choosing</p><ol><li>Immediate Value (aka the MVP)</li><li>Ensuring Teams have the Autonomy to run as fast as they can</li><li>Being Agile and Responsive to Customer Needs.</li></ol><p>Interestingly enough, these Agile goals are usually the bane of the Architect, where teams use the Agile mantra to load up on Technical Debt and never quite tackle the big problems, or drive the big solutions that will help organisations with their long-term strategic goals.</p><p>On the other hand, when (formally) architecting a solution we look to</p><ol><li>Maximum Value at the expense of immediate value.</li><li>Seek Opportunities for Reuse and synergy across Teams instead of seeking Autonomy.</li><li>Be Forward-thinking (i.e. Slow) instead of Agile and Responsive.</li></ol><p>So what we appear to have is a fundamental dichotomy of goals that are equally important but seem to have trouble living together.</p><h4>Immediate Value vs Maximum Value</h4><p>So where do we set this dial?</p><ul><li>Do I want 50% of the possible value of an opportunity within 1 month or wait for 90% of the possible value in 10 months?</li></ul><p>And the answer is → It depends. What a great discussion to have with your stakeholders!</p><h4>Autonomy vs Reuse</h4><p>So what is more important?</p><ul><li>What you know? OR</li><li>Who you know?</li></ul><p>So a totally unsubstantiated hypothesis is that -</p><p>H1. Engineers like being autonomous and keeping to themselves because as a group they are mostly Introverts.</p><p>H2. Engineers are a very clever group of people and what they need to do can be done quicker if they don’t need to talk to anyone.</p><p>H3. Reuse won’t happen, unless Engineers are forced or have an incentive to look within the organisation for possible reuse.</p><p><em>Some ideas for unlocking reuse .. coming up</em></p><h4>Agile and Responsive vs Forward Thinking</h4><p>It is very rare, when looking at a plan for a new feature or some uplift of functionality that I see time carved out to understand and get the architecture right.</p><p>Usually, there is an expectation that “build” will start the week following the kick-off / sprint-planning / discovery workshop, etc. As architects, we don’t then have a lot of time to draw rectangles on whiteboards and stare out the window looking for inspiration.</p><p>So the challenge for the “Agile” Architect is how can we -</p><ul><li>Provide enough guidance to the Engineers to start build, without making them wait until we finalise the architecture.</li><li>Minimise any waste; yes a lot of incremental work are two-way decisions that can be reversed, but let’s not waste a sprint if we don’t need to.</li></ul><p><em>The usual approach to solve this is to complain that Product / Service Design etc have had months doing research and study and there is just not enough time to do a proper architecture. A different approach coming up.</em></p><h3>Problem 1 — Equating Agile Architecture with No Architecture</h3><p><em>Favouring the No Architecture Approach</em></p><h4>Technical Debt gets accumulated</h4><p>Actually, there is <strong>Bad</strong> technical debt and <strong>Not-So-Bad</strong> technical debt.</p><ul><li><strong>Bad</strong> technical debt is technical debt that we accumulate .. and we don’t know that we are creating it — until later.</li><li><strong>Not-So-Bad</strong> technical debt are short-cuts that we know about upfront and are still willing to pay the price because the “Value” is worth it.</li></ul><p>So the risk here is that we are creating Bad technical debt, and we don’t know it yet. Was the effort <strong>plus the new debt accumulated</strong> worth the Value we unlocked with this initiative?</p><h4>Can’t see the forest for the trees</h4><p>The Emerging Architecture / No Architecture approach lacks connection with a greater purpose. It can be difficult to see if this is moving us closer or further away from our medium and long-term goals for the system/portfolio/organisation.</p><h4>Reuse is not identified</h4><p>Refer to the Hypothesis above.</p><ul><li>H3: Engineers will not look to reuse assets if it is too hard or they are not told to.</li></ul><h3>Problem 2 — Thinking that Agile Architecture is just the same as what we used to do</h3><p><em>All Architecture is Intentional and sometimes Ivory Tower architecture</em></p><h4>Value opportunities are missed or diluted</h4><p>Every week we spend architecting the perfect solution, means a week longer to start realising value. The time we consume should be sympathetic to the value that is being unlocked and any expiry date on that potential value.</p><p>As an IT capability, we sometimes gather around and discuss how product can’t make up their minds and keep pivoting on direction. Actually what might be happening is that solutioning is taking too long and that the potential value has expired.</p><h4>Capacity is drained with reviews and decisioning</h4><p><em>… where no decision is needed</em></p><p>It’s not uncommon to have multiple layers of approval for a relatively minor architecture solution. Even if that solution is implementing a pattern that has been implemented many times before.</p><p>Time can be wasted in formal reviews and preparing for reviews, where we could perhaps put more trust in our senior engineers and a peer review process.</p><h3>Agile Architecture</h3><p>So bouncing from one sprint to the next and doing just enough design to keep the Engineers busy is not Agile Architecture and the old ways of pondering about a solution for months to produce all the “correct” architecture artefacts is not Agile Architecture. What can we say is Agile Architecture? What are the Steps?</p><h4>Step 1: The Architect Title and the Architect Role</h4><p><em>I’m An Architect so I do all the Architecture. Or this solution needs architecting.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*tEBqTk-cfAP3b3zYfYyaiQ.png" /><figcaption>Hi I’m from Architecture, I’m here to help</figcaption></figure><p>At the risk of putting some architects out of business. Not all architecture needs to be done by someone with the title of “Architect”. In fact, an Engineer in the Pod or Tribe may be much closer to the problem to be solved and the value that is being unlocked.</p><p>When creating a design for a new feature or enhancement, the person doing the architecture needs to consider -</p><ul><li>How do we usually solve these types of problems? Is there a Pattern or Guideline for this already? <strong>See Step 2</strong></li><li>Do I need help? Find an Architect or another Engineer to run your idea by.</li><li>Just like code reviews, get your solution peer-reviewed. <strong>See Step 3</strong></li></ul><h4>Step 2: Architecture Patterns &amp; Guidelines</h4><p><em>The Guardrails and Cheatsheets</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QhfIFS5ejf-cCYWf" /><figcaption>Photo by <a href="https://unsplash.com/@0ruofei0?utm_source=medium&amp;utm_medium=referral">Bournes senruoB</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>Extract from the TOGAF 9 Standard —</em></p><blockquote>Patterns offer the promise of helping the architect to identify combinations of Architecture and/or Solution Building Blocks (ABBs/SBBs) that have been proven to deliver effective solutions in the past, and may provide the basis for effective solutions in the future.</blockquote><p>Architecture patterns provide a systematic approach to solving common challenges. They not only expedite the solutioning process but also ensure that solutions adhere to best practices, promoting consistency and reliability across diverse projects.</p><p>Well-documented patterns solves the first challenge of reuse — How do we get Engineers (and other people doing architecture) to leverage the organisation’s knowledge.</p><p>Actually, can a lot of the detailed solutioning be distilled down to just a set of tick-a-boxes? For example -</p><p>☐ Does the solution use our documented OAuth pattern for Authentication</p><p>☐ Does the solution use the standard logging pattern</p><p>☐ Does the solution’s APIs conform to the API standard and are they published in the developer portal.</p><p>… you get the idea.</p><p><strong>How to Create Architecture Patterns</strong></p><ol><li>The best practice is extracting the architecture patterns out of the strategic projects within the organisation which leverages the depth and breadth of experiences gained during these significant initiatives. Many of the strategic projects include One-way decisions. We should be building patterns that consolidate our investment in these decisions.</li><li>Industry patterns are a great source of inspiration. The problem though is that there is more than one way (pattern) to do something. A process is needed to agree on the suitable patterns to use.</li><li>The most challenging way to produce patterns is a forensic analysis of what already exists in the organisation. This typically means multiple patterns have been used to solve the same type of problem. Work is needed to review the existing patterns and pick a winner for moving forward.</li></ol><h4>Step 3: Peer Reviews</h4><p><em>The Light Governance Approach</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DCVssL84iicy9HfU" /><figcaption>Photo by <a href="https://unsplash.com/@paulina_milde_jachowska?utm_source=medium&amp;utm_medium=referral">Paulina Milde-Jachowska</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the words of one of America’s greatest Politicians and B-grade actors Ronald Reagan <strong>“Trust but verify”</strong> (Actually he borrowed it from a Russian proverb).</p><p>We want to trust people doing architecture to get on and do architecture, with a minimum of red tape. Especially for those two-way / noncritical solutions that are providing incremental value for their teams.</p><ul><li>Our Engineers are clever people who should not be slowed down by too much bureaucracy.</li></ul><p><strong>The Solution for ensuring conformance to architecture is -</strong></p><ol><li>Train Engineers / Architects to recognise Architectural significant solutions. Solutions that are systemically important need to have some more oversight and review.</li><li>Use the helpline / phone a friend to get to the right solution. This is especially important if you are colouring outside the lines or traveling too close to the guardrails.</li><li>Reviews should be open; foster debate and take us to a better place. They should not be so scary that they are avoided at all costs.</li></ol><h3>Summary</h3><h4>Large programs of work and One-Way Decisions</h4><p>When putting together an architecture for a significant piece of work or a One-Way decision, it is important to be intentional. Architecture should be well defined and endorsed, after all, it will be around for some time.</p><p>To get the most out of these types of investments, we should aim to produce Architecture Patterns. Architecture Patterns will help to ensure that enhancements and features that build on top of the work delivered are consistent and maximise value.</p><h4>Agile Architecture for Everything Else</h4><p>So now that we have sorted out the large significant projects and architectures …</p><ol><li><strong>Good architecture is not just done by Architects.</strong> Given the right tools and support, we can have good repeatable architecture solutions from within the Pods / Tribes without bringing in external consultants (ie architects)</li><li><strong>Invest “architecture time” in Patterns rather than Solution Architectures. </strong>We don’t need to lock up capacity building, documenting, and approving solutions for something that we already know the answer to. An architecture pattern documented once can serve many project initiatives.</li><li><strong>Trust but verify</strong>. Architecture solutions can be peer-reviewed as well. Engineers and architects should not be afraid to raise an architectural concern.</li></ol><h4>Next — Agile Enterprise Architecture?</h4><p>Did not get a chance to discuss how Agile architecture can / needs to align with the organisation strategy. Topic for next part in the series.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=385071ae5d75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prospa-technology/emerging-vs-intentional-architecture-385071ae5d75">Emerging vs Intentional Architecture</a> was originally published in <a href="https://medium.com/prospa-technology">Technology @ Prospa</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecturally Significant Decisions]]></title>
            <link>https://medium.com/prospa-technology/architecturally-significant-decisions-68ac47687277?source=rss-8cd329cb306e------2</link>
            <guid isPermaLink="false">https://medium.com/p/68ac47687277</guid>
            <category><![CDATA[agile-architecture]]></category>
            <category><![CDATA[architecture-governance]]></category>
            <category><![CDATA[architecture-decisions]]></category>
            <dc:creator><![CDATA[Stephen Crockett]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 21:04:23 GMT</pubDate>
            <atom:updated>2023-10-02T22:00:02.850Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Part 1 of the Agile Architecture Series</em></strong></p><p>Engaging in architecture within a start-up or scale-up organisation offers a unique and exciting set of opportunities that distinguish it from traditional corporate environments.</p><p>It’s an environment where architects often find themselves navigating a dynamic landscape that demands adaptability and creativity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vh-RycuE_NL5Slcqgp7sBg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mrtnpro?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Martin</a> on <a href="https://unsplash.com/photos/LQiXb7dA4Dk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Scope and Diversity:</strong> Crucially, the scope and diversity of architectural challenges encountered across different domains can present architects with a uniquely rewarding yet equally demanding experience.</p><p>This diversity not only allows architects to explore a wide spectrum of problems but also challenges them to adapt and find innovative solutions, making their roles both intellectually stimulating and professionally enriching.</p><p><strong>Agility and Focus:</strong> Juggling Agility and Focus in such a vast scope can be tricky. But how do we decide what’s crucial?</p><p>Well, that’s where One-Way and Two-Way decisions come into play.</p><h3>One-Way and Two-Way Decisions</h3><p>As a kid, one of the classic hobbies I embraced was playing with model trains, and it was an endless source of fun and imagination.</p><p>One of the earliest and most significant “one-way” decisions I had to make was selecting the gauge of the model trains. It might seem like a small choice, but in the world of model trains, it’s the decision that sets the stage for everything else. The gauge determines the size and scale of the trains and tracks, dictating which models, accessories, and scenery would be compatible. It’s akin to choosing the foundation for your miniature railway universe.</p><p>This seemingly simple choice had a profound impact on the entire journey, as it guided subsequent decisions about track layouts, locomotives, carriages, and even the landscapes I would create. It’s amazing how a single decision in a childhood hobby can teach the importance of architecturally significant choices in the broader context of life and decision-making.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*R-4oCO28-v-4zJVhbvWKEw.jpeg" /><figcaption>Wikimedia Commons</figcaption></figure><p>I’m going to paraphrase a great visualisation from the <a href="https://www.opengroup.org/"><strong>The Open Group</strong></a></p><blockquote>Think about decisions as one-way or two-way doors [Think Like Amazon: Rossman 2019].</blockquote><blockquote>When you walk through a <strong>one- way door</strong>, if you do not like what you see on the other side, you cannot get back to the initial state. This type of decision, is difficult to reverse.</blockquote><blockquote>When you walk through a <strong>two-way door</strong>, if you do not like what you see on the other side, you can walk right back through the door and return to the previous state. This type of decision, is easy to reverse.</blockquote><h3>One-Way Decisions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*1xa6Cal7leN031a987fGiQ.jpeg" /></figure><p>One-way decisions are choices that significantly impact a project, system, or organisation and are challenging to reverse or modify once implemented. These decisions typically include large programs of work that have a profound and enduring impact on an organisation.</p><p>Examples of One-Way Decisions can include -</p><ul><li>Re-platforming your core system. This can be akin to modernising the heart of your organisation. This typically involves migrating from an existing infrastructure or architecture to a new one, often driven by the need for improved functionality, scalability, security, or compliance.</li><li>Changing your Technology Stack (or Parts of). Another example of a one-way decision with significant implications. This decision involves migrating from one set of programming languages, frameworks, or tools to another, often with the aim of improving efficiency, reducing costs, or addressing emerging market trends.</li></ul><p>So when it comes to Focus, it becomes critical to identify your one-way decisions, spend more time evaluating them, testing them and architecting them.</p><p>When you figure out the big, game-changing “One-Way” decisions, the other choices (should just) fall into place. Those Two-Way decisions should go hand-in-hand with and match up to the main direction that has been set.</p><h3>Two-Way Decisions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*tiLmefMZ-gpOJinMpx7o2w.jpeg" /></figure><p>Two-way decisions, on the other hand, are choices that offer flexibility and the possibility of revisiting the decision later in the project.</p><p>Key characteristics of two-way decisions include:</p><ol><li><strong>Flexibility: </strong>Two-way decisions allow the team to experiment and adjust based on evolving requirements or new information.</li><li><strong>Lower Impact:</strong> These decisions have a lower immediate impact on the overall architecture and can be revisited if necessary.</li><li><strong>Examples: </strong>Include adopting a specific library or building a feature for a mobile app. Also, many Two-Way decisions are usually made within the team or pod and don’t have a complex integration requirement.</li></ol><p>Actually, the Two-Way Decisions don’t always just fall into place. There can be a lot of wastage around doing things the wrong way, then needing to fix them up and trying again (<em>More on how to avoid this problem in Part 2 of this series</em>).</p><h3>Conclusion</h3><ul><li>Architecturally Significant Decisions hold the power to shape a project, system, or organisation. Recognising these decisions is crucial to channel time and resources effectively. Equally vital is avoiding unnecessary “governance” on less important decisions that can be easily undone.</li><li><strong>One-way decisions</strong> should have focus and oversight. These are the architecture decisions that are important to the organisation and set the stage for future work.</li><li><strong>Two-way decisions </strong>benefit from a lighter touch when it comes to governance and oversight. These choices empower teams to innovate and deliver swiftly, enabling flexibility and agility in response to evolving needs and opportunities.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68ac47687277" width="1" height="1" alt=""><hr><p><a href="https://medium.com/prospa-technology/architecturally-significant-decisions-68ac47687277">Architecturally Significant Decisions</a> was originally published in <a href="https://medium.com/prospa-technology">Technology @ Prospa</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>