<?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[everydayAgile // Engineering Agile Culture - Medium]]></title>
        <description><![CDATA[Coaching leaders through agile transformation and change - Medium]]></description>
        <link>https://medium.com/everydayagile?source=rss----fb2196dbe459---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>everydayAgile // Engineering Agile Culture - Medium</title>
            <link>https://medium.com/everydayagile?source=rss----fb2196dbe459---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:15:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/everydayagile" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pandemic Level Agility]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/everydayagile/pandemic-level-agility-7190ffd2081b?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*yUve1e7w-yXR2982" width="6000"></a></p><p class="medium-feed-snippet">When Chaos Leads to Innovation</p><p class="medium-feed-link"><a href="https://medium.com/everydayagile/pandemic-level-agility-7190ffd2081b?source=rss----fb2196dbe459---4">Continue reading on everydayAgile // Engineering Agile Culture »</a></p></div>]]></description>
            <link>https://medium.com/everydayagile/pandemic-level-agility-7190ffd2081b?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/7190ffd2081b</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[chaos-engineering]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[pandemic]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Thu, 20 Aug 2020 13:46:24 GMT</pubDate>
            <atom:updated>2020-08-20T13:46:24.313Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Synthesizing Information in an Agile Environment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/everydayagile/synthesizing-information-in-an-agile-environment-359c091c0d6?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*W5rWbs7sj461NUkc" width="3753"></a></p><p class="medium-feed-snippet">The Art of Information Radiators</p><p class="medium-feed-link"><a href="https://medium.com/everydayagile/synthesizing-information-in-an-agile-environment-359c091c0d6?source=rss----fb2196dbe459---4">Continue reading on everydayAgile // Engineering Agile Culture »</a></p></div>]]></description>
            <link>https://medium.com/everydayagile/synthesizing-information-in-an-agile-environment-359c091c0d6?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/359c091c0d6</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[comprehension]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Mon, 08 Jun 2020 15:00:57 GMT</pubDate>
            <atom:updated>2020-06-08T15:00:57.737Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Active Listening]]></title>
            <link>https://medium.com/@RyanisAgile/active-listening-468af29623f2?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/468af29623f2</guid>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[respect]]></category>
            <category><![CDATA[listening]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 20:21:47 GMT</pubDate>
            <atom:updated>2024-01-09T20:21:51.052Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4zFflr42mBSQI8sCLlV3w.jpeg" /><figcaption>Active Listening</figcaption></figure><h4>Listen, then respond</h4><p>The best leaders I have ever worked with practice active listening. This is a technique used by counselors, coaches, mentors, and of course, leaders to help with resolving conflicts, understanding the underlying issues a person may be experiencing, and convey empathy during the encounter.</p><p>If you’ve ever had a conversation with someone who always interrupts or starts to assume things then this technique may be for you. People will mimic the person they are conversing with. If the conversation start to get heated they will in turn either walk away or contribute to a heated conversation in kind.</p><p>The active listening technique gives you the tools to calmly guide the flow of the communication while being self-aware.</p><p><a href="https://www.mindtools.com/CommSkll/ActiveListening.htm">Learn More</a></p><p>Have a great weekend you awesome people, stay agile</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0H_yh5oyrzukfyUo9EB5gg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=468af29623f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Became a Scrum Master]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/everydayagile/how-i-became-a-scrum-master-9b3cfcf92587?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*HFgkoWiNBVAsZtgu" width="3024"></a></p><p class="medium-feed-snippet">The Continuing Journey to Mastery</p><p class="medium-feed-link"><a href="https://medium.com/everydayagile/how-i-became-a-scrum-master-9b3cfcf92587?source=rss----fb2196dbe459---4">Continue reading on everydayAgile // Engineering Agile Culture »</a></p></div>]]></description>
            <link>https://medium.com/everydayagile/how-i-became-a-scrum-master-9b3cfcf92587?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/9b3cfcf92587</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[journey]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Wed, 08 May 2019 23:11:26 GMT</pubDate>
            <atom:updated>2024-01-09T00:16:44.628Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Facilitating Excellence]]></title>
            <link>https://medium.com/@RyanisAgile/facilitating-excellence-b2fa2968d3e?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/b2fa2968d3e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Tue, 07 May 2019 00:37:05 GMT</pubDate>
            <atom:updated>2024-01-09T20:22:24.848Z</atom:updated>
            <content:encoded><![CDATA[<h4>What Happens When Everyone Starts to “Get It”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0N5eBnjpOEfNkbVt" /><figcaption>Photo by <a href="https://unsplash.com/@austinchan?utm_source=medium&amp;utm_medium=referral">Austin Chan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I remember a specific day working ruthlessly to help a Product Owner get a team’s backlog prioritized. This Product Owner was VERY new to agile thinking and was also very frustrated with the team, tensions were really high. The coaching questions I was asking did not seem to resonate much at first, until I must have said something that made lightbulbs go off.</p><p>The response was almost instant, <em>“so you’re saying its a behavioral thing?” </em>now I was asking questions, not stating the issue was this or that, but still they seemed to hone in on this revelation. These lightbulb moments are where I see the most change occur, as if they have crossed into a new region and can take another step that gets them closer to their goal. This is also most gratifying for a coach to see.</p><p>As a I tried to break down the first principles to this Product Owner, they became instantly enthused by the discovery and were totally bought in, because “Product Owner” was just something they were called when they joined the team, it had no REAL meaning and so this was understood to be the same as “Product Person” and no sense of ownership or entrepreneurialism had been established. The truth is that words have meaning and can be used for good or bad.</p><h3>Unlocking Behavioral Change</h3><p>Not to get too scientific, but behavioral change can be broken down into behaviors and habits.</p><ul><li>A behavior is asserted as something the person is <strong>conscious</strong> of like showing up for the daily scrum even though they believe it is a useless prescribed event.</li><li>A habit is asserted as something the person is <strong>NOT conscious</strong> of like showing up for the daily scrum even though they have it on their calendar.</li></ul><p>So changing the behavior when a person is conscious of it and agrees that it needs to be changed might be the first step in the process (this doesn’t happen overnight, nothing does).</p><p>What about reinforcing this with good habits? I like to reference the experts about habits, like James Clear author of <a href="https://jamesclear.com/habits">Atomic Habits</a>, who breaks good habit building into four main categories: Cue, Craving, Response, Reward.</p><p><a href="https://jamesclear.com/habit-triggers">The 5 Triggers That Make New Habits Stick</a></p><h3>Intuition for Excellence</h3><p>If you’ve ever seen an awesome movie and then watched a really terrible movie you know this feeling, the more you watch movies you start to recognize patterns of what makes the movie great and can also, using your intuition know whether it was great or not.</p><p>The same thing happens when a sports team is scouting for athletic talent, they might use a few statistics and data, they will also use the recommendations of others, but ultimately it comes down to their own intuition because they are accountable for making the decision to give the athlete a trial.</p><p>An agile coach who has coached a wide variety of teams knows what excellence looks like and can recognize patterns in team and organizational formation. The earlier this is done the better, because a team or an organization can go way off track without the proper rails and safety mechanisms.</p><h3>Notes on Facilitation</h3><p>As a rebellious teenager, I have never really liked the word <strong>maturity</strong>, it has a negative connotation and when used to describe an organization or a team of professionals it might leave a bad taste telling an organization or a team that they are just not mature.</p><p>I really like the word <strong>journey</strong>, this is compelling and positive in nature and sets the conversations up around where someone is going. The best facilitators of excellence know that you must tread lightly as a guide and not just point at the map, because one mis-step and everyone could get lost on the journey.</p><p><strong>You must be the compass</strong> so that they look to you for guidance and reassurance that they are on the right path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lfWnjZsZB6dbSC8T" /><figcaption>Photo by <a href="https://unsplash.com/@heidi_sandstrom?utm_source=medium&amp;utm_medium=referral">Heidi Sandstrom.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Maintenance Mode</strong></h3><p>When a team is self organizing, does that mean your job is done? No, it’s really just beginning, here’s why.</p><p>An organization needs to grow and a side effect of growth is more people joining the organization. The team members who are doing awesome might feel the growth coming and jump ship, others will see it as an opportunity.</p><blockquote>Where there is growth, there is change</blockquote><p>Maintenance mode, in my opinion does not exist because you should be always striving for better and never settle. Whatever was done in the past is in the past and all we have the present and the future.</p><p>My point is that facilitating excellence is about being consciously aware of behavioral change, intuition for excellence, being a compass vs a map, and staying out of maintenance mode.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2fa2968d3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Adapt to Your Environment]]></title>
            <link>https://medium.com/@RyanisAgile/how-to-adapt-to-your-environment-39357455a698?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/39357455a698</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 18:09:52 GMT</pubDate>
            <atom:updated>2024-01-09T20:22:41.991Z</atom:updated>
            <content:encoded><![CDATA[<h4>When Change Happens, How do you Respond?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zOc8d4mfaGTOZmDl" /><figcaption>Photo by <a href="https://unsplash.com/@vishu_gowda?utm_source=medium&amp;utm_medium=referral">Vishu Gowda</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Adaptation is one of the pillars of empiricism, the underlying theory behind Scrum. The concept of adapting is simple to understand but everyone struggles with it, why? Adapting to a new environment is always a <strong><em>push</em></strong> and not a <strong><em>pull</em></strong>, in other words you’re not pulling yourself into a new environment but rather some change has caused this to happen.</p><p>When change is <strong><em>pushed</em></strong> or dictated there are really only two options, react to the change which can have negative effects or accept (respond) and welcome the change. The <a href="https://www.agilemanifesto.org/">Manifesto for Agile Software Development</a> has a value and a principle that says to welcome change. The principle also says agile processes harness change (iterative and incremental).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*yKIWrQ58oTieB4tA5j6JQg.png" /><figcaption>3rd Principle of the Manifesto for Agile Software Development</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*vwiZ53Le-H0UPalMJET_Gg.png" /><figcaption>4th Value of the Manifesto for Agile Software Development</figcaption></figure><p>Why would the signatories of the manifesto include the word <strong><em>change</em></strong> in both the values and the principles? Seems like they felt it needed to be emphasized thoroughly. This is where it gets difficult, people can easily understand what is described here, but still struggle in this regard. The theory is good at identifying the need, but leaves the actions and response to the practitioner because <em>everyones environment is different</em>.</p><h3>Why Change?</h3><blockquote><strong><em>“Change is a certainty of life, things are going to change and the faster you come to this realization the better”.</em></strong></blockquote><h3>Three steps to successful adaption</h3><h3>Step 1. Break things down by asking questions</h3><p>Agile talks about the processes that help us harness change, which are to approach things <strong><em>iteratively and incrementally</em></strong>. This means we must first look at the change and start asking the right questions that will break this change down into consumable increments and place those into our iteration.</p><p>Ask questions like;</p><ul><li>What are the impacts of this change?</li><li>Why is this change needed?</li><li>What is the effort, relative to everything else?</li><li>When could we start?</li></ul><h4>What is Iteration?</h4><p><strong>Iteration</strong> is the repetition of a process in order to generate a (possibly unbounded) sequence of outcomes. The sequence will approach some end point or end value. Each repetition of the process is a single iteration, and the outcome of each iteration is then the starting point of the next iteration.</p><h4>What is Incremental?</h4><p>of, relating to, being, or occurring in especially small <a href="https://www.merriam-webster.com/dictionary/increments">increments</a></p><h3>Step 2. Make the change, understand values</h3><p>As we discussed, change is both hard and a certainty, this is where you need to express the Scrum values of <em>Courage</em>, <em>Commitment</em>, <em>Respect</em>, <em>Focus</em>, and <em>Openness</em> to be effective. How these are expressed is up to you and the environment that you’re in.</p><p>For instance, it might take courage to keep asking questions and actually make the change. You will need to be committed to the change. The values are there to aid in your journey through adapting because a person’s principles or standards of behavior or a judgment of what is important in life are directly related to how you process change.</p><h3>Step 3. Measure the outcome, create a pain scale</h3><p>As we take a journey of adapting to our environment, we need to retrospect and measure the outcome. A good way to measure the outcome of adapting to change is by creating a pain scale. How painful was the change? Looking back on many changes in my career, some change have been very painful and others not so much, I can reflect on what made those changes so painful and identify what caused so much pain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BD4-wpSXI_N0ApGW" /><figcaption>Photo by <a href="https://unsplash.com/@franckinjapan?utm_source=medium&amp;utm_medium=referral">Franck V.</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Conclusion</h3><p>Since humans are always susceptible to change, we need some tools that help us with this, I believe these steps can be a useful, light-weight, and easily integrated into your daily lives with the intention of helping others who feel the same pain and struggle with many of the same affects change has on us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39357455a698" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of a Working Agreement]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@RyanisAgile/the-power-of-a-working-agreement-912befb914d1?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*8Yom60axa7T7IvOH" width="4000"></a></p><p class="medium-feed-snippet">How a Team Governs Themselves</p><p class="medium-feed-link"><a href="https://medium.com/@RyanisAgile/the-power-of-a-working-agreement-912befb914d1?source=rss----fb2196dbe459---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@RyanisAgile/the-power-of-a-working-agreement-912befb914d1?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/912befb914d1</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Fri, 28 Dec 2018 18:34:29 GMT</pubDate>
            <atom:updated>2024-01-09T20:23:02.252Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Rise of the Chief Agile Officer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@RyanisAgile/rise-of-the-chief-agile-officer-e73148477604?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*AISVPOZNacZ_elos" width="4000"></a></p><p class="medium-feed-snippet">Bringing Transformation In-House</p><p class="medium-feed-link"><a href="https://medium.com/@RyanisAgile/rise-of-the-chief-agile-officer-e73148477604?source=rss----fb2196dbe459---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@RyanisAgile/rise-of-the-chief-agile-officer-e73148477604?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/e73148477604</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 16:31:40 GMT</pubDate>
            <atom:updated>2024-01-09T20:23:17.592Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Never Stop Continuously….]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@RyanisAgile/never-stop-continuously-3a3d16a376ac?source=rss----fb2196dbe459---4"><img src="https://cdn-images-1.medium.com/max/2600/0*Ab01w7YoP-yXgORP" width="4030"></a></p><p class="medium-feed-snippet">Improving, Delivering, Challenging, Caring, [Insert Here]</p><p class="medium-feed-link"><a href="https://medium.com/@RyanisAgile/never-stop-continuously-3a3d16a376ac?source=rss----fb2196dbe459---4">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@RyanisAgile/never-stop-continuously-3a3d16a376ac?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/3a3d16a376ac</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[running]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Sat, 10 Nov 2018 18:31:38 GMT</pubDate>
            <atom:updated>2024-01-09T20:23:41.544Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[This week I started focusing on getting my Instagram account updated.]]></title>
            <link>https://medium.com/everydayagile/this-week-i-started-focusing-on-getting-my-instagram-account-updated-3b98eeeb00a5?source=rss----fb2196dbe459---4</link>
            <guid isPermaLink="false">https://medium.com/p/3b98eeeb00a5</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ryan]]></dc:creator>
            <pubDate>Fri, 09 Nov 2018 18:16:10 GMT</pubDate>
            <atom:updated>2018-11-09T18:16:09.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*DsFivliVLFuog56_SpH-0w.png" /></figure><p>This week I started focusing on getting my Instagram account updated. I decided to add a few highlight categories including Music, Awesome (things that are awesome), Learning (things I am learning), and Coaching (things related to agile coaching).</p><h4>Follow me <a href="https://www.instagram.com/realryankey/">here</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*MBKUgOlD5bPjNDlBaK4Wog.png" /><figcaption>Instagram Logo</figcaption></figure><p>My next task is start using the new IGTV and get some videos in the works.</p><h4>Recent stories:</h4><p><a href="https://everydayagile.com/the-ultimate-self-organizing-team-90b680d3c200">The Ultimate Self Organizing Team</a></p><p><a href="https://everydayagile.com/making-time-for-continuous-improvement-2cbab2510c11">Making Time for Continuous Improvement</a></p><p><a href="https://everydayagile.com/why-professionals-follow-the-rules-178da62e4e1">Why Professionals Follow the Rules</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b98eeeb00a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/everydayagile/this-week-i-started-focusing-on-getting-my-instagram-account-updated-3b98eeeb00a5">This week I started focusing on getting my Instagram account updated.</a> was originally published in <a href="https://medium.com/everydayagile">everydayAgile // Engineering Agile Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>