<?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 Rory Dwyer on Medium]]></title>
        <description><![CDATA[Stories by Rory Dwyer on Medium]]></description>
        <link>https://medium.com/@rory.dwyer?source=rss-64c5a8db048c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ENWpI0baZ3rt8vCg.jpg</url>
            <title>Stories by Rory Dwyer on Medium</title>
            <link>https://medium.com/@rory.dwyer?source=rss-64c5a8db048c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:07:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rory.dwyer/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[4 Tips for Better Remote Meetings]]></title>
            <link>https://medium.com/momenton/4-tips-for-better-remote-meetings-1ca1af970d27?source=rss-64c5a8db048c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ca1af970d27</guid>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Rory Dwyer]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 00:53:54 GMT</pubDate>
            <atom:updated>2021-02-15T00:53:54.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWwS_KrTXtmMadzkKiz1Lg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cwmonty?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chris Montgomery</a> on <a href="https://unsplash.com/@cwmonty?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m sure many meeting facilitators and scrum masters out there will agree — the last year has taught us that remote meetings can be a drag, and that it can be a real challenge to have consistent engagement in your calls. Have you ever been the only one with a camera on, staring at your reflection, talking seemingly into the abyss, questioning where it all went wrong?</p><p>Well, I have. So over the last few months, I’ve tried to reflect on this challenge and find ways to improve. There’s still lots to learn, but my team and I have seen improvements in this area. So I wanted to share some of our learnings and I hope that you find them helpful.</p><h3>1 — Be Human</h3><p>When working remotely, we miss out on so much human interaction that we normally get in the workplace. Aside from the research showing how important human interaction is for our health, we are also missing opportunities to connect and grow as a team. These opportunities to get to know each other could be in the form of simple office banter, asking about favourite hobbies over a coffee, or even confiding in a colleague and asking for support. It’s no surprise that these things are more difficult through an instant message, email or call, where there’s limited or no body language to work with.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26BRuo6sLetdllPAQ%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26BRuo6sLetdllPAQ%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F26BRuo6sLetdllPAQ%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="303" frameborder="0" scrolling="no"><a href="https://medium.com/media/92f678979f0babd05c503520b4b60d2c/href">https://medium.com/media/92f678979f0babd05c503520b4b60d2c/href</a></iframe><p>With this in mind, we need to be mindful we don’t become robots jumping from one meeting or task to the next. Allow for some time in your remote meetings to have more human interactions. How this plays out will differ based on your team’s dynamics and size, so don’t force something that doesn’t fit. Some examples could be:</p><ul><li>Take 5 minutes at the start or end of the call for general chit-chat. This is especially great for meetings on a Monday or Friday where people have exciting weekend plans to talk about.</li><li>If you run daily stand-ups, take turns telling a joke or riddle at the end of each call. Even the cringey dad-jokes will get a chuckle.</li><li>There’s always the pet person in the team. They will be happy to show off their furry loved ones to the team.</li></ul><p>Whatever the approach, try to involve everyone and have fun with it. Fun = engaging. And if some days nobody wants to chat, don’t take it personally.</p><p>Even with this tip in mind, engagement can still be difficult if you’re the only one making an effort. Which leads me to point 2…</p><h3>2 — Get Feedback — and Give Your Own</h3><p>If you’re making an effort to engage and it feels like the rest of the team isn’t, this can lead to frustration and resentment. If this is the case, or if your meetings just aren’t as good as you’d like them to be, it’s great to raise this during the <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">Scrum Retrospective</a> (or equivalent session in the framework you use). Remember to raise the issue with an open-mind, without directing blame, and be prepared to receive feedback yourself.</p><p>As an example, saying “I feel that our scrum ceremonies aren’t collaborative enough” instead of “You all ignore me in backlog refinement!” will set you up for a more positive conversation. In this way, you’re asking the whole team to collaboratively inspect what is going wrong with the meetings. This may lead to brainstorming ideas that the whole team, including you, could implement. Perhaps you’ll find out that meetings often meander away from the agenda, which leads people to become disconnected. That may prompt you to think about timeboxing and other techniques. Keep a <a href="https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/">growth mindset</a>. Easy.</p><h3>3 — Be Pointed (When Necessary)</h3><p>Often as a facilitator, you’ll find yourself asking an open question to the group. It’s great when someone immediately jumps in with a response to keep the conversation going, but that doesn’t always happen. There are two tactics to try and keep things going in this case.</p><p><strong>First option</strong>: Let the awkward silence roll…</p><p>Okay, long silences can be hard for some of us. But often as facilitators, we try too hard to force the conversation forward. It’s okay to let it breathe, as the audience digests the information and considers a response. As you feel the urge to jump in, hold off a little longer. You might even find that your hastiness is interrupting the flow. Maybe your team has more analytical personality types and they like to take their time before replying.</p><p><strong>Second option</strong>: If the awkward silence technique isn’t working, consider politely prompting someone by name. If the topic is specialised, maybe you’ll want to prompt someone who is the subject matter expert in that area. Otherwise, just randomly pull a name from the list and ask them. Seriously.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohhwiunVgYqfVYVEs%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohhwiunVgYqfVYVEs%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3ohhwiunVgYqfVYVEs%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="217" frameborder="0" scrolling="no"><a href="https://medium.com/media/14591e89b4a15fcaca95e4c225704a14/href">https://medium.com/media/14591e89b4a15fcaca95e4c225704a14/href</a></iframe><p>Try not to constantly single out the same people each time, as this could lead to other problems in the team. Your goal is for everyone to be collaborating.</p><h3>4 — Share Facilitation</h3><p>This is one of my personal favourites. What better way to build up engagement than to have different team members facilitate meetings? There are a few great benefits to this; other team members get to cross-skill, the usual facilitator gets to see new ideas from a fresh perspective, and the whole team increases their empathy for some of the challenges faced by a facilitator. I’ve personally found that once someone starts facilitating they become a more engaged audience member later. Empathy is powerful.</p><p>I would usually recommend doing this with a less “daunting” meeting, such as a Retrospective which can be run in <a href="https://www.google.com/search?q=scrum+retro+ideas">so many different ways</a>. In one of my teams right now, we’re taking turns running the Retro and I’m being exposed to many great ideas and tools. It’s also just nice participating from the “audience side” for a change to see what works and what doesn’t.</p><p>There’s so many more techniques and strategies out there, so keep digging. And if you’re really struggling with your remote meetings and want some quick wins on the board, I’d recommend starting with tips 2 &amp; 4!</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ca1af970d27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/4-tips-for-better-remote-meetings-1ca1af970d27">4 Tips for Better Remote Meetings</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jira vs. GitHub Issue Tracking]]></title>
            <link>https://medium.com/momenton/jira-vs-github-issue-tracking-4cdf3bdd1437?source=rss-64c5a8db048c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cdf3bdd1437</guid>
            <dc:creator><![CDATA[Rory Dwyer]]></dc:creator>
            <pubDate>Tue, 06 Oct 2020 01:22:42 GMT</pubDate>
            <atom:updated>2020-10-06T01:22:42.650Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jira vs GitHub Issue Tracking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4CeBMq8rS0U1Ud4twlcq2A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Headway</a> on <a href="https://unsplash.com/s/photos/github?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I recently joined an established software development team in a large enterprise who exclusively used GitHub for issue tracking. From a developers perspective, it made sense. GitHub becomes your one-stop shop for tracking, version control and source code management. <br>If it ain’t broke, why fix it?</p><p>The Product Owner and I talked about backlog visibility and found this was one of the major challenges with the current setup. As the team maintains a number of services spread across multiple GitHub repositories, there was no single board to view and refine a combined backlog. Another challenge was that there were no estimations or story points, with more of a gut-feel approach on what could be completed in any given sprint.</p><p>After a few <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">retros</a>, we noticed some common themes occurring. So we decided to do an agile baseline health-check to further validate where we could improve. We individually scored our team on various agile fundamentals then had a big retro to review the results. Some of the common themes we struggled with were, in part, directly related to those limitations in our issue tracking mentioned earlier. Clarity on the product vision and backlog management was an issue, which a single backlog view could improve. Sustainable pace was an issue, which estimations and understanding our velocity could help with. The quality of user stories was also an opportunity for us to grow, which would require discipline — but perhaps the right tool could accelerate the process!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*wNIJ3yEngod3DLlV.jpg" /><figcaption>We projected our agile health to improve by at least 40 stonks with the right issue tracking tool</figcaption></figure><p>For the record, our target areas could be tackled in lots of ways! But for this article, we’ll focus on <strong>issue tracking and the backlog</strong>.</p><h3>Backlog</h3><p>Out of the box, Github’s <a href="https://docs.github.com/en/github/managing-your-work-on-github/about-project-boards">project board</a> is essentially a kanban that can be setup quickly and easily. It has some automation available around tickets being moved between status columns which is handy, but it’s not really a backlog view. For a more traditional backlog, you could potentially view each repository’s issue list separately, but that wasn’t feasible for us with 15–20 repositories — imagine backlog refinement! 😱<br>The only way to combine all of them (in out of the box GitHub) is to use a project board.</p><p>Aside from not really being a traditional backlog offering, a limitation of the project board is that it is not suited to larger projects and teams with a higher number of issues. In those environments, you may not want to use automation to add all new issues to the board, or it will get cluttered quickly and lose clarity. Therefore, you’ll be adding cards manually using the Add Cards pane. This offers no drop-down menus or auto-fills for simplified searching, so if you’re running a lot of repositories and issues this becomes a bit daunting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtWEPULpkjW_eR1zHYdcuA.png" /><figcaption>Easy to setup, but has it’s limits</figcaption></figure><p>Another limitation of GitHub’s project boards is that a maximum of twenty-five repositories can be linked to one board. For most teams this isn’t a problem. However, it’s worth considering how your team and product might grow over time when making a choice.</p><p>Whilst I’m sure there are many ways to customise your GitHub, our team wanted a light-touch setup. Those who have worked in large enterprises will know the challenges in customising your operational tooling, with approvals and dependencies likely to slow down any significant change.</p><p>At least it’s super easy to get rolling with.</p><p>Alternatively, Jira <em>could </em>take slightly longer for that initial setup but may offer more value overall.</p><p>We decided to go with Jira for a few reasons, one of them being the backlog view. We added <a href="https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/">quick filters</a> to allow the PO to switch between the combined backlog view of all issues or to view issues only for a particular service. While at the same time, developers could bookmark the Jira board with the quick filter(s) for their current workstream already selected — saving them from the noise of unrelated issues.</p><p>The backlog view in Jira allows us to drag and drop issues between sprints and backlog easily. We can drag priority tickets to the top of the backlog to visualise and plan how the next sprints will look, ensuring our refinement ceremonies are more meaningful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*286NCRkVFROVoEvp" /><figcaption>Clean and crisp backlog</figcaption></figure><h3>Issue Fields</h3><p>Our team had identified two key problems relating to the contents of issues — a lack of estimations and user story quality being a little “lacking”. In GitHub, there’s no built-in field to capture effort. How could we plan for a sprint if we couldn’t quantify the required work in some way? Well, Jira not only had a built-in field to capture story points but also shows this against each issue in the backlog. It also displays totals above the active sprint of story points to do, in progress and done. Use of story points can be enhanced with some add-ons for burndown and velocity charts, which in our case were already available in our Jira environment. Within 3–4 sprints, we started getting some consistency and understanding the velocity we could achieve in each sprint on average. This has brought more confidence to our sprint planning and helps improve toward a sustainable pace for the team.</p><p>On the second problem of user story quality; as touched on earlier this would require discipline from the team, but could also be helped with by the right tool. By simply enabling the Acceptance Criteria field in our Stories in Jira and making it mandatory, we were reminding ourselves to meet some minimum requirements on all of our Stories. This was a basic example of prompting the user, but plenty of Jira’s built-in fields could be used to guide users in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*3oq6RzLYb2HH1mpf" /><figcaption>Great job, me!</figcaption></figure><p>Another benefit with issue content was using Epics to group Story issue types. Where previously in GitHub, we were trying to loosely group related tasks using combinations of labels or milestones, the Epic issue type allowed us to create a high level parent issue with some information around the overall goal of that feature or enhancement. This is far superior to a GitHub label, for example, as it allows information such as acceptance criteria or a business-level user story, to be held at the top level Epic — as well as allowing the Epic itself to transition through a workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*ziREJ5n6HrX1tN8D" /><figcaption>Epics are awesome. And epic!</figcaption></figure><h3>Migrating from GitHub to Jira</h3><p>Having decided as a team to give Jira a try, we started migrating GitHub tickets to Jira in increments. Fortunately, we were able to use GitHub’s API for this instead of writing out hundreds of issues manually. We used the list-repository-issues call (<a href="https://developer.github.com/v3/issues/#list-repository-issues">API docs</a> / <a href="https://developer.github.com/enterprise/2.21/v3/issues/#list-repository-issues">enterprise API docs</a>) to extract all open issues in a particular repository, then used an open source tool to convert JSON to CSV, then tidied up the CSV into a format we could <a href="https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html">import into Jira</a>.</p><p>A limitation is that the issue comments don’t come back in that API response; instead you’ll need to make a second API call for each issue to another endpoint for comments. As our comments were low volume and not worth the extra effort, we simplified the approach and instead made the CSV template a <em>tiny </em>bit fancy by concatenating the original GitHub issue link into the new Jira description to be imported. That way if anyone wanted to check the original link for comments it was right there in each Jira ticket.</p><h3>Summary</h3><p>When would GitHub work best for issue tracking? In my opinion, it could work in smaller development or support teams who only need a simple kanban setup and have a lower volume of issues. Perhaps it could also work for high-performing, well-established development teams with other methods and tools for estimations, reporting, backlog refinement and visualisation!</p><p>When would Jira work best for issue tracking? From my experience, when directly comparing to GitHub, Jira gets the chocolates in most categories. Especially in large enterprises where transparency and reporting are fundamental. Yes, it can take longer for initial setup depending on your requirements, such as for more complex workflows. However, if you need a lightweight setup there are built-in workflows.</p><p>One downside is that you need some customisation to link Jira issues directly to GitHub pull requests, which developers may bemoan when comparing to GitHub.</p><p>Hopefully this information helps as you consider the needs of your team. Good luck!</p><p><em>I have no affiliation with Jira or GitHub. I’m just a nerd for organisation.</em></p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cdf3bdd1437" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/jira-vs-github-issue-tracking-4cdf3bdd1437">Jira vs. GitHub Issue Tracking</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>