<?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 Jörgen N. Karlsson on Medium]]></title>
        <description><![CDATA[Stories by Jörgen N. Karlsson on Medium]]></description>
        <link>https://medium.com/@jorgen.karlsson?source=rss-9fef7cba97bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UwsWNoWGPapWv2iZQL8sqg.jpeg</url>
            <title>Stories by Jörgen N. Karlsson on Medium</title>
            <link>https://medium.com/@jorgen.karlsson?source=rss-9fef7cba97bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:29:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jorgen.karlsson/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[When Forgetting Is the Feature]]></title>
            <link>https://medium.com/@jorgen.karlsson/when-forgetting-is-the-feature-119d0093ba8c?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/119d0093ba8c</guid>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 12:47:25 GMT</pubDate>
            <atom:updated>2026-06-02T12:47:25.189Z</atom:updated>
            <content:encoded><![CDATA[<p>A friend called me a while back with a simple question: what service would I recommend for sending a large, sensitive file?</p><p>I thought about it. Sprend came to mind, a Swedish service, solid and respectable. But my friend needed more than that. The file contained personal data that had no business sitting on someone’s server for a week. It needed to arrive, get read, and cease to exist on the internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WUkUYAkVhvlKQ-gzBCZRJw.png" /><figcaption>It exists for the handover. Not after. Photo: AI.</figcaption></figure><p>I couldn’t think of a good answer. So I did what engineers do when they can’t find the right tool: I built a workaround. I helped encrypt the file, spun up a virtual machine at some ISP, dropped the encrypted file on it, and served it through a simple Python command over a bare IP address with an obscure path. My friend emailed the link to the recipient. When they confirmed it arrived, I deleted the VM. The whole thing, server and file and link and trace, was gone.</p><p>It worked. And when my friend thanked me, they added: “You should build this properly.”</p><p>So I did. That conversation is how <a href="https://vitalsend.eu/">VitalSend</a> started.</p><p>But the reason I’m writing about it isn’t the product. It’s the design problem I had to think through to build it, because it turns out that building a tool which succeeds by disappearing is a genuinely unusual challenge.</p><h3>The assumption baked into every file transfer tool</h3><p>Most software is designed to remember. Files stay synced. History is searchable. Transfers are logged. You can pull up what you sent six months ago in two clicks.</p><p>For most situations, that assumption is correct.</p><p>But there is a category of file transfer where persistence is the problem, not the solution. Where the right outcome is that neither party can prove the transfer happened. Where a recoverable file is a liability, not a safety net.</p><p>WeTransfer exists because email has a size ceiling that never went away. It launched in 2009 to answer a single question: how do you get a large file to someone when email won’t carry it? It solves that well. But the assumptions baked into the solution, persistence and recovery and availability windows, were never really questioned, because for large-file transfer between collaborators they are fine.</p><p>Email has a different problem that file transfer tools have not addressed. It is not just that messages sit in someone’s inbox. Modern email infrastructure is layered with persistence most senders never think about: mail server backups, corporate archiving, compliance retention policies, phone sync, the recipient’s own backup service. A file sent by email does not live in one place. It exists in a dozen copies across infrastructure neither party controls, with retention periods neither party set.</p><p>File transfer services helped with the size ceiling. They didn’t help with the persistence problem. They just moved it.</p><h3>A concrete example</h3><p>A political party needs to share its member register with a regional office. The file contains names, addresses, and political affiliations, which is Article 9 sensitive data under GDPR, the category that carries the highest protection obligations. Every copy of that file that exists anywhere is a liability. The sending organisation needs to know the file reached its destination without lingering or leaving extra copies.</p><p>If they send it by email, it lands in an inbox, gets backed up to a mail server, possibly archived by the recipient’s employer, synced to a phone, copied into a folder. Six months later, nobody knows how many copies exist or where.</p><p>If they use WeTransfer, the file sits on its servers for seven days, downloadable by anyone with the link, and the recipient can forward that link. Expired transfers can be recovered too, with recovery switched on by default. This is not a flaw in WeTransfer. It is a deliberate feature. It just happens to be exactly the thing the sending party was trying to prevent.</p><p>The pattern repeats across the alternatives. SwissTransfer, the European option from Infomaniak, keeps files for thirty days by default: better jurisdiction, same structural problem. And Proton Drive comes up a lot when I talk to privacy-conscious people about this. It is end-to-end encrypted, Swiss-hosted, and genuinely serious about not reading your data, and I respect what they have built. But encryption and ephemerality are not the same thing. Proton cannot read your file, yet the file still exists for as long as you or the recipient keeps it. You can share it outside Proton with a standard link, and when you do, the encryption ends at the boundary. The file keeps living in your Drive until you delete it manually. There is no one-download-and-gone. Proton solves confidentiality. It does not solve persistence. Those are different problems.</p><p>Sending the register on a USB stick by physical post is not a joke. I have done it. There was a consulting engagement, a client who needed a sensitive document delivered without any digital trace. After ruling out every electronic option, we burned the file to a drive, mailed it, confirmed receipt, and destroyed both copies. It worked. It took four days and cost about forty euros in courier fees.</p><p>That should not be the answer in 2026.</p><h3>What it actually means to build for forgetting</h3><p>The interesting design challenge is not encryption, or access control, or file size limits. It is a more fundamental question: what does it mean to build a tool that succeeds by leaving no trace?</p><p>Every metric most software teams care about, like return visits and session length and re-downloads and history depth, points in the wrong direction. You are optimising for a transfer that happened once and cannot be reconstructed. The success state is a user who never comes back, because there is nothing to come back to.</p><p>That changes every decision.</p><p>Encryption has to happen before the file reaches the server, because if you hold the keys you can be compelled to use them. The recipient gets one download. Not one per device, not one with a grace period. One. After that, the link is dead. Not expired. Dead. There is no “recover this transfer” path, because recovery would mean the guarantee was never real.</p><p>You cannot store transfer history, because a log of what was sent to whom is itself sensitive. The billing system records a date and nothing else. No file references, no timestamps granular enough to reconstruct a sequence of events. The credit ledger and the transfer system are kept deliberately separate, so that even internal tooling cannot join them.</p><p>None of this is technically hard. What is hard is committing to it. Every feature request that sounds reasonable, like “can I resend if the recipient missed it?” or “can I see my past transfers?”, has to be refused, because accepting it means the guarantee is gone.</p><p>That refusal is the product.</p><h3>The asymmetry</h3><p>When you send a file through a standard service, both parties carry a copy of something: the file, the metadata, the link, the download history. If the handover ever becomes relevant in a dispute, there is a trail.</p><p>When the design goal is to make the handover unreconstructable, that asymmetry reverses. The sender cannot prove they sent it. The recipient cannot prove they received it. The service cannot show what was transferred. That is not an accident or a gap. It is the point.</p><p>This matters for a specific kind of professional. Lawyers who need a draft to exist only during negotiation. HR teams handling documents that shouldn’t survive the process. Security teams rotating credentials. Anyone whose job involves knowing that certain information travelled from A to B, and that it doesn’t exist anywhere else now.</p><p>WeTransfer and SwissTransfer are the right tools for most transfers. For the political party’s member register, for the HR file during an active investigation, for the pre-decision document that shouldn’t live in inboxes after the meeting, they are the wrong tools by design. Not because of any flaw, but because they were never built for the requirement that the file must not outlive the handover.</p><p>The VM at an ISP, with a Python server and a random IP, was the most honest solution I could find at the time. Then I built the real version.</p><p><em>Jörgen Karlsson is the founder of </em><a href="https://vitalsend.eu/"><em>VitalSend</em></a><em>, a file transfer service built in Sweden. One download. Then it’s gone.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=119d0093ba8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2025 — The Year Agile Dies?]]></title>
            <link>https://medium.com/@jorgen.karlsson/2025-the-year-agile-dies-3fdc5e1bf874?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fdc5e1bf874</guid>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Sat, 11 Jan 2025 06:45:20 GMT</pubDate>
            <atom:updated>2025-01-11T06:45:20.282Z</atom:updated>
            <content:encoded><![CDATA[<h3>2025 — The Year Agile Dies?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPJouol36GCo0sdrhMTZyg.png" /><figcaption>Agile stands att crossroeads: will it be pronounced dead, or is it evolving into something even more impactful?</figcaption></figure><p><strong>As we step into 2025, a provocative question looms large in the Agile community: Is Agile dying? Once celebrated as a revolutionary way of working, Agile now feels like a bloated elephant in the room-impossible to ignore, but too awkward to talk about. Job ads for ‘Agile’ are declining, major companies are phasing out roles like Agile Coach and Scrum Master, replacing them with Team and Enterprise Coaches. Are these just the same roles with a fresh coat of lipstick to avoid the stigma of Agile, or does the shift reflect deeper, systemic change?</strong> <strong>Is Agile’s decline inevitable, or is it simply shedding its old skin to evolve into something new? In this article, I’ll explore why some believe Agile is dying, what might lie beyond it, and challenge you to start rethinking the future-and your role in shaping it. One thing is certain: 2025 will be a defining year for the Agile movement-whether as its obituary or its rebirth.</strong></p><h3>Why Do People Say Agile Is Dying?</h3><p>Last year, I wrote about this very topic in my article, <a href="https://agiletto.se/agile-is-not-deadits-evolving-the-future-beyond-agile/">Agile Is Not Dead-It’s Evolving: The Future Beyond Agile</a>. At the time, I concluded that Agile wasn’t dying-it was evolving. But now, six months later, I’d like to revisit this question with fresh insights.</p><p>So, why do people say Agile is dying? Here are six main reasons:</p><h4>1. Framework Fatigue</h4><p>Many organizations have grown disillusioned with rigid implementations of frameworks like Scrum, SAFe, or LeSS. When frameworks are treated as inflexible processes, they often lead to bureaucracy, slowing teams down, and creating dissatisfaction among team members.</p><p>Let’s be honest-it’s easier to blame the framework than to address the real issue: leadership. Instead of saying, <em>“Let’s reinforce the mindset of our leaders,”</em> it’s simpler to say, <em>“Let’s stop doing Agile.”</em></p><h4>2. Misinterpretation of Agile Values</h4><p>Agile is often reduced to a checklist of processes and ceremonies, losing sight of its core values: collaboration, adaptability, and delivering value. Ironically, this is the exact opposite of what Agile was meant to be.</p><p>Take Scrum, for example. Its prescriptive nature can be helpful for new teams transitioning to Agile. But this structure is often misunderstood as a rigid process, leading teams to believe they must <em>“follow Scrum”</em> to be Agile. In reality, nothing could be further from the truth.</p><p>We should celebrate when teams want to move beyond Scrum-it often means they’ve matured enough to adapt their practices and recognize its limitations.</p><h4>3. The Rise of Alternatives</h4><p>I often hear, <em>“We don’t use Agile; we use DevOps/Lean/Kanban/Younameit.”</em> But here’s the truth: same values, different name. DevOps, Lean Startup, Teal Organizations, CI/CD-these movements aren’t rejecting Agile; they’re building on it.</p><p>Whether it’s DevOps, Lean, Kanban, or CI/CD, these approaches emphasize continuous value delivery, continuous learning, and removing impediments-the very principles Agile was founded on. These alternatives are often evolutions of Agile, not replacements.</p><h4>4. Failure to Deliver Business Outcomes</h4><p>Agile transformations don’t always deliver measurable business improvements, which frustrates executives. This failure often stems from cultural resistance rather than flaws in Agile itself.</p><p>Here’s the kicker: many organizations underestimate the cost of transformation-financially and in terms of temporary productivity dips. Agile isn’t a quick fix; it’s a long-term investment in cultural and operational change.</p><p>And let’s not forget Jeff Sutherland, co-creator of Scrum, who might have unintentionally set unrealistic expectations with the title of his book: <em>Scrum: The Art of Doing Twice the Work in Half the Time.</em> It’s simply not that easy.</p><h4>5. Buzzword Backlash</h4><p>Agile has been co-opted by consultants and organizations promising quick fixes. This “Agile Industrial Complex” often leads to superficial implementations, skepticism, and eventual disillusionment. Too many Agile practitioners have overpromised and underdelivered, prioritizing invoices over outcomes.</p><p>When Agile becomes more about certification fees ( <em>looking at you, SAFe</em>) and less about principles, it’s no wonder people start questioning its value.</p><h4>6. The Excuse Machine</h4><p>I’ve heard it all: <em>“Agile doesn’t work for hardware.”</em> <em>“We can’t use Agile in HR, marketing, or law because our lead times are too long.”</em></p><p>These excuses ignore the flexibility Agile provides. Agile doesn’t demand two-week sprints for every context-it demands a mindset of adaptability. The real issue often lies in misapplication or resistance to change, not Agile itself.</p><h3>Is Agile Really Dead-or Just Evolving?</h3><p>New data suggests Agile isn’t dying-it’s evolving. Engineering and R&amp;D teams are now the fastest-growing adopters of Agile, making up 48% of practitioners-a remarkable 16% increase since 2022. This growth demonstrates Agile’s ability to address challenges far beyond its traditional IT roots.</p><p>Here’s why Agile isn’t dead, but evolving:</p><h4>1. The Core Principles Are Timeless</h4><p>Responding to change, delivering value incrementally, and fostering collaboration are not just Agile principles-they’re universal drivers of organizational success. These principles will continue to shape how businesses operate, even if the terminology evolves.</p><h4>2. Agile Goes Beyond IT</h4><p>Business agility is expanding across organizations, reaching teams in HR, marketing, and beyond. For example, 86% of marketers plan to shift some or all of their teams to Agile methodologies, according to the Agile Marketing Report. This trend shows how Agile’s principles of adaptability, iterative delivery, and customer focus are reshaping industries outside of IT.</p><h4>3. Hybrid and Tailored Approaches</h4><p>Organizations are no longer treating Agile frameworks as rigid blueprints but are adapting them to fit their unique needs. Kanban, for instance, has seen notable success: 87% of adopters report that it’s more effective than their previous work management methods. These tailored approaches ensure Agile remains flexible, relevant, and impactful across diverse contexts.</p><h4>4. Focus on Outcomes Over Process</h4><p>The shift from process adherence to outcome-driven agility is redefining success. Nearly three in five Agile practitioners report greater satisfaction due to better alignment with business needs. This focus on delivering tangible value underscores Agile’s continued relevance when implemented thoughtfully.</p><h3>A Personal Reflection</h3><p>But here’s the challenge: if a vocal majority believes Agile is dying, does sticking with it make me a <em>bakåtsträvare</em> -what we Swedes call a stubborn traditionalist? Me? Someone who’s always been a forerunner, challenging the status quo and embracing change?</p><p>What I see is an evolution-not a decline. Agile may be shedding its buzzword status, but the principles and practices are far from obsolete. The real question isn’t whether Agile is dead-it’s how we adapt to ensure it continues to evolve in meaningful ways.</p><p>So, what’s my conclusion? Keep reading.</p><h3>2025: A Year of Reckoning or Renewal?</h3><p>If 2025 brings a reckoning for Agile, it will likely focus on these areas:</p><ul><li><strong>Cultural Transformation</strong>: Organizations that embrace Agile as a mindset, not just a method, will thrive. Culture is the foundation of meaningful change.</li><li><strong>Leadership Evolution</strong>: Leaders who adapt to Agile principles-empowering teams, fostering trust, and embracing change-will shape the future.</li><li><strong>Pragmatism Over Purism</strong>: The future of Agile lies in adaptability, integrating the best ideas from Lean, Design Thinking, DevOps, and beyond.</li></ul><p>If Agile is pronounced “dead” in 2025, it will be Agile as a buzzword that dies-not Agile as a set of principles for working smarter, faster, and more collaboratively. While the buzzword may fade, the movement and its values will endure.</p><h3>Conclusion: My Challenge to You</h3><p>2025 might not be the year Agile is pronounced dead-it might be the year it’s reborn. But for that to happen, it requires all of us to step up and take responsibility for its evolution.</p><p>Here’s my challenge to you:</p><ul><li><strong>Reflect on Your Practices</strong>: Are you clinging to rituals and frameworks, or are you truly living Agile’s core principles of adaptability, collaboration, and delivering real value?</li><li><strong>Be a Changemaker</strong>: What can you do to ensure Agile evolves meaningfully in your organization, team, or community?</li><li><strong>Lead the Change</strong>: Don’t wait for someone else to define what comes after Agile. Speak up, experiment, and share your successes-and failures-with others.</li></ul><p>The conversation needs to shift from <em>“Is Agile dead?”</em> to <em>“How is Agile evolving-and how are we shaping that evolution?”</em> The future is ours to create, and 2025 will be a defining year for what comes next.</p><p>What do you think? Is Agile facing an existential crisis, or is it shedding its old skin to adapt to new challenges? Let’s discuss! 🚀</p><h3>Get Weekly Insights</h3><p>Stay ahead in the agile world — join my newsletter for the latest insights and best practices. <a href="https://agiletto.se/subscribe">Subscribe here!</a></p><p><em>Originally published at </em><a href="https://agiletto.se/2025-the-year-agile-dies/"><em>https://agiletto.se</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fdc5e1bf874" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do We Really Need a Product Owner, or Can They Be Replaced by AI?]]></title>
            <link>https://medium.com/@jorgen.karlsson/do-we-really-need-a-product-owner-or-can-they-be-replaced-by-ai-8872edc0e099?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8872edc0e099</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Fri, 22 Nov 2024 09:45:20 GMT</pubDate>
            <atom:updated>2024-11-22T09:45:20.436Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Product Owner (PO), or “Value Maximizer” as I prefer to call them, has long been considered indispensable in Agile frameworks. They bridge the gap between customers, users, stakeholders, and the development team, ensuring the right features are built at the right time to deliver maximum value. But with the rapid advancements in AI-especially large language models (LLMs) like ChatGPT, Claude, and Bard-a bold and provocative question arises: <em>What if your Product Owner was an AI? With advancements in tools like ChatGPT, could we be on the brink of reshaping Agile roles forever?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ze7NjlfJ2z27GxKdctNh6w.png" /></figure><p><strong>In this article, I’ll explore this possibility, set up an experiment, and offer concrete tips on how LLMs could support-or even replace-certain PO tasks. But don’t worry, we’ll also consider whether the human touch is still essential-or if it’s time to rethink who truly owns the Product Owner role.</strong></p><p><strong>So, let’s do it!</strong></p><h3>The Role of a Product Owner: Critical but Challenging</h3><p>A Product Owner’s responsibilities include prioritizing the product backlog, communicating with stakeholders, translating business needs into actionable stories, and ensuring the team understands the product vision. The PO balances strategic goals with customer needs, all while keeping everyone aligned and maintaining focus.</p><p>The importance of this role is undeniable, but it’s also <strong>demanding</strong> -requiring deep product knowledge, business acumen, and crucially, human empathy. So how could AI possibly replace that?</p><h3>Can AI Really Take Over the PO Role?</h3><p>At first, it might seem absurd to suggest that AI-whether it’s ChatGPT, Claude, or Bard-could take over the complex, strategic role of a Product Owner. <strong>But let’s not dismiss it too quickly.</strong></p><p>LLMs are already being used to augment many roles, offering powerful assistance in tasks that previously required human oversight. Could the PO be next? Let’s break down the tasks that AI could potentially handle, provided it has access to key product information like the backlog, product vision, and roadmap.</p><h4>1. Backlog Refinement</h4><ul><li>AI can help organize, prioritize, and sort backlog items based on predefined criteria such as business value, dependencies, or user feedback.</li><li>It can suggest improvements to user stories or acceptance criteria based on past data or examples.</li><li>AI can even update the backlog after a workshop automatically.</li><li>LLMs can refine vague inputs into clearer user stories and feature descriptions, providing drafts that the team can then finalize.</li></ul><h4>2. Stakeholder Communication</h4><ul><li>AI might not replace strategic discussions with stakeholders, but it could generate summaries, answer routine questions, and even collect feedback-freeing up the PO for more complex conversations.</li><li>An AI “copilot” could respond to stakeholder queries in real-time while keeping a log of all interactions for future use.</li></ul><h4>3. Sprint Planning Assistance</h4><ul><li>AI can assist in breaking down features into stories, estimating workload, and highlighting risks or dependencies — providing support for planning.</li></ul><h4>4. Predicting Trends</h4><ul><li>AI can analyze vast amounts of market data and user behavior to predict trends or future needs, helping POs make data-driven decisions about product direction.</li></ul><h3>My Experiment: Letting AI Take Over Some PO Tasks</h3><p>To test this, I’m running an experiment where I create an AI-driven PO for a fictional product. The AI will handle part of the Product Owner’s responsibilities. Specifically, I’ll be using it for:</p><ul><li>Backlog refinement and prioritization</li><li>Breaking down features into stories</li><li>Drafting user stories from high-level business needs</li><li>Assisting with prioritization</li></ul><p>I’ll report back on how the AI performs. Here’s my hypothesis: <strong>The output will look impressive on the surface but will lack the nuanced understanding required for real product success.</strong> Will AI deliver? Or will the results be less than usable? Stay tuned-I’ll even share the tool so you can try it yourself!</p><h3>The Human Touch: Why We Still Need a Product Owner (For Now)</h3><p>Despite the impressive potential of AI, certain aspects of the Product Owner role simply can’t be automated-yet. Here’s why:</p><p><strong>1. Empathy and Context</strong></p><ul><li>A key part of the PO role is understanding the emotional landscape of the team and stakeholders, navigating conflicts, and maintaining team morale. AI might be powerful, but it cannot build trust or relationships.</li></ul><p><strong>2. Strategic Vision</strong></p><ul><li>AI can suggest priorities based on data, but a Product Owner shapes the <strong>vision</strong> for a product. This requires deep understanding of the business, the market, and the customer’s needs.</li></ul><p><strong>3. Adaptability in Ambiguity</strong></p><ul><li>A PO often operates in uncertainty, dealing with shifting priorities and unforeseen challenges. AI excels when patterns are clear, but humans excel at handling ambiguity and making quick, complex judgment calls.</li></ul><p><strong>4. Collaborative Leadership</strong></p><ul><li>Good Product Owners lead by fostering collaboration and encouraging team creativity. AI can crunch numbers, but it can’t inspire or guide a team in the same way.</li></ul><h3>Could the Team Share the PO Responsibility?</h3><p>One possibility is that AI could assist a team in sharing some of the PO’s responsibilities. AI could help prioritize, draft user stories, and generate summaries, while teams make the final decisions.</p><p>This requires a <strong>high level of team maturity</strong> and autonomy, but it raises an intriguing idea: could teams, supported by AI, take on more ownership and reduce reliance on a single PO?</p><h3>Conclusion: The PO Isn’t Going Anywhere-Yet</h3><p>While AI can support many Product Owner tasks, the role of the PO is still crucial to Agile success. AI can streamline workflows and handle routine tasks, but the strategic, empathetic, and leadership aspects of the role remain uniquely human.</p><p>However, experimenting with AI as a support tool could allow POs to focus on higher-level strategy, customer collaboration, and unlocking even more value. And who knows? <strong>Maybe in the future, AI will help teams share PO responsibilities</strong> and truly democratize product ownership.</p><p>So, do we still need Product Owners? <strong>Absolutely</strong> -but with the right tools, the role could evolve into something even more powerful.</p><p>Want more insights on Agile leadership, team dynamics, and the future of roles in Agile? Subscribe to my weekly newsletter for fresh articles and tips directly to your inbox. <a href="https://staging.agiletto.se/subscribe/">Sign up here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8872edc0e099" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mistake #3: Inability to Transform Organizational Culture — A Core Obstacle in Agile…]]></title>
            <link>https://medium.com/@jorgen.karlsson/mistake-3-inability-to-transform-organizational-culture-a-core-obstacle-in-agile-13341751f07d?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/13341751f07d</guid>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 11:24:46 GMT</pubDate>
            <atom:updated>2024-10-11T11:24:46.713Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mistake #3: Inability to Transform Organizational Culture — A Core Obstacle in Agile Transformations</h3><p><strong>In a mid-sized tech company, the CEO enthusiastically declared, “We’re going Agile!” Teams swiftly adopted new tools, rituals, and frameworks, and the board was pleased with the quick wins. But beneath the surface, things weren’t as smooth as they seemed. Leaders continued making top-down decisions, departments operated in silos, and productivity dropped-despite the shiny new Agile façade. Frustrated, the leadership began to question the value of Agile methodologies and searched for ways to “interface” Agile with their existing business processes.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCBa7eT5IT1QIMLUfYU1mw.png" /></figure><p><strong>This story is far from unique. Many organizations embark on Agile transformations without realizing that true success hinges on a deep cultural shift. Agile is not just a set of frameworks-it requires a fundamental change in how people think, act, and work together. This shift is what we often refer to as <em>organizational culture</em>.</strong> <strong>In this article, I’ll explore the critical role culture plays in Agile success, how the failure to transform culture derails Agile efforts, and practical steps for ensuring cultural alignment with Agile principles. So, let’s do it!</strong></p><h3>Forgetting the Culture</h3><p>When organizations begin an Agile transformation, they often prioritize processes, tools, and frameworks without addressing the critical underlying component-culture. Coaches are brought in, and teams adopt Scrum, Kanban, or even the full SAFe framework, yet something still feels off. The transformation appears promising at first, but soon, cracks begin to show.</p><p>Leadership continues to operate hierarchically, making decisions over the heads of teams, particularly when the stakes are high. Silos remain intact, and what emerges is <em>Zombie Agile</em> -a mechanical practice of Agile rituals layered on top of the old, deeply ingrained ways of working. Agile becomes just another process, rather than the transformative force it was meant to be.</p><h3>Signs and Symptoms</h3><p>The following symptoms might appear in an organization that have not transformed the organizational culture:</p><ul><li><strong>Superficial Agile Adoption</strong>: Teams go through the motions of daily standups, sprint planning, retrospectives, and other Agile ceremonies, but these meetings lack real engagement or value. Rituals are performed because they’re required, not because they enhance collaboration or workflow. Decision-making remains centralized, undermining true agility.</li><li><strong>Resistance from Leadership and Middle Management</strong>: Agile’s push for distributed decision-making often threatens traditional hierarchies. Leaders and middle management, accustomed to holding authority, may resist the shift and continue exerting control over teams.</li><li><strong>Siloed Departments</strong>: Despite the intention of cross-functional collaboration, departments continue operating in silos, focusing more on individual departmental goals than on collective, value-driven outcomes. Teams remain isolated, failing to share knowledge and work toward common objectives.</li><li><strong>Lip Service to Agile Values</strong>: The organization may frequently discuss Agile values like trust, transparency, adaptability, and collaboration, but these values remain largely theoretical. In practice, the organization falls back on old habits, prioritizing processes and authority over empowerment and flexibility.</li><li><strong>Focus on Processes Over People</strong>: Instead of following Agile’s mantra of “individuals and interactions over processes and tools,” the organization becomes rigid and process-driven. Little effort is made to foster a culture of trust, autonomy, or collaboration. Authority is emphasized, with rigid adherence to roles, rather than empowering teams to take ownership of their work.</li><li><strong>Lack of Adaptation</strong>: Teams continue to follow the same process sprint after sprint, even when it’s clear something isn’t working. They feel they have no authority to change their ways of working, so they simply go through the motions without adapting to feedback or improving.</li><li><strong>Metrics Over Outcomes</strong>: Teams become fixated on metrics like velocity or sprint deadlines, often losing sight of their ultimate goal-delivering value to customers. The focus shifts from meaningful outcomes to simply completing tasks, tracking progress for the sake of reporting rather than producing high-quality, valuable products.</li><li><strong>Command-and-Control Mindset</strong>: Despite the shift to Agile, management continues to operate in a command-and-control style. Managers dictate how work should be done, stifling creativity and initiative within teams. Process owners enforce rigid adherence to processes, preventing teams from adapting their approach.</li><li><strong>Superficial Ownership</strong>: Team members treat tasks and the “definition of done” as mere checklist items. There is little real ownership or accountability, and instead of working toward collective outcomes, individuals focus on completing their own tasks without concern for team success or improvement.</li><li><strong>Moving People to the Work</strong>: The Agile concept of placing everything in backlogs-moving work to the people-becomes flawed when people are constantly reassigned. Individuals may be working across multiple teams or projects, leaving little room for cohesion or team synergy.</li><li><strong>Teams in Name Only</strong>: Teams often don’t function as cohesive units. Instead, individuals continue to work on their own specialized tasks, only integrating their work toward the end of the sprint. In some cases, team members may not even be working on the same goals. The result is fragmented efforts, with little collaboration or shared responsibility.</li></ul><h3>Consequences of Not Transforming the Organization’s Culture</h3><h3>Short-Term Consequences</h3><p>In the early stages of an Agile transformation, things might seem promising despite missing out on the cultural transformation. Teams may deliver on short-term goals, adopting Agile ceremonies like sprint planning, standups, and retrospectives. Leaders may feel reassured by these quick wins, believing that progress is being made. But beneath the surface, cracks begin to appear. Agile practices become mechanical-teams go through the motions of ceremonies without fully embracing the values that should guide them.</p><p>This superficial adoption creates an illusion of success, but without the deep cultural transformation, the organization is merely <em>doing</em> Agile, not <em>being</em> Agile. As the weeks and months progress, these surface-level changes fail to create lasting improvements.</p><h3>Long-Term Consequences</h3><p>As time goes on, the failure to transform the underlying culture leads to far-reaching negative impacts. Teams and team members become disengaged and disillusioned, realizing that the promised autonomy, collaboration, and flexibility were never fully realized. Burnout becomes common as teams feel trapped in a system that demands Agile rituals but offers none of the empowerment or adaptability that should come with it.</p><p>Leaders, seeing that Agile isn’t delivering the expected results, begin to question its value. Without cultural change to support Agile practices, leaders may conclude that Agile itself is flawed, and decisions to abandon or drastically scale back the transformation become likely. The entire transformation stalls, leaving the organization stuck between two worlds-no longer fully committed to its old ways, but equally unable to move forward with Agile.</p><h3>Broader Implications</h3><p>Culturally, the organization remains entrenched in old paradigms-hierarchical, siloed, and resistant to change. This inertia prevents the organization from achieving true business agility, where teams can respond quickly to change and continuously deliver value. Instead, decision-making remains slow and centralized, stifling innovation and limiting the organization’s ability to compete in fast-moving markets.</p><p>Without addressing cultural transformation, the organization not only fails in its Agile journey but also risks falling behind competitors who have embraced a more adaptive, innovative mindset.</p><h3>Case Studies</h3><p><em>These case studies are based on real companies, but their names have been withheld to protect anonymity.</em></p><h4>The Packaging Solutions Company</h4><p>A packaging solutions company adopted Agile to accelerate project delivery and improve efficiency. They implemented the SAFe framework, hired Agile coaches, and set up Scrum teams and Agile Release Trains. However, leadership continued to manage in the same traditional, top-down, risk-averse style. Teams were given little room to make their own decisions, and communication silos persisted between business and IT, as well as within IT departments. To make matters worse, the company retained overarching waterfall processes, making it nearly impossible for teams to achieve true agility. As a result, teams became disengaged, deadlines were missed, product quality declined, and the transformation never gained momentum. Eventually, the company abandoned the Agile transformation altogether.</p><h4>The Software Company</h4><p>A software company in the entertainment industry understood from the start that cultural change was essential for a successful Agile transformation. Instead of jumping straight into a predefined framework, they first engaged leadership at all levels in cultural workshops focused on key Agile values: transparency, collaboration, and trust. They nurtured a learning culture, where mistakes were treated as opportunities for growth rather than failures. Rather than adopting a one-size-fits-all framework, they crafted their own, inspired by existing Agile practices but tailored to their specific needs. Over time, this cultural transformation allowed Agile practices to truly take root and thrive, leading to faster innovation, shorter time to market, improved product quality, more engaged teams, and sustained business growth.</p><h4>Analysis</h4><p>The packaging solutions company failed because they viewed Agile as a framework that could be applied without addressing their organizational culture. Leadership maintained their old habits, which undermined the autonomy and flexibility that Agile requires. In contrast, the software company succeeded by placing cultural transformation at the heart of their Agile adoption. By fostering leadership involvement, building trust, and creating a culture of continuous learning, they allowed Agile principles to drive real, lasting change.</p><h3>Why We Need to Embrace the Cultural Transformation</h3><p>Cultural transformation isn’t just a component of becoming Agile-it <em>is</em> the transformation. That’s why it’s called a “transformation,” not merely a change. Agile isn’t about tweaking processes or adopting new tools; it’s about reshaping the entire organization to embody Agile values from the ground up.</p><p>When the culture aligns with Agile principles, teams and individuals feel empowered, motivated, and engaged. They take ownership of their work, striving to innovate and produce real value that solves customer problems. Collaboration flows naturally, sparking creativity and driving continuous improvement. As a result, time to market decreases, and quality improves-because true agility requires high-quality work to respond quickly and effectively to change.</p><p>A culturally Agile organization becomes a place where people want to work. It fosters an environment of trust, autonomy, and purpose, leading to happier, more productive teams. And as a side effect, both productivity and profitability typically increase.</p><h3>Reflective Questions</h3><p>Based on this article, consider the following questions within your own environment and answer them thoughtfully for yourself:</p><ul><li><strong>Are your Agile practices deeply embedded in your culture, or are they merely rituals?</strong></li><li><strong>How does your current culture and processes support or hinder Agile values like collaboration and transparency?</strong></li><li><strong>What steps can leadership take to actively drive cultural transformation in your organization?</strong></li></ul><h4>Application to Practice</h4><p>Start by assessing where you currently stand. Conduct a cultural audit to evaluate how well your organizational values align with Agile values and principles. If necessary, engage leadership in cultural transformation workshops to build awareness, foster commitment, and lay the groundwork for meaningful and deliberate transformation.</p><h3>Conclusion</h3><p>Cultural transformation is the foundation of any successful Agile initiative. Without it, the transformation simply won’t happen. Agile practices will either fail outright or achieve only superficial success. By recognizing the need for deep cultural change and actively embedding Agile values into the fabric of the organization, you unlock the true potential of Agile and pave the way for sustained business agility. True agility or Zombie Agile-which path will your organization take?</p><h3>Additional Resources</h3><ul><li><em>Leading Change</em> by John Kotter</li><li><em>Organizational Culture and Leadership</em> by Edgar Schein</li></ul><p><strong>This article is the third in </strong><a href="https://agiletto.se/tag/Agile%20Transformation%20Failures/"><strong>a series of articles </strong></a><strong>about common mistakes in Agile transformations. Subscribe to my newsletter to stay updated and continue your journey toward Agile mastery!</strong></p><p><a href="https://agiletto.se/tag/Agile%20Transformation%20Failures/">All articles including future articles</a></p><p><em>Originally published at </em><a href="https://agiletto.se/mistake-3-inability-to-transform-organizational-culture-a-core-obstacle-in-agile-transformations/"><em>https://agiletto.se</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13341751f07d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Agile Teams: How Business Agility Future-Proofs Your Organization]]></title>
            <link>https://medium.com/@jorgen.karlsson/beyond-agile-teams-how-business-agility-future-proofs-your-organization-26c5823decc6?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/26c5823decc6</guid>
            <category><![CDATA[business-agility]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 13:11:49 GMT</pubDate>
            <atom:updated>2024-10-07T13:11:49.757Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In one organization I worked with, the goal of the transformation suddenly shifted to “We must start 100 agile teams.”</strong></p><p><strong>My response was blunt: “If we start 100 agile teams, we’ll get 100 agile teams. But will they work toward the same goal? Will the organization itself become agile? Will the processes surrounding these teams change on their own? What will be the outcome when we set a goal based on a vanity metric like the number of teams?”</strong></p><p><strong>This well-intentioned but misguided approach highlights a critical truth about agility-it’s not something that can be imposed or implemented in isolation. Agility isn’t a tool or a checklist for teams; it’s a mindset and a cultural shift for the entire organization. It demands commitment from leadership, engagement from teams, and an organizational willingness to embrace continuous learning, feedback, and adaptation-across the entire company.</strong></p><p><strong>The real question is no longer whether organizations need agility-they do. Those who think they don’t will soon be relics of the past. The agile era isn’t over; in fact, it’s the new business standard. But agility isn’t just about starting agile teams or “doing agile.” It’s about recognizing two interrelated but distinct aspects of agility: Team Agility and Business Agility. While agile teams are the engines that deliver value quickly and iteratively, Business Agility ensures that the entire organization-from leadership to frontline teams-can adapt to the fast-changing business landscape and truly be agile.</strong></p><p><strong>In this article, we’ll explore how both Team Agility and Business Agility are critical for success. Cultivating one without the other is a dangerous gamble, leaving your organization vulnerable in today’s volatile, unpredictable world. So, let’s do it!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XoljiaJQA74dmKTb8KILyw.jpeg" /></figure><h3>Defining Team Agility and Business Agility</h3><p>Let’s start by defining the two types of agility:</p><p><strong>Team Agility</strong> is a team’s ability to <strong>rapidly adapt</strong> to changing demands, customer feedback, and internal challenges. Agile teams focus on delivering value iteratively, learning continuously, and constantly improving their processes. They operate in short cycles, frequently inspect and adapt their work, and prioritize <strong>collaboration</strong>, <strong>transparency</strong>, and <strong>efficiency</strong>. <strong>Team Agility</strong> ensures that teams can respond quickly to evolving priorities while maintaining high levels of engagement and productivity.</p><p><strong>Business Agility</strong>, on the other hand, is an organization’s ability to respond quickly and effectively to changes in the market, customer needs, emerging technologies, and economic or political disruptions. It requires aligning strategy, operations, and culture to ensure long-term success in a volatile world. A truly <strong>business agile</strong> organization delivers in short cycles, adapts continuously, and seizes every opportunity to learn and evolve-ultimately becoming a <strong>learning organization</strong>.</p><h3>Connecting the Agile Manifesto to Team and Business Agility</h3><p>The <strong>Agile Manifesto</strong> outlines four core values- <strong>Individuals and interactions over processes and tools</strong>, <strong>Working systems over comprehensive documentation</strong>, <strong>Customer collaboration over contract negotiation</strong>, and <strong>Responding to change over following a plan</strong>. These values are essential for both <strong>Team Agility</strong> and <strong>Business Agility</strong>, but they manifest differently depending on the scope. Note that I’ve deliberately substituted <em>software</em> with <em>systems</em>. The agile principles apply universally-not just to software, but to any form of value delivery, whether it’s hardware, integrated solutions, or services.</p><p>In the context of <strong>Team Agility</strong> and <strong>Business Agility</strong>, these values take on different dimensions. Agile teams deliver value iteratively, but the surrounding organization must adapt to <strong>support and enable</strong> them. The broader organization’s main role is to <strong>empower these teams</strong> to deliver value. For an organization to be truly agile, it must scale these principles across every function-creating a dynamic, learning organization that can respond to external changes in the business environment. This means extending agility beyond teams, ensuring the <strong>entire organization</strong> is structured and aligned to support the delivery of value.</p><p>This is the core of <strong>Business Agility</strong>:</p><ul><li><strong>Business Agility</strong> is an organization’s ability to rapidly adapt to market shifts, emerging technologies, evolving customer needs, and disruptions-while maintaining its core values and strategic direction.</li><li><strong>Business Agility</strong> is holistic, encompassing strategy, operations, culture, development, and leadership alignment throughout the organization, including partners such as customers and suppliers.</li><li><strong>Business Agility</strong> supports teams in being agile, removing organizational impediments-the wet blanket stifling their ability to innovate and adapt.</li></ul><h3>Why Business Agility Is Essential</h3><p>Organizations that can <strong>anticipate and adapt</strong> to change will thrive. Those that can’t will fall behind-fast. The speed of technological advancement, shifting customer expectations, and fierce competition demand more than operational efficiency. Organizations need to be <strong>strategically agile</strong>.</p><p>Business Agility allows organizations to:</p><ul><li><strong>Respond to Market Disruptions</strong>: Agile businesses don’t just react; they pivot when necessary, staying ahead of competitors and market shifts.</li><li><strong>Stay Aligned with Customer Needs</strong>: In a customer-driven world, staying close to evolving customer needs is crucial. Business Agility ensures that customer feedback isn’t just heard but is <strong>strategically embedded</strong> into decision-making processes.</li><li><strong>Foster a Culture of Innovation</strong>: Agile organizations experiment, take risks, and <strong>fail fast</strong> -creating an environment where innovation thrives and employees are empowered to improve continuously.</li><li><strong>Align Teams and Strategy</strong>: Even the most agile teams can’t contribute to long-term success if they’re not aligned with the organization’s broader strategy. Business Agility ensures that teams work toward <strong>shared goals</strong> that advance the organization’s objectives.</li><li><strong>Become a Workplace Where People Thrive</strong>: Business Agility helps create an environment where employees can grow, innovate, and feel empowered-a place where people <strong>become awesome</strong>.</li></ul><h3>Real-World Examples of Business Agility</h3><p>The global pandemic was a make-or-break moment for many organizations. <strong>Zoom</strong> is a prime example of how agility turned crisis into opportunity. Already a leader in video conferencing, Zoom rapidly scaled its infrastructure to handle the massive surge in users during the pandemic. They didn’t stop there-Zoom expanded services for education and remote work and introduced enhanced security features in response to “Zoombombing.” This ability to <strong>adapt and scale</strong> while maintaining service quality is the essence of <strong>Business Agility</strong>.</p><p>Another strong example is <strong>Revolut</strong>, a fintech company that rapidly launched new financial services like cryptocurrency trading and stock options by delivering MVPs, gathering feedback, and iterating based on real-world use. This approach allowed Revolut to <strong>quickly diversify</strong> its offerings and stay relevant in a fast-evolving market. Revolut’s ability to adjust based on customer feedback highlights how Business Agility fosters innovation and maintains a competitive edge.</p><h3>What Business Agility Is Not</h3><p>There are many misconceptions about Business Agility that need to be cleared up:</p><ul><li><strong>Not Just Team Agility</strong>: Having 100 agile teams doesn’t mean your organization is agile. Without alignment, those 100 teams could be moving in 100 different directions and struggling with cooperation and dependencies. Business Agility ensures cohesive, organization-wide alignment and cooperation.</li><li><strong>Not Limited to IT</strong>: While agility may have started in software development, <strong>Business Agility</strong> applies across all functions-from marketing and finance to operations and leadership. It’s about creating an organization that adapts as a whole.</li><li><strong>Not an Excuse to Avoid Strategy</strong>: Agility doesn’t mean abandoning strategy. It requires a strong, well-communicated vision and clear goals, but with the flexibility to adapt when necessary-based on measurable facts from real-world experience.</li></ul><h3>Final Thoughts: The Synergy Between Team Agility and Business Agility</h3><p>In a world of accelerating change, no organization-big or small-can rely solely on <strong>Team Agility</strong> or <strong>Business Agility</strong>. These are not competing concepts, but complementary pillars of a future-ready organization. <strong>Team Agility</strong> drives the day-to-day delivery of value, while <strong>Business Agility</strong> ensures that the organization’s strategy and processes are aligned to support that delivery.</p><p>Without <strong>Business Agility</strong>, agile teams risk being smothered by a rigid, outdated organization that acts like a <strong>wet blanket</strong>, stifling their ability to innovate and adapt.</p><p>The question is no longer “Do we need agility?” It’s “How do we cultivate both <strong>Team Agility</strong> and <strong>Business Agility</strong> to thrive in a world of constant, unpredictable change?”</p><p>It’s not enough to just launch agile teams or implement an agile framework in one department or within IT alone. What’s needed is a shift in <strong>mindset</strong>, <strong>values</strong>, and <strong>culture</strong> across the entire organization, regardless of size. Only then can organizations truly harness the power of agility and position themselves to thrive in an increasingly complex and fast-paced world.</p><p><em>Originally published at </em><a href="https://agiletto.se/beyond-agile-teams-how-business-agility-future-proofs-your-organization/"><em>https://agiletto.se</em></a><em>.</em></p><p>Want to have insights every week? Subscribe to my weekly newsletter: <a href="https://agiletto.se/subscribe">https://agiletto.se/subscribe</a></p><p><a href="https://agiletto.se/subscribe">Expert Articles from Agiletto AB | Insights on Agile, Technology, and Leadership | Agiletto AB</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26c5823decc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Is Not Dead-It’s Evolving: The Future Beyond Agile]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jorgen.karlsson/agile-is-not-dead-its-evolving-the-future-beyond-agile-3db17acd0adf?source=rss-9fef7cba97bc------2"><img src="https://cdn-images-1.medium.com/max/2600/1*xRQITETljuTaej6DDt1Ktg.jpeg" width="3840"></a></p><p class="medium-feed-snippet">The question of whether Agile is dead continues to ignite debate. Some critics point to studies claiming a 268% higher failure rate for&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jorgen.karlsson/agile-is-not-dead-its-evolving-the-future-beyond-agile-3db17acd0adf?source=rss-9fef7cba97bc------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jorgen.karlsson/agile-is-not-dead-its-evolving-the-future-beyond-agile-3db17acd0adf?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/3db17acd0adf</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 14:48:15 GMT</pubDate>
            <atom:updated>2024-10-01T14:48:15.626Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Mistake #2: Alienated Leadership — The Silent Killer of Agile Transformations]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jorgen.karlsson/mistake-2-alienated-leadership-the-silent-killer-of-agile-transformations-308276ddf691?source=rss-9fef7cba97bc------2"><img src="https://cdn-images-1.medium.com/max/1920/1*LjgynY1uyFdfRAw66TTbdg.png" width="1920"></a></p><p class="medium-feed-snippet">Imagine two worlds within the same organization. In one, leaders actively champion Agile transformation, embodying its principles&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jorgen.karlsson/mistake-2-alienated-leadership-the-silent-killer-of-agile-transformations-308276ddf691?source=rss-9fef7cba97bc------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jorgen.karlsson/mistake-2-alienated-leadership-the-silent-killer-of-agile-transformations-308276ddf691?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/308276ddf691</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[transformation]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 06:57:46 GMT</pubDate>
            <atom:updated>2024-09-03T06:57:46.736Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Five Things Great Leaders Ask Themselves. Daily.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jorgen.karlsson/five-things-great-leaders-ask-themselves-daily-a9acb3e76710?source=rss-9fef7cba97bc------2"><img src="https://cdn-images-1.medium.com/max/2600/1*MXcP_bPcWW4wgrp-szH3tQ.jpeg" width="4834"></a></p><p class="medium-feed-snippet">Leadership isn&#x2019;t just about guiding a team or setting a vision. It&#x2019;s about constantly challenging your assumptions and asking yourself: Am&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jorgen.karlsson/five-things-great-leaders-ask-themselves-daily-a9acb3e76710?source=rss-9fef7cba97bc------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jorgen.karlsson/five-things-great-leaders-ask-themselves-daily-a9acb3e76710?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9acb3e76710</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[self-leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Tue, 27 Aug 2024 06:18:12 GMT</pubDate>
            <atom:updated>2024-08-27T06:18:12.678Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What to Do When Your Team Says They Do Not Need a Daily Standup]]></title>
            <link>https://medium.com/@jorgen.karlsson/what-to-do-when-your-team-says-they-do-not-need-a-daily-standup-dbf804e082b2?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbf804e082b2</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Tue, 20 Aug 2024 00:00:40 GMT</pubDate>
            <atom:updated>2024-08-20T15:34:28.731Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>“Why are we even having these meetings?” Paula asked, addressing the elephant in the room. Some team members stared down at the floor, shifting uncomfortably. John, usually the most vocal in the group and a strong advocate for processes, seemed lost for words. He looked at me, clearly frustrated. “Do something,” he said. “We need to have daily stand-up meetings because…” He hesitated, then added, “It says so in the Scrum Guide!”</strong> <strong>This was, as any coach would say, a critical moment. As a Scrum Master, I knew I had to navigate this situation carefully. I could either lose the team’s trust or help them overcome this hurdle and take a crucial step forward in their Agile journey, advancing through the Wheelan stages of team development. But if I handled this poorly, the team might stagnate or even regress. These thoughts flashed through my mind, and I felt a wave of dizziness. This was a defining moment-not just for me as a Scrum Master, but for the team as a whole.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KHyl3Oxzmba2yHfo" /></figure><p><strong>The scenario above is fictitious, yet it mirrors countless real-life situations where teams push back against their Scrum Master on specific practices-often targeting the Daily Scrum or Daily Stand-up. This 15-minute meeting, designed for planning the day and synchronizing activities, frequently becomes the scapegoat for all Agile frustrations. It can also be a key indicator of a team’s Agile maturity. In this article, I’ll share strategies to address this challenge. If you’re ready to find solutions, keep reading! So, let’s do it!</strong></p><h3>The Stand-Up</h3><p>The daily stand-up is a cornerstone of Agile practices, intended to foster alignment, communication, and rapid problem-solving within teams. But what should you do when your team claims they no longer need daily stand-ups? This is a common scenario that many Scrum Masters and Agile coaches encounter, and how you respond can significantly impact your team’s effectiveness and cohesion.</p><p>If there’s one meeting you should strive to keep and evolve, regardless of whether you’re using Scrum, Kanban, or any other Agile method or framework, it’s a daily collaboration meeting, whether you call it a stand-up or something else.</p><h3>Possible Reasons for Rejection</h3><p>As I wrote in my article about the <a href="https://agiletto.se/blog/9-daily-stand-up-myths-busted-transform-your-agile-meetings">9 Daily Stand-Up Myths Busted</a>, there are several misconceptions about this crucial meeting that might hinder the team. The list of myths in that article, along with the do’s and don’ts, might give you clues about possible reasons for rejection. However, as a Scrum Master, your role isn’t to judge the team but to coach them into improving their daily stand-up meeting. It’s important to understand the team’s dynamics and maturity level.</p><h3>Team Maturity</h3><p>Understanding the team’s maturity is key. A group of individuals merely working on their own tasks isn’t really functioning as a team. In such cases, the solution might be to foster more collaboration. Techniques like pair programming or limiting the Work in Progress (WIP) can encourage team members to work together more closely. Conversely, if the team is highly mature and well on its way to becoming a high-performing unit, the meeting might have lost its effectiveness or become a status report rather than a collaborative, problem-solving session. In such cases, consider changing the format or even temporarily removing the Scrum Master and/or the Product Owner from the meeting.</p><p>For example, I once visited a team that didn’t discuss issues with each other, instead turning to the Scrum Master for direction. To encourage more collaboration, I suggested, in a coaching session, that the Scrum Master start the meeting and then step aside, pretending to take a phone call or something. Standing by with a silent phone, the Scrum Master listened as the team began to discuss, plan, and solve problems together.</p><h3>Understanding the Root Cause</h3><p>As a Scrum Master, it’s crucial to facilitate the team in solving this problem themselves. This can be done in a separate meeting or, even better, at the next planned retrospective.</p><h3>Listen to the Team</h3><p>Begin by listening to the team. Conduct an exercise or simply ask them to write down their thoughts on sticky notes to get the conversation started. The prompt could be, “What are the problems with our daily stand-up meeting?”</p><p>But don’t linger too long in the problem space, because what you focus on is what grows. Instead, swiftly transition to finding solutions.</p><h3>Create a Vision and a Purpose</h3><p>One common issue is that the team may not have a clear purpose for the meeting. Even if they do, it might be time to redefine or reiterate that purpose. Ask the team why they need a stand-up meeting, or why it is part of all Agile methodologies. What is its purpose? What is the outcome of a good meeting?</p><p>Once a shared purpose is established, work on creating a vision. Ask the team to imagine the ideal stand-up meeting. What would happen? How would they feel afterward? A useful technique here is “The Worst Meeting Ever.” Have the team imagine the worst possible meeting and describe it. Then, flip those statements to define what the best possible meeting would look like.</p><h3>Take the Next Step: Experiment</h3><p>Ask the team, “What is our first step toward achieving this vision? What can we do as early as tomorrow?” The experiment could involve setting ground rules for the meeting, reducing the Scrum Master’s role, or trying a new agenda or meeting time. Just remember that it is the team that shall define the experiment.</p><p>But don’t stop there. Have the team define the expected outcome of their next step. What will happen? How will they know it has happened? Can it be measured?</p><p>This approach treats changes as experiments. The team formulates a hypothesis (e.g., “We think the meetings will be better if we…”) and an expected outcome (“We will feel more engaged when…”). Like any experiment, it must be evaluated and adjusted as needed. Use the next retrospective or sooner to assess whether the team is on the right track. This is the basis of any empirical way of working, like Agile.</p><h3>Conclusion</h3><p>When your team pushes back against the daily stand-up, responding with thoughtfulness and adaptability is essential. The daily collaboration meeting, whether you call it a stand-up or something else, plays a crucial role in Agile success. However, it’s not just about keeping the meeting-it’s about ensuring it serves its true purpose of fostering alignment, communication, and collaboration.</p><h3>What to Do When Your Team Says They Don’t Need a Daily Standup</h3><ul><li><strong>Listen and Understand</strong><br>Begin by genuinely listening to the team’s concerns. Understand why they feel the daily stand-up is unnecessary. Is it because the meeting has lost its purpose, become a status update, or feels like a redundant routine? Getting to the root of their concerns is the first step in addressing the issue.</li><li><strong>Reframe the Purpose</strong><br>Often, the issue isn’t the stand-up itself but how it’s conducted. If it has become a rigid ritual, consider shifting the focus to problem-solving, planning, and forward-looking discussions. Refer back to the insights from the <a href="https://agiletto.se/blog/9-daily-stand-up-myths-busted-transform-your-agile-meetings">9 Daily Stand-Up Myths Busted</a> article for ways to refresh and refocus the meeting.</li><li><strong>Envision a Perfect Meeting</strong><br>Work with the team to create a vision for an ideal stand-up meeting. Encourage them to include not just logistical details but also how they want the meeting to feel. Questions like “How will it feel when we have the perfect stand-up?” can help surface important soft factors that contribute to a successful meeting.</li><li><strong>Experiment and Adapt</strong><br> Be open to experimenting with different formats and improvements if the traditional stand-up isn’t working. Could the meeting be held at a different time, or with a new structure? The key is to maintain regular communication and alignment within the team. Continuously evaluate, adjust, and adapt all changes.</li><li><strong>Encourage Team Ownership</strong><br>Empower the team to take ownership of the stand-up. The meeting should not feel like an obligation imposed by the Scrum Master or Product Owner but rather a tool the team values for staying aligned and addressing challenges together. When the team takes ownership, the meeting becomes more meaningful and effective.</li></ul><h3>The Essential Takeaway</h3><p>The team’s Agile maturity and development stage are often reflected in their approach to stand-up meetings. If they see and use stand-up meetings to enhance collaboration, identify and solve problems, and align their efforts toward their common goal, they are likely well along the path of Agile maturity. On the other hand, if they oppose the daily stand-up, they might be resisting Agile practices altogether, seeing the stand-up as just another process step rather than a vital part of team collaboration.</p><p>The core message of this article is simple: while the format and frequency of daily stand-ups can and should evolve with the team’s maturity, the need for regular, structured collaboration remains essential. By listening to your team, adapting the stand-up format, and reinforcing its purpose, you can ensure this practice continues to add value and drive your team’s success.</p><p>Ultimately, the daily stand-up-or whatever form your team’s daily collaboration takes-should be a time for alignment, problem-solving, and collective planning. It’s not about rigidly following a process but about fostering the communication and collaboration that are vital to any Agile team’s success. Keep this principle at the heart of your Agile practices, and you’ll help your team move forward with confidence and clarity.</p><p>What are your thoughts?</p><p><em>Originally published at </em><a href="https://agiletto.se/blog/what-to-do-when-your-team-says-they-do-not-need-a-daily-standup"><em>https://agiletto.se</em></a><em> on August 20, 2024.</em></p><ul><li><a href="https://medium.com/@jorgen.karlsson/9-daily-stand-up-myths-busted-transform-your-agile-meetings-1903131b7833">9 Daily Stand-Up Myths Busted: Transform Your Agile Meetings</a></li><li><a href="https://agiletto.se/subscribe">Expert Articles from Agiletto AB | Insights on Agile, Technology, and Leadership | Agiletto AB</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbf804e082b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mistake #1: No Vision, No Victory — The Root Cause of Agile Transformation Failure]]></title>
            <link>https://medium.com/@jorgen.karlsson/mistake-1-no-vision-no-victory-the-root-cause-of-agile-transformation-failure-d2a5877a0764?source=rss-9fef7cba97bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2a5877a0764</guid>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jörgen N. Karlsson]]></dc:creator>
            <pubDate>Mon, 12 Aug 2024 00:00:44 GMT</pubDate>
            <atom:updated>2024-08-12T15:45:32.663Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mistake #1: No Vision, No Victory — The Root Cause of Agile Transformation Failure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mxmFtW9DNG70fI7x" /></figure><p><strong><em>In the bustling corridors of an unnamed company within the automotive industry, the mood had shifted from vibrant innovation to palpable uncertainty. Their Agile transformation, focused on SAFe and initiated with much fanfare, was floundering. Why? A deep dive revealed a startling absence: a clear, compelling vision for the transformation. The purpose was also unknown. They did not know where they were heading, nor did they understand why they needed to change. Consequently, lacking a defined destination and reason, the transformation was eventually abandoned in favor of another large change initiative — a reflection of a common pattern where organizations leap from one change to another without a foundational vision.</em></strong> <strong><em>This story isn’t unique. Similar patterns are observed across various sectors, where organizations embark on Agile journeys equipped with tools and methodologies yet falter at a fundamental hurdle — the absence of a unifying vision and purpose. This article discusses why a clear vision is the linchpin in Agile transformations. Drawing upon Simon Sinek’s insightful ‘Start With Why,’ and integrating principles from John Kotter’s 8-Step Change Model, we’ll explore the transformative power of a well-articulated vision. It’s not just about adopting Agile practices; it’s about rallying every team member around a shared purpose, steering the organizational ship through the tumultuous seas of change.</em></strong></p><p><strong><em>Expect to navigate through this article the common pitfalls associated with vision in Agile transformations, armed with real-life examples, strategies, and reflective exercises. Our goal is to equip you with the insights to craft a vision that resonates, inspires, and propels your Agile journey forward. So let’s do it!</em></strong></p><h3>Consequences</h3><p>As with any mistake in agile transformation, the consequences might be the first indication that something is wrong. The consequences of lacking a clear vision and purpose in a transformation might include:</p><p><strong>Lack of Motivation and Engagement:</strong> Without a clear vision and purpose, team members may feel unmotivated and disengaged. They struggle to understand the reason behind their work and how it contributes to larger transformative goals, leading to reduced enthusiasm and productivity, not just in the change itself but also in value delivery.</p><p><strong>Confusion and Misalignment:</strong> Vision and purpose provide direction and clarity. Without them, teams often experience confusion about priorities and misalignment in their goals. This can lead to duplicated efforts, conflicting objectives, and inefficiencies in workflows.</p><p><strong>Stagnation and Resistance to Change:</strong> Agile transformations thrive on continuous improvement and adaptation. A lack of vision and purpose can result in stagnation, where teams stick to old, or even updated, habits and resist new methods or practices. This resistance can severely hinder the agile transformation process when teams and individuals question the change, not understanding what’s in it for them.</p><p><strong>Diminished Creativity and Innovation:</strong> Vision and purpose inspire creativity and innovation by providing a future-oriented focus. When these are missing, teams might become overly focused on day-to-day tasks and fail to explore new ideas or solutions, limiting their potential for innovative solutions to transformation problems. Teams may struggle to set clear, achievable change objectives, leading to a cycle of missed targets and unmet expectations.</p><p><strong>Poor Decision-Making:</strong> A clear vision and purpose help in prioritizing tasks and making strategic decisions. In their absence, decision-making can become reactive and short-sighted, leading to suboptimal outcomes and a lack of strategic direction. The absence of a clear vision and purpose can also create fear of decision-making, as leaders and individuals might fear taking steps without knowing if they align with the right direction.</p><p><strong>Perceived Need for Detailed Processes:</strong> A lack of vision may lead leaders and other individuals to demand detailed instructions, such as role descriptions or process guidelines. This stems from the uncertainty of not knowing where to go, leading to a focus on how to proceed instead. This is directly counterproductive to the agile goals the organization aims to achieve.</p><p><strong>Erosion of Trust and Morale:</strong> Teams need a vision and purpose to feel that their efforts are meaningful and valued. Without them, trust in leadership can erode, and morale can decline, as team members feel their work lacks purpose and recognition.</p><h3>The need for a vision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5mpXZLpWJ4icxg14Je10OQ.jpeg" /><figcaption>Image: AI.</figcaption></figure><p>As the Cheshire Cat wisely tells Alice in Lewis Carroll’s <em>Alice in Wonderland</em>:</p><p>“If you don’t know where you’re going, any road will get you there.”</p><p>This metaphor aptly illustrates the necessity of a clear vision in Agile transformations. Without knowing the desired destination, teams can easily veer off course, making random decisions that lead nowhere meaningful, since any road will get you there.</p><p>Agile transformation, a journey as promising as it is challenging, must begin with a clear vision and purpose. One of the most common pitfalls in this journey is a lack of understanding or clarity regarding the ‘why’ behind the transformation. In my experience in the field, I have encountered at least four distinct yet common traps or faults in this area:</p><p>1. Vision Not Known</p><p>2. Vision Not Aligned</p><p>3. Vision Not Enough Communicated</p><p>4. Vision not Clear, Providing Priorities and Directions</p><p>But before explaining these mistakes, it’s crucial to understand why we need a vision for the transformation in the first place.</p><h4>Vision and Purpose</h4><p>In my experience, both vision and purpose are essential for a successful transformation. The vision sets the destination, while the purpose provides the motivation and rationale for embarking on the journey. Ensuring that both are clearly defined, well-communicated, and aligned with organizational values can significantly enhance the likelihood of a successful Agile transformation.</p><p><strong>The vision</strong> acts as a North Star, guiding and aligning the efforts of teams and leaders alike. It’s not just about adopting a new methodology; it’s about embracing a vision that resonates with every member of the organization. However, it’s not just the vision itself that’s important. To create a compelling vision, we must understand the reason behind the change — the “why.” As Simon Sinek aptly put it: “It starts with why.”</p><p><strong>The purpose,</strong> the “why,” helps the entire organization to understand the necessity of change. It can be for any reason. For instance, in the “State of Agile 2022” report, 52% of respondents identified accelerating time to market as the key benefit of Agile. But is “Accelerating time to market” enough as a purpose? I don’t believe so. It doesn’t resonate with all employees, nor does it help them understand the need for Agile. It doesn’t aid in making daily decisions and might even lead to misguided actions. “If we’re going to accelerate time to market, why can’t we just work faster and drop all this Agile nonsense?” is a sentiment I’ve encountered. Overcoming this mindset as a coach is challenging.</p><p>No, the compelling why must be on a much higher level. A purpose like, “We will be out of business in three years if we do not implement Agile. We are currently burning out people by working harder instead of smarter, delivering value to our customers too seldom, and the quality is not meeting their expectations.” A manager might continue, “In our vision, we are like a family. Working together, supporting each other. No one is more important than the other. We deliver value often, as often as every week. We listen to each other and to our customers. We engage in fruitful disagreements but unite on a solution. We plan regularly, but the purpose of planning is not to have a plan, but the process itself — the enlightenment of dependencies, the cross-competence knowledge sharing, and matching capacity to demand and demand to capacity. We deliver what we promise, and we promise what we can deliver. And we deliver with quality. This is our vision. How does it sound?”</p><p>This example of a vision, including a compelling purpose, even if imaginary, illustrates the power of having such a vision. The strength lies not only in its formulation but also in its repetition and communication.</p><h3>A real world example</h3><p>This concept of a transformative vision is not just theoretical. Take, for instance, the journey of Ericsson, a case that mirrors the power of a compelling vision. Initially recognized as a hardware-centric company focused on delivering tangible products, Ericsson embarked on a transformative path. Their vision was not just about a shift in product offerings but a fundamental change in their operational ethos — from a box-delivery, hardware-oriented company to a modern, agile, software-focused enterprise.</p><p>This vision steered Ericsson through a series of ups and downs, typical of any significant organizational change. However, their unwavering commitment to this agile transformation vision ultimately led to their success. Today, Ericsson stands as a testament to what can be achieved — the company is now celebrated as a fully agile, software-centric organization, showcasing the transformative power of a well-defined and embraced vision.</p><h3>Reiterating and Communicating the Vision</h3><p>The repetition and frequent communication of the vision are as crucial as the vision itself. A vision that is not constantly communicated risks being forgotten or, worse, misunderstood. It should be integral to everyday conversations, decision-making processes, and strategic meetings. Each repetition reinforces its importance, ensuring that it remains at the forefront of everyone’s mind and actions.</p><p>When a vision is articulated with clarity and conviction, it becomes more than just words; it transforms into a guiding principle that influences behavior and decisions. This process of regular reinforcement helps in embedding the vision into the organizational culture, making it a living, breathing part of the Agile transformation journey.</p><h3>Detailing the vision with strategy</h3><p>While a broad vision sets the direction for Agile transformation, incorporating strategic details is essential for guiding the organization on achieving this vision. These details should be carefully crafted to be directive enough to ensure alignment and steer the organization towards its goals, yet flexible enough to allow for autonomous action and adaptation.</p><p>A detailed strategic vision should strike a balance between providing direction and allowing flexibility. It needs to be “fluffy” enough to encourage creativity and initiative and clear enough to ensure everyone is aligned and moving towards the same objectives. This balance is crucial in Agile environments, where adaptability and responsiveness are key.</p><p>Consider this illustrative example: “ <em>In the first quarter, our focus will be on the Agile teams. We aim to cultivate empowered Agile teams, inclusive of all necessary competencies, working across organizational boundaries to deliver real value to our customers. And by customers, I mean our end-users — the ones paying for our services. These teams should learn about Agile, embrace self-organization, and begin implementing an Agile process. We will not prescribe which methodology they should use, we will learn as we go and go as we learn, starting becoming a learning organization</em> “</p><p>This example demonstrates a strategy that is specific enough to give clear direction — focusing on team empowerment, cross-functional collaboration, and customer-centricity — yet open-ended enough to allow teams to choose their Agile methodologies. This approach encourages teams to take ownership of their Agile journey, fostering a sense of agency and commitment.</p><p>As we saw in the example, leaders play a pivotal role in communicating these strategic details. They must articulate the vision in a way that resonates with and motivates the teams, encouraging them to take the necessary steps toward transformation. This communication should be continuous and consistent, reinforcing the strategic aspects of the vision at every opportunity.</p><h3>Periodic Review and Adaptation of the Agile Vision</h3><p>Agile methodologies, at their core, are about adaptability and responsiveness to change. This principle should, of course, also apply to the strategic vision guiding an Agile transformation. A vision, while providing direction and purpose, should not be static. Instead, it needs to be dynamic, evolving with the organization’s changing context and external environment.</p><p>By regularly reviewing and adapting the strategic vision, organizations can ensure that their Agile journey remains relevant, effective, and aligned with both their internal goals and the external environment. A dynamic vision is a cornerstone of a successful Agile transformation.</p><h3>The Traps of Vision in Agile Transformation</h3><p><strong>Vision Not Known:</strong> Often, I’ve seen organizations where the vision for Agile transformation is vaguely defined or not shared with all members. Or not even known at all. The first question from me when I come to a new organization in the midst of an Agile transformation is “Why? Why are you doing this transformation?” Some organizations and leaders give a very compelling answer, but some struggle to get a meaningful answer. The worst answer I have gotten is: “Because our parallel organization is doing it.”</p><p><strong>Vision Not Aligned:</strong> Another common issue is when the Agile vision is not aligned with the overall organizational goals or varies between different organizational parts. This misalignment creates internal conflicts and mixed messages, diluting the transformation efforts. The vision needs to be a part of, and go hand in hand with, the complete organizational vision, mission, and, of course, strategy. The Agile transformation may be a theme in the company strategy. Maybe it is a good idea to tell customers, shareholders, and the steering committee that we are doing this transformation, and we expect the following outcome …</p><p><strong>Vision Not Enough Communicated:</strong> It’s not uncommon to find that the vision, although well-crafted, is not communicated effectively or frequently enough. Sometimes it is in a document not even accessible for all. I have seen organizations that proudly say when I ask for the vision. “Yes, it is here, we did it last fall on a management workshop”. On my follow-up question on when it was communicated, they say “I think it was communicated briefly once”. This failure in communication leads to a lack of buy-in and enthusiasm among the workforce. Transformation is impossible unless hundreds or thousands of people are willing to help, often to the point of making short-term sacrifices. Employees will not make sacrifices, even if they are unhappy with the status quo, unless they believe that useful change is possible. Without credible communication, and a lot of it, the hearts and minds of the troops are never captured.</p><p><strong>Vision not Clear, Providing Priorities and Directions:</strong> Without clear priorities and directions, even a well-defined vision can become ineffective. Teams need to understand not only the ‘why’ but also the ‘what’ and the ‘how’ of their daily actions towards achieving the Agile transformation. And they need to be empowered to make their own decisions about the details. If you ask for ten teams that shall run Scrum, you will get ten teams that run Scrum. Probably by the book, focusing on the process. But if you ask for 10-ish empowered, cross-organizational, cross-functional, self-organized teams that continuously deliver customer value with high quality, have all the competence, tools, and resources they need, and have fun simultaneously. Guess what you get? Ask for outcomes, not output!</p><h3>Time for Reflection</h3><p>As you reach the end of this article, take a moment to reflect on your organization’s Agile transformation journey:</p><ul><li>How well is your organization’s vision for Agile transformation understood and communicated?</li><li>Is the vision aligned with the broader goals of your organization?</li><li>Have it been enough communicated? Do all understand it?</li><li>Are priorities and directions clear?</li><li>What part will <strong>you</strong> improve tomorrow?</li></ul><h3>Conclusion</h3><p>A powerful and well-communicated vision and purpose forms the bedrock of a successful Agile transformation. It must resonate with everyone, be aligned with broader organizational objectives, and be communicated consistently and effectively. By avoiding the common traps related to the vision and purpose, organizations can set a strong foundation for their Agile journey.</p><p>In coming articles, we will explore each of the remaining ten areas where Agile transformations commonly fail. Armed with the understanding that it all starts with a clear, compelling, and well-communicated vision and purpose, we next turn our attention to another critical aspect of Agile transformations: leadership engagement and alignment. So stay tuned!</p><p>This article is the second in a series of articles about common mistakes in agile transformations. <a href="https://agiletto.se/subscribe">Subscribe</a> to my newletter not to miss the rest!</p><h3>Previous article in the series</h3><ul><li><a href="https://agiletto.se/blog/most-agile-transformations-fail-12-common-mistakes-revealed">Most Agile Transformations Fail: 12 Common Mistakes Revealed - Agiletto AB</a></li><li><a href="https://medium.com/@jorgen.karlsson/most-agile-transformations-fail-12-common-mistakes-revealed-1a4ca6382852">Most Agile Transformations Fail: 12 Common Mistakes Revealed</a></li></ul><p><em>Simultaneously published at </em><a href="http://agiletto.se/blog/mistake-1-no-vision-no-victory-the-root-cause-of-agile-transformation-failure"><em>https://agiletto.se</em></a><em> on August 12, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2a5877a0764" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>