<?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 Imran Qazi on Medium]]></title>
        <description><![CDATA[Stories by Imran Qazi on Medium]]></description>
        <link>https://medium.com/@imran-qazi?source=rss-99956f423126------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HSlL5iVNRoxW1T7XKUZMvQ.jpeg</url>
            <title>Stories by Imran Qazi on Medium</title>
            <link>https://medium.com/@imran-qazi?source=rss-99956f423126------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:40:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@imran-qazi/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[Managing Cognitive Load in the AI Era]]></title>
            <link>https://imran-qazi.medium.com/managing-cognitive-load-in-the-ai-era-1d69ce7095dc?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d69ce7095dc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai-productivity]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 11:25:26 GMT</pubDate>
            <atom:updated>2026-10-14T12:11:27.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kehvu9UkyBYt-z1C_psokw.png" /></figure><p><em>Making domain learning reusable in AI-assisted delivery</em></p><p>In <em>Team Topologies</em>, Matthew Skelton and Manuel Pais describe a practical constraint on software delivery: teams can only handle so much complexity.</p><p>Their application of cognitive load gives engineering leaders a useful way to think about that constraint:</p><p><strong>Intrinsic load</strong> includes the technical knowledge needed to do the work, such as understanding a language or framework.</p><p><strong>Extraneous load</strong> comes from friction around the work, including cumbersome processes and unnecessary coordination.</p><p><strong>Germane load</strong> is the effort devoted to learning and valuable problem-solving, including understanding the business domain.</p><p>The principle is to minimise intrinsic load, remove extraneous load wherever possible, and create room for germane thinking. <a href="https://teamtopologies.com/s/Organization-Dynamics-with-Team-Topologies-Mini-book-MB80.pdf">Team Topologies explains the framework here</a>.</p><p>AI gives us new ways to apply this principle. It can help produce requirements, backlog items and code. The leadership opportunity is to use that assistance to create more capacity for understanding the business.</p><p>My argument is that shared project context can make that understanding reusable. What people discover and agree can become knowledge that guides subsequent AI-assisted work.</p><p>A recent experience with our team made this tangible.</p><h3>One assumption changed the business rule</h3><p>We were asked to produce a complex business system within a very tight timeline. The domain was new to the software engineers, and we did not have time for the discovery work we would normally want before implementation.</p><p>While developing a business rule, we assumed that tasks had to be completed in a fixed sequence, with each task following the previous one.</p><p>Within a day, AI-assisted analysis of the requirement helped reveal that the assumption was wrong. The tasks could be completed in any order.</p><p>That correction had potentially significant implications. A sequential interpretation could have led us to build dependencies or restrictions the business did not require. Code and tests could have faithfully implemented the wrong rule.</p><p>This is the kind of work our engineers are spending more time on: exploring requirements, generating questions and testing assumptions with AI. We review requirements with domain experts, correct them and update the shared context for future iterations.</p><p>The speed of analysis matters. So does what happens to the knowledge afterwards.</p><h3>Give the learning somewhere to live</h3><p>We maintain our project context in a shared wiki. It includes notes, requirements, business rules and decisions, open questions, architecture decisions, meeting transcripts and implementation information.</p><p>The team and its AI agents use that context to develop backlog items and features iteratively. The agents’ context is updated as new or corrected information is added to the wiki.</p><p>Questions lead to discussions with domain experts. Agreed corrections return to the context and inform subsequent work.</p><p>For the task-order example, the corrected rule is the knowledge we want future work to use. The earlier sequential interpretation also needs to be marked as superseded. Keeping both versions without distinguishing them would leave ambiguity in the context.</p><p>The aim is to maintain an evolving account of what the team understands, what has been decided and what still needs an answer.</p><p>This approach brings all three types of cognitive load into view.</p><h3>Intrinsic load: make technical knowledge accessible</h3><p>AI can help engineers explore unfamiliar code and explain how parts of a system fit together. Architecture decisions and implementation notes give those explanations context about the team’s chosen approach.</p><p>Engineers still need to check explanations against the implementation and understand how the system behaves. Pairing, mentoring and deliberate technology choices remain useful. Every additional framework or service introduces something the team may need to diagnose and maintain.</p><p>The practical test is whether engineers can explain the system, change it safely and investigate a failure. Easier generation needs to be accompanied by the technical capability to own the result.</p><h3>Extraneous load: reduce repeated reconstruction</h3><p>Project knowledge is often reconstructed from conversations, messages and individual memory. A decision gets explained again, then translated into requirements, backlog items and implementation guidance.</p><p>Shared context gives people and AI a common source to work from. AI can assist with expressing requirements and generating delivery artefacts, while the team assesses whether those artefacts reflect the intent.</p><p>Backlog development still requires judgement. Structuring an agreed requirement and deciding whether it deserves priority involve different kinds of thinking.</p><p>Review also takes effort. A polished requirement can contain a wrong assumption. Tests can repeat the same error as the code.</p><p>Keep increments focused enough to assess and make the relevant decisions visible to reviewers. Automated checks can handle repeatable validation, leaving people more attention for business meaning and technical judgement.</p><p>The opportunity is to reduce avoidable searching, repetition and reconstruction around that essential work.</p><h3>Germane load: turn questions into shared understanding</h3><p>The task-order example illustrates why domain thinking deserves protected attention. Producing an implementation from the initial assumption would not have established the correct business rule.</p><p>AI supported the exploration. Domain expertise helped us correct requirements. The wiki gives the resulting knowledge somewhere to remain available.</p><p>The shift we are observing is that engineers spend more time understanding the domain than generating code. They work with AI to explore what requirements mean and where assumptions need to be challenged.</p><p>This suggests a useful relationship: better domain understanding can improve human judgement and the context available for AI-assisted delivery. Review and implementation can then expose further questions, creating opportunities to deepen that understanding.</p><p>Our experience of correcting assumptions and requirements supports this hypothesis. Establishing how consistently it improves delivery will require looking at the wider process, including maintenance, review and rework.</p><h3>Shared context needs people to maintain it</h3><p>Keeping the wiki current is a challenge. It creates continuing work, which we consider worthwhile.</p><p>We have assigned responsibility for it. The business analyst maintains business decisions and rules. The technical lead maintains architecture decisions and the implementation approach. Subject matter experts are responsible for resolving open questions.</p><p>Those responsibilities matter because recorded information can still be incomplete, outdated or unsettled. A transcript preserves a discussion; it does not necessarily establish an agreed decision.</p><p>In his <a href="https://teamtopologies.com/news-blogs-newsletters/team-topologies-for-the-ai-age-stewardship-of-value-flow">update on Team Topologies for the AI age</a>, Matthew Skelton emphasises stewardship of value flow: human teams remain responsible for its ongoing health and direction as AI performs more production work.</p><p>For our approach, stewardship includes maintaining the context and having enough knowledge to assess the output. Reviewers need to recognise mistaken assumptions and know when to involve an expert. That responsibility continues as the team supports and evolves the software it accepts.</p><h3>Protect the capacity to understand</h3><p>Our deadline meant we had to carry more discovery into delivery. Shared context has helped us preserve that learning, but the need to understand the business remains.</p><p>Engineering leaders can support this by making time for domain conversations, assigning responsibility for current knowledge and using small increments to expose uncertainty.</p><p>They also need to decide where any released capacity goes. If easier drafting and coding simply lead to more work in progress, the space for learning can disappear.</p><p>Within a day, our team challenged an interpretation that could have shaped the system incorrectly. The continuing value of that correction depends on making it available to the people and AI agents working on the next increment.</p><p>That is where the cognitive load argument becomes practical: reduce friction around delivery, protect the thinking that establishes what is right, and make what the team learns useful beyond the moment of discovery.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d69ce7095dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helpful Leaders are the Ultimate Bottleneck]]></title>
            <link>https://medium.com/being-agile/helpful-leaders-are-the-ultimate-bottleneck-33521eb6afa6?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/33521eb6afa6</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[managing-people]]></category>
            <category><![CDATA[taking-ownership]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 00:01:32 GMT</pubDate>
            <atom:updated>2026-01-19T00:06:06.491Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*F4fGJopfCVgUMbZl0UYWzg.png" /><figcaption>I keep a toy monkey at my desk to remind people of ‘Managing Monkey’ concept</figcaption></figure><p>Helpful leaders create helpless teams.</p><p>I learnt this the hard way. Early in my career, I thought “leading” meant “fixing.” When someone brought me a problem, my instinct was to roll up my sleeves and dive in. It felt noble. It felt like I was being a servant leader.</p><p>It wasn’t noble. It was a disaster.</p><p>By jumping in to save the day, I was actually doing three things:</p><ol><li>Stealing ownership.</li><li>Stripping away context.</li><li>Training my people to escalate by default.</li></ol><p>The cost? A culture of dependency. More rework, slower delivery, and a team that stopped thinking for themselves because they knew I’d do the thinking for them.</p><h3>Who’s got the monkey?</h3><p>The turning point for me was an HBR classic: <em>Management Time: Who’s Got the Monkey?</em></p><p>Think of every problem as a “monkey.” When a team member mentions a challenge and you say, <em>“Let me think about that and get back to you,”</em> the monkey just leaped from their back to yours.</p><p>Suddenly, you’re the one with the To-Do list, and your team is standing around waiting for <em>you</em> to move. You’ve become the bottleneck.</p><h3>My “No Monkey” Rules</h3><p>I’ve had to rewire my brain. Now, when a problem arrives, I don’t let it jump. I help the owner care for it.</p><p>Here’s how I keep the primates where they belong:</p><ul><li><strong>Clarify ownership:</strong> I ask, <em>“Whose decision is this?”</em> If it’s theirs, it stays theirs. No exceptions.</li><li><strong>Coach before you answer:</strong> I ask, <em>“What options have you considered?”</em> I’m looking for their logic, not giving them mine.</li><li><strong>Agree on the next action:</strong> The next step stays with the owner, not me. I’m a sounding board, not a task-taker.</li><li><strong>Set cadence, not control:</strong> I review the <em>outcomes</em>, not the “how.” If the result is right, the process belongs to them.</li><li><strong>Make it visible:</strong> I literally keep a toy monkey on my desk. It’s a silent, slightly cheeky reminder to the whole room: <strong>Don’t hand me your primate.</strong></li></ul><h3>The Bottom Line</h3><p>Leadership isn’t about solving every issue. It’s about creating the conditions where the right people solve the right problems at the right level.</p><p>When you take the monkey, you aren’t being helpful. You’re being a hurdle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33521eb6afa6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/helpful-leaders-are-the-ultimate-bottleneck-33521eb6afa6">Helpful Leaders are the Ultimate Bottleneck</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking, Fast and Slow — A Synopsis via a mindmap]]></title>
            <link>https://medium.com/being-agile/thinking-fast-and-slow-a-synopsis-via-a-mindmap-678f9bc858ba?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/678f9bc858ba</guid>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[the-human-mind]]></category>
            <category><![CDATA[thinking]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Mon, 11 Oct 2021 06:20:39 GMT</pubDate>
            <atom:updated>2021-10-11T06:43:58.075Z</atom:updated>
            <content:encoded><![CDATA[<h3>Thinking, Fast and Slow — A Synopsis via a mindmap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVniO2FZsuP4wwfJXdpf5g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hal Gatewood</a> on <a href="https://unsplash.com/s/photos/brain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I recently finished the book Thinking, Fast and Slow by Daniel Kahneman. It is a fascinating book that describes the working of the human mind by introducing the reader to two fictitious characters. The characters are called System 1 and System 2.</p><p>These characters are introduced to explain the two modes of thinking by the human brain. One mode where the thinking happens automatically and quickly, for example, the emotion and thinking that is evoked by looking at a photo of an angry woman or a smiling baby. The second mode is evoked when dealing with effortful mental activities such as complex computations for example 17 x 24.</p><p>Daniel Kahneman defines the two systems as follows</p><h4>System 1</h4><p>Operates automatically and quickly, with little or no effort and no sense of voluntary control.</p><h4>System 2</h4><p>Allocates attention to the effortful mental activities that demand it, including complex computations. The operations of System 2 are often associated with the subjective experience of agency, choice, and concentration.</p><p>The rest of the book is written in a way that describes the psychodrama with the two characters. The book explains the working of the two systems with real-world examples. My take on the book is that it can be a challenge to grasp it completely.</p><p>I thought it would be useful to create a mindmap of the working of System 1 and 2 to help me visualize the two modes of thinking. I found this exercise helpful in understanding the two thinking modes. I hope that other readers of the book will find it useful. I will very much appreciate it if you can let me know what you think and provide some feedback if you have read the book.</p><p>The full interactive mindmap can be viewed at the following <a href="https://miro.com/app/board/o9J_luMRTxk=/?invite_link_id=136363634490">miro board</a>. A static image of the mindmap is shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O--Od7InRKTRUOSpHYHX6w.jpeg" /><figcaption>Thinking, Fast and Slow — A mindmap</figcaption></figure><h4>References</h4><p><em>Kahneman, Daniel. Thinking, Fast and Slow Penguin Books Ltd.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=678f9bc858ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/thinking-fast-and-slow-a-synopsis-via-a-mindmap-678f9bc858ba">Thinking, Fast and Slow — A Synopsis via a mindmap</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Progressive Web App (PWA)?]]></title>
            <link>https://medium.com/being-agile/what-is-a-progressive-web-app-pwa-ef3b95030820?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef3b95030820</guid>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Fri, 01 Oct 2021 05:41:53 GMT</pubDate>
            <atom:updated>2021-10-04T05:00:29.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zHYtJ0-ImQytc-JSmIyxSA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@liza-summer?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Liza Summer</a> from <a href="https://www.pexels.com/photo/crop-broker-using-trading-app-on-smartphone-against-laptop-6347711/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h4>And how you can use them to your advantage</h4><p>Before I explain what is Progressive Web Apps and how you can use them to your advantage, let&#39;s have a look at the traditional ways of distributing mobile apps.</p><p>The mobile apps are distributed via app stores. There are however certain challenges in app management and distribution via these channels.</p><ul><li>The app store releases process includes a review each time you need to release the app. This process can take hours and sometimes days. The review process can raise objections that must be fixed and the app needs to go through the process again. This can delay the urgent releases</li><li>App updates rely on user settings for upgrades. If the user does not have automatic updates for the apps, this will mean that the app will only be updated if the user does it manually. This can cause issues with critical bug fixes and features availability</li><li>App stores have strict policies around financial transactions within the app. Both Apple and Google do not allow third-party payments via their platform. You must use an apple or android in-app purchase platform that can extract up to 30% of the transaction as a fee</li></ul><h4>Progressive Web Apps (PWA)</h4><p>PWA’s provide an answer to these challenges in certain use cases especially if you are building an enterprise or business app that needs to be available via mobile.</p><p>PWA’s are created using web frameworks and delivered via URLs. Same as any web app or webpage. The difference is that once they are accessed via the mobile app, the user can pin the app to their phone home screen. Once that is done, the app work and behaves exactly like a native mobile app.</p><p>There are great advantages in building and distributing apps as PWA:</p><p><strong>Cost</strong></p><p>PWA is cost-effective. As you do not have to deal with Native Code for iOS and Android or plugins as in the case of Hybrid app development — you build the PWA once and run anywhere. You can even customize the app for desktop use. This increases your delivery channels and makes it easy for your users to do work in-field or in the office using a single codebase.</p><p><strong>Distribution</strong></p><p>Distribution is via URL so all you need to do is to send your users the URL or promote it via various other channels. Once the user pins the app to the home screen it will become a normal app.</p><p><strong>App Update</strong></p><p>Any app updates are distributed to the users automatically. This greatly reduces the release time and urgent and critical fixes can get to the users as soon as they are available.</p><p><strong>Native Capability</strong></p><p>Most of the native mobile functionality such as Camera, GPS are now available via a PWA. It works offline so you can create an app that is capable of working in the areas where connectivity is an issue.</p><p><strong>Cloud Capability and Integration</strong></p><p>As a web app, it can integrate with any cloud service for additional features such as payments. This allows providing a payment facility without having to pay the transaction fee to Apple and Android stores. The PWA can integrate with any enterprise-wide systems such as Single Sign-on, HR, Finance etc. This creates a seamless experience to carry out enterprise-level tasks with advanced capability.</p><p><strong>Conclusion</strong></p><p>In short, PWA can provide an enterprise app to enable users to do work anywhere, anytime saving time, money and streamlining business processes in a cost-effective way.</p><p>Interested in building a PWA — Talk to <a href="http://lapisit.com.au/">Lapis </a>today for a free consultation.</p><ul><li><a href="http://lapisit.com.au/">Lapis </a>Case Study eCatch — An offline-capable PWA app to help Victorian Commercial Fishers complete their mandatory logbook submission to Victorian Fisheries Authority <a href="https://ecatch.vfa.vic.gov.au/portal/#/login">https://ecatch.vfa.vic.gov.au/portal/#/login</a></li><li>General Case Studies — <a href="https://web.dev/clipchamp/">https://web.dev/clipchamp/</a></li><li>PWA App List — <a href="https://www.pwalist.app/">https://www.pwalist.app/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef3b95030820" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/what-is-a-progressive-web-app-pwa-ef3b95030820">What is a Progressive Web App (PWA)?</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to succeed with agile where agile frameworks fail?]]></title>
            <link>https://medium.com/being-agile/how-to-succeed-with-agile-1ed729f8950a?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ed729f8950a</guid>
            <category><![CDATA[agile-principles]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team-performance]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Wed, 16 Jun 2021 23:17:13 GMT</pubDate>
            <atom:updated>2021-06-16T23:52:12.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zf5z7CYqcMBRnWTgLzFZQ.jpeg" /></figure><blockquote>Focus on agile principles, be flexible on the agile framework</blockquote><p>A team can apply an agile framework (Scrum, Kanban, Safe, etc), yet it can still be far from being agile. Agile frameworks facilitate agility, but without a change in the mindset, true agility can remain elusive. Unfortunately, many teams experience this. They implement an agile framework but fail to achieve agility.</p><p>So, how can teams instill an agile mindset?</p><p>One way is to review the agile principles to set a team’s behavior and processes. Then encourage the behaviors that will create an agile culture and mindset.</p><p>So let&#39;s see what the agile principles tell us. There are 12 agile principles. For simplicity, I will class them into four broader groups</p><h4>Group 1: Delivery of working software</h4><p>I chose the following agile principles as part of this group</p><ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</li><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</li><li>Working software is the primary measure of progress.</li></ul><p>If your team is not delivering working software in the hands of your customers often, then no matter what framework you are using, you are not agile. The first priority of your team should be to deliver working software often. Your processes, tools, and framework should facilitate this. If this is not the case, review your process and adjust.</p><h4>Group 2 — Collaboration and Motivation</h4><p>I chose the following agile principles as part of this group.</p><ul><li>Business people and developers must work together daily throughout the project.</li><li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</li><li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</li><li>The best architectures, requirements, and designs emerge from self-organizing teams.</li></ul><p>Your framework and processes should encourage collaboration. True collaboration happens when the cross-functional team works as a unit to deliver value to the clients.</p><p>If the team is not talking to the customers they should change that. The entire team should be part of understanding the requirements. This will usually mean that the whole team needs to work with the business and other stakeholders. This includes developers, BA, Testers, Product Owners etc.</p><p>The team should also take responsibility and aims to become self-organized. The best solutions emerge from self-organizing teams.</p><blockquote>Remember: “No one can whistle a symphony. It takes an orchestra to play it.” — H.E. Luccock</blockquote><h4>Group 3— Don’t do work that does not add value</h4><p>I chose the following agile principle as part of this group.</p><ul><li>Simplicity–the art of maximizing the amount of work not done–is essential.</li></ul><p>My view is that this is one of the most critical and misunderstood principles of agile. This is the reason that this single principle forms its own group.</p><p>The team should ensure that they are not doing anything that does not add value. Examine every task and process and ask the question — Does this task or process add enough value? Then be brave in cutting the waste as this will mean making hard decisions.</p><blockquote>Remember: “There is nothing so useless as doing efficiently that which should not be done at all” — Peter Drucker</blockquote><h4>Group 4— Continuous Improvement</h4><p>Finally, I chose the following principles under this group</p><ul><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</li><li>Continuous attention to technical excellence and good design enhances agility.</li><li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</li><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.</li></ul><p>The teams should have a sharp focus on continuous improvement. A relentless pursuit of being better at what they do. This includes open to change even late in development for the customer’s benefit. Focus on technical excellence. Pause and reflect to become more effective.</p><p>The changes do not have to be big. The team can apply Kaizen principles to help them achieve continuous improvement.</p><blockquote>Remeber : “Continuous improvement is better than delayed perfection” — Mark Twain</blockquote><p>With a sharp focus on these principles, the team will deliver more value to their stakeholders. This will help the team succeed with agile with any chosen framework.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ed729f8950a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/how-to-succeed-with-agile-1ed729f8950a">How to succeed with agile where agile frameworks fail?</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Strategy for improving team agility]]></title>
            <link>https://medium.com/being-agile/a-simple-strategy-for-better-teams-262d1af3c19f?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/262d1af3c19f</guid>
            <category><![CDATA[business-agility]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 06:52:52 GMT</pubDate>
            <atom:updated>2021-02-25T22:31:01.550Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G-IMOqUDI0uLVPLyPzw_CA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fauxels?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">fauxels</a> from <a href="https://www.pexels.com/photo/multi-cultural-people-3184419/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><blockquote>Create the next level of team agility using a Network-based competency Structure</blockquote><p>Stephen Denning in his book <em>The Age of Agile</em> outlines three ‘Laws of Agility’:</p><ul><li>The<strong> Law of the Small Team</strong> states that the complex tasks are best done by small cross-functional autonomous teams</li><li>The<strong> Law of the Customer</strong> states that the organisations exist to serve the customer and not the stakeholders. This is a fundamental shift from the previous view that the organisations exist to maximise the value for their shareholder</li><li>The<strong> Law of the Network</strong> states that a network is a set of teams that interact with and collaborate with other teams with the same connectivity, interaction, and passion as they do within their own small team</li></ul><p>In this blog, I will talk about how we have used the two laws (Law of the small team and Law of Network) to take our team to the next level of agility. These two laws can be applied by any team to take the team to the next level. Here’s how.</p><h4>Law of the small team — <strong>Define smaller teams within your team</strong></h4><p>At <a href="http://lapisit.com.au/">Lapis</a>, we created small teams based on competencies within our larger development team. We first identified four areas of competencies based on the work we do, and the skills and interests of our team members. The four areas are:</p><ul><li>UI/UX or Front-end Technologies</li><li>API or Backend Technologies</li><li>DevOps — All things related to DevOps including Cloud-based Services in AWS and Azure</li><li>QA/BA — All things related to software testing and business analysis</li></ul><p>Each team is encouraged to ‘own’ their competency area and work internally to solve complex problems and champion improvements. As per the law of the Small Team’, this helps us achieve the greatest outcome as a collective.</p><h4>Law of the Network — <strong>Small teams talking to each other</strong></h4><p>We then bring in ‘Law of the Network’ with our small teams sharing their learnings and ideas with other groups. This strengthens the overarching organisational capability and helps us perform better overall as a broader team.</p><p>Below is a diagram of our small teams and competency-based network implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*vtJS-tXhGOBuKV9mstxffg.png" /><figcaption>Lapis — Competency-Based Network Implementation</figcaption></figure><p>This implementation has created a powerful mechanism for people to work on issues and improvements, and create a network across the organisation with other areas of competencies.</p><p>It has also helped us move away from hierarchical-based thinking — that only senior members of the team or team members with the right title are responsible for making important decisions. It is now the responsibility of the competency area team. Other areas of competencies are there to support and together, they lift the capability of the whole organisation.</p><p>For us, this implementation has added another level of agility and significantly improved our team’s capability to deliver continuous value to our clients. Give it a go — your team will be better for it.</p><p><em>Hi, I’m Imran, Business Manager at </em><a href="http://lapisit.com.au/"><em>Lapis</em></a><em>, and I’m passionate about creating high-performing teams. </em><a href="https://www.linkedin.com/in/imranqazi/"><em>Connect with me on LinkedIn.</em></a></p><p><em>Reference: The Age of Agile by Stephen Denning</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=262d1af3c19f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/a-simple-strategy-for-better-teams-262d1af3c19f">A Simple Strategy for improving team agility</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story of Objectives and Key Results (OKR) Implementation — Part 1]]></title>
            <link>https://medium.com/being-agile/story-of-objectives-and-key-results-okr-implementation-part-1-ded9964b9f7d?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/ded9964b9f7d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business-agility]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Mon, 19 Oct 2020 23:28:05 GMT</pubDate>
            <atom:updated>2020-10-19T23:28:05.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JxoYnogfJ0Dha-4EYC_TEg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fauxels?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">fauxels</a> from <a href="https://www.pexels.com/photo/photo-of-person-holding-mobile-phone-3183153/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h3>Story of Objectives and Key Results (OKR) Implementation — Part 1</h3><p>This is a story of our attempt to implement OKR at <a href="http://lapisit.com.au/">Lapis</a>. This stage where we are defining the OKR for Q1 — 2021. This blog is a reflection of our process and experience so far.</p><p>First things first — let&#39;s talk about what Objectives and Key Results (OKR) are. For those who are not familiar with the framework, OKR is a management tool for defining and executing significant business goals.</p><h4>Objective</h4><p>An Objective (O) is simply what is to be achieved. An objective is significant, concrete, action-oriented, and (ideally) inspirational. When properly designed and deployed, they are a vaccine against fuzzy thinking — and fuzzy execution (1).</p><h4>Key Result</h4><p>KEY RESULTS (KR) benchmark and monitor HOW we get to the objective. Effective KRs are specific and time-bound, aggressive yet realistic. Most of all, they are measurable and verifiable. It’s not a key result unless it has a number. You either meet a key result’s requirements or you don’t; there is no grey area, no room for doubt (1).</p><h4>Initiative</h4><p>Some people add another dimension to the OKR called initiatives. These are the steps and actions that one takes to achieve key results in order to complete the Objective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*Hx-Wlx1srz0PWUZv1Akr1Q.png" /><figcaption>An Example of OKR</figcaption></figure><p>How does OKR differ from a traditional annual goals process? The key differences are:</p><ul><li>OKRs are usually set for, and measured every quarter. This enables a more agile approach of inspecting and adapting if things do not go according to the plan.OKRs are usually reviewed every 4–6 weeks by the team.</li><li>OKRs are not tied to compensation. This enables the team to set the OKRs that are aggressive and inspirational. This means that even if the OKRs are not achieved 100% — significant progress (70% above) will result in substantial improvement and gains.</li></ul><h4>Lapis OKR Implementation</h4><p>Adopting OKRs is a change — It requires a change management process. At Lapis, we started with an introduction to OKR. In the same meeting, we tried to set some OKRs for the upcoming financial year Q1 — (BIG MISTAKE). Never mix the introduction to the concept with implementation. OKR is a change and it needs to be handled as a change process. No matter where your organization is in terms of the goals process — OKRs will be a change to that process.</p><p>In addition, OKRs demand a sharp focus and commitment. This means that the existing processes and goals will have to be changed or transitioned to OKRs. Defining Objectives that are important and related Key Results that are measurable is a challenge. Lapis team faced the same challenge. What Objective to keep and what to drop. What will be the level of commitment we can afford in addition to the normal activities of running the business?</p><p>So, we took a step back and did some analysis. We reviewed our current goals and processes. We did a budget estimation of what we can afford in terms of Research and Development and Personal Development and what we will need to grow the company. This analysis provided us with a clear pathway to set Objectives in the following categories</p><ul><li>Research and Development</li><li>Personal Development</li><li>Business Growth</li><li>Operational Excellence</li></ul><p>We created 4 Ojectives and developed Key Results in each of the categories for Q1. We defined OKRs on the following basis</p><ul><li>What is important</li><li>What we can afford (budget), and</li><li>What we can substantially achieve (practical).</li></ul><p>Here is our initial version of OKRs for Q1 — 2021. The diagram below includes Objectives, Key Results, and Initiatives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLFKQhWA6_WzNXUcPyO03A.png" /><figcaption>Lapis OKRs for Q1 2021</figcaption></figure><p>I will keep this series updated as we move to the implementation phase. I hope that this experience will provide some insights to those who are planning to use OKRs. If you have experience with OKRs I would love to hear your thoughts.</p><ol><li>Doerr, John. Measure What Matters (p. 7). Penguin Books Ltd. Kindle Edition.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ded9964b9f7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/story-of-objectives-and-key-results-okr-implementation-part-1-ded9964b9f7d">Story of Objectives and Key Results (OKR) Implementation — Part 1</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are faking agile without real customer collaboration]]></title>
            <link>https://medium.com/lapis/you-are-faking-agile-without-real-customer-collaboration-5e0465eb6aba?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e0465eb6aba</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Wed, 16 Sep 2020 23:26:58 GMT</pubDate>
            <atom:updated>2020-09-16T23:26:58.296Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_dzAl_q83TbAws0k1iPZg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fauxels?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">fauxels</a> from <a href="https://www.pexels.com/photo/photo-of-people-having-meeting-3183186/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><blockquote>No one can whistle a symphony. It takes a whole orchestra to play it. — H.E. Luccock</blockquote><p>Agile success lies in creating the highest value for the available budget and resources. This does not happen by only adopting agile — a continuous focus and close customer collaboration are vital to achieving this. ‘Customers’ includes project sponsors, product owners, wider stakeholders, and users of the system.</p><p>Technical teams have an inherent difficulty in creating real collaboration with their customers. The difference in language and motivational factors between technical and business people can be a barrier. Technical teams are passionate about technical excellence. They want to create new products and features. The business owners focus on business value and end-customer needs. There will be times when these two things might not have a natural alignment.</p><p>Real collaboration is more than just talking to customers. It is about creating a common understanding of the complex software development process. Balancing the technical team’s motivational factors, and business owner’s need in order to maximize value. It is coming up with real ideas about product features together. It is about designing a short and effective feedback process.</p><p>So how do we engage customers in a meaningful and productive collaborative mindset? Here are 5 ways to create a collaborative environment to achieve the highest value.</p><h4>Make it easy — Start with explaining agile and continue with coaching</h4><p>Start the new project with a session on the development process. Ensure that the customers understand the high-level process, its benefits, and constraints. Explain how the development team does things and what the team will need from the customers.</p><p>After the initial explanation, continue to coach your customers in agile. You do this with your development team and product owners. Expand this to the wider group. You do not have to make your customers experts in agile. The aim is to create enough understanding so that technical teams and customers can work in a productive way.</p><p>Focus on topics that will help customers and the team increase the value of the available budget.</p><h4>Make them partners</h4><p>Trust your customers and make them real partners in the project. Highlight the challenges the team faces. Explain the reasons behind technical decisions in layman terms. There will be certain features that are more expensive due to technical reasons. With a clear understanding, customers will be able to make informed decisions as to whether a simplified implementation may suffice or the original requirement still provides business value.</p><p>Help your team to see your customer’s perspective. You can play a key role in helping your team understand the business challenges and needs. It will even be better when your customer explains business to the technical team.</p><p>Don’t spend time on the technical issues when other simpler solutions are available.</p><h4>Make it transparent</h4><p>Your customers should have access to all the aspects of the project all the time. They should know the high-level schedule and the budget burndown versus features delivered. They should be clear on the risks and mitigation strategies. They should have access to the product backlog and the sprint board. Make it easier for your customers to understand all aspects of the project.</p><p>This will make it easier for the development team to have meaningful discussions with them, resulting in better value.</p><h4>Create diverse channels of communication</h4><p>People have their own preferences of how they communicate. Some people like email, while others favor a chat app. Some people are more comfortable having regular meetings. Create diverse channels of communication. This will help engage your customers in a much more productive way.</p><p>The increase in engagement will result in building trust and better products.</p><h4>Establish a short feedback loop</h4><p>Scrum has a two-week feedback loop (Sprint Reviews). This is out of date and I have written about this in my <a href="https://medium.com/being-agile/a-week-is-a-long-time-in-politics-two-weeks-can-be-longer-in-product-development-5e0bf48a765d">blog </a>about the benefits of shorter feedback.</p><p>We have found that meeting your customers every two days works quite well. These meetings are short (15 mins) like stand-ups to show progress and get feedback. Create a small end to end feature slice that you can show your customers in these meetings. We even show the feature from the developer computer if it is not complete to get feedback. We have meetings to get feedback on wireframes, UI/UX designs to help make decisions. This saves time and saving time increases the value.</p><p>As Henry Ford said — if everyone is moving forward together, then success takes care of itself. This is also the key to getting the highest value from available resources and your success with agile.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e0465eb6aba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lapis/you-are-faking-agile-without-real-customer-collaboration-5e0465eb6aba">You are faking agile without real customer collaboration</a> was originally published in <a href="https://medium.com/lapis">Code道</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are faking agile without real customer collaboration]]></title>
            <link>https://medium.com/being-agile/you-are-faking-agile-without-real-customer-collaboration-3f533c8dfa08?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f533c8dfa08</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Mon, 17 Aug 2020 01:55:19 GMT</pubDate>
            <atom:updated>2020-09-15T01:47:14.950Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_dzAl_q83TbAws0k1iPZg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fauxels?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">fauxels</a> from <a href="https://www.pexels.com/photo/photo-of-people-having-meeting-3183186/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><blockquote>No one can whistle a symphony. It takes a whole orchestra to play it. — H.E. Luccock</blockquote><p>Agile success lies in creating the highest value for the available budget and resources. This does not happen by only adopting agile - a continuous focus and close customer collaboration are vital to achieving this. ‘Customers’ includes project sponsors, product owners, wider stakeholders, and users of the system.</p><p>Technical teams have an inherent difficulty in creating real collaboration with their customers. The difference in language and motivational factors between technical and business people can be a barrier. Technical teams are passionate about technical excellence. They want to create new products and features. The business owners focus on business value and end-customer needs. There will be times when these two things might not have a natural alignment.</p><p>Real collaboration is more than just talking to customers. It is about creating a common understanding of the complex software development process. Balancing the technical team’s motivational factors, and business owner’s need in order to maximize value. It is coming up with real ideas about product features together. It is about designing a short and effective feedback process.</p><p>So how do we engage customers in a meaningful and productive collaborative mindset? Here are 5 ways to create a collaborative environment to achieve the highest value.</p><h4>Make it easy — Start with explaining agile and continue with coaching</h4><p>Start the new project with a session on the development process. Ensure that the customers understand the high-level process, its benefits, and constraints. Explain how the development team does things and what the team will need from the customers.</p><p>After the initial explanation, continue to coach your customers in agile. You do this with your development team and product owners. Expand this to the wider group. You do not have to make your customers experts in agile. The aim is to create enough understanding so that technical teams and customers can work in a productive way.</p><p>Focus on topics that will help customers and the team increase the value of the available budget.</p><h4>Make them partners</h4><p>Trust your customers and make them real partners in the project. Highlight the challenges the team faces. Explain the reasons behind technical decisions in layman terms. There will be certain features that are more expensive due to technical reasons. With a clear understanding, customers will be able to make informed decisions as to whether a simplified implementation may suffice or the original requirement still provides business value.</p><p>Help your team to see your customer’s perspective. You can play a key role in helping your team understand the business challenges and needs. It will even be better when your customer explains business to the technical team.</p><p>Don’t spend time on the technical issues when other simpler solutions are available.</p><h4>Make it transparent</h4><p>Your customers should have access to all the aspects of the project all the time. They should know the high-level schedule and the budget burndown versus features delivered. They should be clear on the risks and mitigation strategies. They should have access to the product backlog and the sprint board. Make it easier for your customers to understand all aspects of the project.</p><p>This will make it easier for the development team to have meaningful discussions with them, resulting in better value.</p><h4>Create diverse channels of communication</h4><p>People have their own preferences of how they communicate. Some people like email, while others favor a chat app. Some people are more comfortable having regular meetings. Create diverse channels of communication. This will help engage your customers in a much more productive way.</p><p>The increase in engagement will result in building trust and better products.</p><h4>Establish a short feedback loop</h4><p>Scrum has a two-week feedback loop (Sprint Reviews). This is out of date and I have written about this in my <a href="https://medium.com/being-agile/a-week-is-a-long-time-in-politics-two-weeks-can-be-longer-in-product-development-5e0bf48a765d">blog </a>about the benefits of shorter feedback.</p><p>We have found that meeting your customers every two days works quite well. These meetings are short (15 mins) like stand-ups to show progress and get feedback. Create a small end to end feature slice that you can show your customers in these meetings. We even show the feature from the developer computer if it is not complete to get feedback. We have meetings to get feedback on wireframes, UI/UX designs to help make decisions. This saves time and saving time increases the value.</p><p>As Henry Ford said — if everyone is moving forward together, then success takes care of itself. This is also the key to getting the highest value from available resources and your success with agile.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f533c8dfa08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/you-are-faking-agile-without-real-customer-collaboration-3f533c8dfa08">You are faking agile without real customer collaboration</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 things I have learned about effective remote teamwork during Covid-19]]></title>
            <link>https://medium.com/being-agile/5-things-i-have-learned-about-effective-remote-teamwork-during-covid-19-8a1deb6be8f6?source=rss-99956f423126------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a1deb6be8f6</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Imran Qazi]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 23:38:20 GMT</pubDate>
            <atom:updated>2020-06-24T01:03:46.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_PvhNVR1U3B0iE4sCpUm8Q.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@bongkarn-thanyakij-683719?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">bongkarn thanyakij</a> from <a href="https://www.pexels.com/photo/macbook-pro-on-white-table-3787903/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>It has been a few months since we have started working from home due to Covid-19. Here are my learnings and reflections on how to make it effective at a team level.</p><h4>1. Keep the routine</h4><p>Make sure that you keep the same routines or close to as much as possible when your team is working from home. We humans are creatures of habit. If you are doing things in a certain way at a certain time, it becomes easy. At a time of stress and uncertainty, make things easy for your team.</p><p>Following this rule, the team kept the same time and format for our stand-ups, for our tech talks and group team sessions. We have the same time and routine for our sprint planning, sprint retrospectives, and meetings with clients. We ensured that we did not drop things that are not directly related to project work such as tech talks or technical group meetings. We still maintain our R&amp;D schedule.</p><p>This enabled the team to develop a certain level of normality as they were working in pretty much the same way as they were in the office. It helped us deliver critical projects with tight deadlines without any major impact.</p><h4>2. Have a good work system in place</h4><p>Nothing beats a good work system. If you have established a good work system (The way work comes to your team, the way it is scheduled, and delivered), then you can be rest assured that the team will not drop the ball when things change, even when it is a sudden change.</p><p>We have a very strong work system based on <a href="https://medium.com/being-agile/how-to-improve-scrum-using-kanban-c918068bf5cc">Scrum and Kanban</a> established before the COVID-19 restrictions were enforced. This allowed us to keep working within the defined system pretty much as we were working in the office.</p><h4>3. Communication is the key — make it effective</h4><p>One of the key things that get impacted when a team is working remotely is a drop in team communication. The office chit chats, the kitchen discussions, water cooler gossip, and <a href="https://agile-mercurial.com/2019/01/26/what-is-osmotic-communication/">osmotic communication</a> suddenly stops. It is really impossible to replace the various forms of informal communication that occurs in the workplace in a remote environment, however, there are things you can put in place to bridge the gap.</p><ul><li>Whether you are using Slack, MS Teams, or any other chat tool, create project-specific channels. All the communication about the project should happen through this channel even it is between individuals. This will ensure that all the project team members are aware of the communication and if they need to provide any input they can do that. This goes some way to emulate the osmotic communication that can sometimes play a crucial role in the project success</li><li>Always start project-based online meetings in your team channel so everyone is aware that it is happening. This will enable any interested team member to join the discussion</li><li>Set up round-robin catch-ups between team members so that they can talk about things that are not strictly work-related</li><li>Make use of code reviews between team members and encourage pair programming as a means for enhanced communication</li><li>Allow 5–10 minutes extra in stand-ups to enable a bit of social chit chat before starting</li></ul><h4>4. Keep the fun alive</h4><p>Most people miss the social aspect of working in an office. The Friday night drinks, team events are not possible while working remotely, especially during a pandemic. Ensure that you set up regular online social events. Make use of online games, themed online meetings, and have them regularly. Keeping the fun alive is key to boosting moral and team participation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*tL44iq2cFiFJxO-Nqykpwg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*Llhq4Um2MSuRijgMBPvHSA.png" /></figure><h4>5. Leaders / Keep or start 1–1 with your team</h4><p>If you are in a leadership position, make sure that you keep or start 1–1 with your team members on a regular basis. It is critical in times of stress and working remotely. In an agile environment, the team has a high level of collaboration with standups, design meetings, sprint planning, reviews, and retros. In all that collaboration, it is easy to forget the importance of a 1–1 meeting.</p><p>Use a 1–1 meeting to ask how an individual team member is doing, and how you can assist them. How is their personal development is progressing, and are there any issues? Ensure that you remove any impediments that have whether it is equipment or process improvement. This will go a long way for overall team morale and commitment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a1deb6be8f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/being-agile/5-things-i-have-learned-about-effective-remote-teamwork-during-covid-19-8a1deb6be8f6">5 things I have learned about effective remote teamwork during Covid-19</a> was originally published in <a href="https://medium.com/being-agile">being-agile</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>