<?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 Justin Kotze on Medium]]></title>
        <description><![CDATA[Stories by Justin Kotze on Medium]]></description>
        <link>https://medium.com/@jstnktz?source=rss-2a80e9ba23d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RXVO2IfpKJkw0JaIBW7wDA.jpeg</url>
            <title>Stories by Justin Kotze on Medium</title>
            <link>https://medium.com/@jstnktz?source=rss-2a80e9ba23d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:39:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jstnktz/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[Too many things in progress? Visualise, prioritise & delay]]></title>
            <link>https://medium.com/@jstnktz/too-many-things-in-progress-visualise-prioritise-delay-7bd505ac7cb1?source=rss-2a80e9ba23d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd505ac7cb1</guid>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Justin Kotze]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 13:01:42 GMT</pubDate>
            <atom:updated>2018-09-18T13:01:42.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I5o1v66RqJLkZKWT-JCFxw.jpeg" /><figcaption>tl;dr</figcaption></figure><p>Sometimes, with the best intentions, teams find themselves in a state where too many things are in progress. Some of the work items visible on a tracking board, and some items not exactly visible to everyone.</p><p>Here is a simple 18 step facilitation guide to help you.</p><blockquote>1. Get the team in a room together.<br>2. Set the stage with <a href="http://retrospectivewiki.org/index.php?title=The_Prime_Directive">the prime directive</a> — “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”<br>3. Ask them to write up everything regardless of where it is tracked that are in flight right now.<br>4. One by one introduce each item and add it to a board<br>5. Add a value of 1–5 to each item to visualize how complete it is. 1 — just started, 5 — just about done.<br>6. Add an exclamation sign to the items that are urgent<br>7. Find the largest item on the board mark it with an L for large. Find the smallest item and mark it with an S for small. Ask the team for an item that fits somewhere in the middle of the two items marked. Add an M for medium to that item.<br>8. Add a t-shirt size relative to the sizing exercise in step 6 to all the items without sizes. S, M or L.<br>9. Draw a one quadrant graph. On the Y-axis add complete scale. 1–5 from step 4. On the X-axis add the t-shirt size scale. S M L from step 7.<br>10. Add all of the items to the correct spaces on your graph.<br>11. Select urgent, almost done items, from small to large<br>12. Now prioritize with by taking one item, and asking if it is more important to work on this item than the next item. Sort this linearly.<br>13. Take the highest priority item and ask the team how confident they are that they could finish this item by the end of their iteration(or a date that makes sense in your context). If they can’t finish the very highest priority item in the given timeframe, break the item down further into smaller items, or extend the timeframe.<br>14. Keep moving down the priorities until the team doesn’t have high confidence to complete things.<br>15. Now add the items that’s left on the prioritized list and items that’s left on the graph to a delayed state.<br>16. Reach agreement with the team to only work on the items they agreed to that they can finish with high confidence.<br>17. Communicate to stakeholders that all the items in the delayed state are delayed until the end of your iteration.<br>18. Breath</blockquote><p>Complete each step before starting the next step.</p><h4>How have you gone about solving this problem?</h4><p>Let me know if you tried this on <a href="https://twitter.com/the_jus">twitter</a> or <a href="https://www.linkedin.com/in/justinkotze/">linkedin</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd505ac7cb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Songs & Stories]]></title>
            <link>https://medium.com/@jstnktz/songs-stories-5e606ac7fda9?source=rss-2a80e9ba23d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e606ac7fda9</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Justin Kotze]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 07:55:27 GMT</pubDate>
            <atom:updated>2018-09-06T07:55:27.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljXt5WC0-Qu1i00ZCKOvGg.jpeg" /></figure><h4>Play a song, tell a story to each other &amp; eat together.</h4><p>Take a second and listen to <a href="https://open.spotify.com/track/5cAwcy1JKv4sKd9yHMKL36?si=mpZ07I3kQ_WPVGXjC1Kr9A">this</a> song. This is a song that reminds me of <a href="https://en.wikipedia.org/wiki/Cape_Town">home</a>. I listen to this when I’m feeling nostalgic. It makes me think of all the <a href="https://en.wikipedia.org/wiki/Regional_variations_of_barbecue#South_Africa">braais</a> I hosted at my place. Time stood still during those times. The laughs, the music, the food, and the company.</p><p>Play a song and tell a story to each other. This, in short, is how songs and stories work.</p><p>It is useful to build familiarity with each other in teams. I have used it in many different scenarios. These include:<br>- Team kickoffs.<br>- On a regular once a month cadence.<br>- Leadership team lunches.<br>- Welcoming new team members in a team.</p><p>Facilitating Songs and Stories have given me unexpected insights into the teams that I support. An example of an unexpected learning was that that the one person on the team does Salsa dancing. They shared a song that they dance to. This surprised the whole team. Another story comes to mind when someone played a <a href="https://open.spotify.com/track/6vdwNUqYE423G3t9iQFYZZ?si=trxgbH0fRX6QJE9EVLDKtg">Dimmu Borgir</a> song and explain that they listen to that song when walking their dog late at night in the woods. Someone also played a Spanish dance song and told the story how they learned dancing from very young. They even got up and danced to the song showing the team their moves.</p><p>It’s such a simple activity yet so powerful.</p><p>Want to try it yourself?</p><blockquote><strong>Here is what you need:</strong><br>1. People<br>2. Music<br>3. Food makes it better</blockquote><blockquote><strong>How to do it in 5 easy to follow steps:</strong><br>1. Bring food.<br>2. Set up a a device where people can search and play music on a speaker<br>3. Give the following instructions:<br>We are going to play a song and tell a story about it.<br>We you have the device, search for your song and play it. <br>You can either turn down the volume and talk over it like a radio DJ. <br>You can play the entire song and talk after it. <br>You can play a small snippet and then talk or just introduce it and play it. <br>It is up to the player to decide how long they want to have people listen to the song and how long they want to talk<br>In order to get the device you need to ask for it. If you do not want to play a song it’s completely fine.<br>The story you tell is about why you chose to share the song that you played.<br>It could be a memory, a song stuck in your head, your favourite song, there are no constraints really<br>4. To start play a song yourself and share a story.<br>5. Allow for conversation to happen when it does.</blockquote><p>As a bonus try to capture all of the songs and share it as a playlist to the team after the exercise.</p><p><strong>A very short adaptation of this could be used as a check in or icebreaker exercise</strong>. <br>1. Ask people to take out their phones.<br>2. Give them 1 minute to find a song that captures their mood in the context of what you are meeting about.<br>3. Ask each person to play a snippet of the song on their phone and talk about why they chose the song.</p><p><a href="https://www.linkedin.com/in/benjiportwin/">Benji</a> introduced me to this exercise at the last <a href="https://www.linkedin.com/pulse/10-reasons-spotifys-agile-coach-unconference-rocked-benji-portwin/">Spotify agile coach unconference</a>. Thanks again Benji.</p><p>I’d love to hear from you if you try this. Ping me on <a href="https://twitter.com/the_jus">twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e606ac7fda9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making your favourite pastime at the office even better.]]></title>
            <link>https://medium.com/@jstnktz/making-your-favourite-pastime-at-the-office-even-better-a22fab491bb9?source=rss-2a80e9ba23d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a22fab491bb9</guid>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Justin Kotze]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 13:27:09 GMT</pubDate>
            <atom:updated>2018-09-04T14:02:47.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVykNFbs-1dz6_5IjnZLyw.jpeg" /><figcaption>tl;dr</figcaption></figure><h4>You are likely also thinking about meetings, right?</h4><p>Let’s join a meeting with Charlie and their team. Here the are having a sync meeting to help them track and keep focus on a large project.</p><p>“<em>I think this is done</em>”, Charlie’s eyebrows go down and closer to each other.<br>“<em>How about the next item</em>” Sam scrolls to the next item.<br>“<em>Robin was out last week, I’ll check with them later. I think this is still relevant</em>” Alex quickly answers.<br>“<em>Hopefully yes. Mark this as red, at risk. I’ll follow up with Robin when I see them.</em>”, Jay says rapidly <br>“<em>Ashley, The next one has your name on it and it looks like it’s been in progress for the last 3 weeks.</em>”<br>Sam looks around the room and doesn’t spot Ashley.<br>“<em>They are still on holiday and it doesn’t look like they didn’t send a representative for their team. Ashley is back next week though. Ah, also I need to leave at half-past I have another meeting booked.</em>”, Alex adds<br>“<em>What about this, we said last week this should be solved.</em>”<br>“<em>Yeah, Morgan isn’t in today. I don’t know.</em>”<br>“<em>We are out of time so see you all next week.</em>”, Sam closes their laptop and runs to the next meeting</p><p>Sound familiar?</p><p>We have all been in meetings like this. Meetings like these may have great reasons why they exist. They could be trying to address many things. Charlies’s team aims to accomplish the following through this weekly sync meeting:</p><p>- Update of the project tracking tool<br>- Identify and solve dependencies<br>- Talk about risks<br>- Keep momentum on the project<br>- Assisting in keeping people aligned<br>- Know who is doing what</p><p>The current format doesn’t accomplish all that it sets out to accomplish. Namely the Above list. It only allows for the very first bullet to be addressed. The rest of the bullets doesn’t get addressed.</p><p>The current meeting format is as follows:</p><blockquote><strong>Charlie and their team’s current meeting format:</strong><br>Walk through the project tool and update.</blockquote><p>I am pretty sure if we ask the team how they would rate the meeting in terms of its effectiveness they would rate it low. The entire current meeting is spent updating a tool together. A lot of time are spend in Charlie’s meeting talking about unimportant things. I’d risk saying that by spending time talking about whether Ashley may or may not have been be doing something for the past 3 weeks aren’t really that important if no one cares enough to follow up outside of this meeting. I’d like to see people take responsibility of keeping the tool they use up to date outside of this meeting. This could give them the opportunity to talk about important risks rather than doing admin in a meeting.</p><p>This got me wondering. What could happen if we change the format a bit? I’m thinking about a format that tries to address all of the items that the team needs to accomplish in the meeting.</p><p>I had the opportunity to share these thoughts with Charlie’s team. They agreed that they could get get more out of this time spent together. I worked a little bit with the team to come up with the following format for their sync meetings.</p><p>The following is a format that’s been working well for me in some of these sync meetings.</p><blockquote><strong>Charlie and their team’s new meeting format:</strong><br>Start with the agenda<br>Remind people of the purpose of the meeting:<br>- It is a meeting to about risks identified in the project tracker tool that is updated outside of this meeting.<br>- It helps us keep momentum on the project.<br>- It assists in keeping people aligned.<br>- It helps us to hear what’s on each other’s mind.<br>- It give us time to talk about topics.<br>- It gives us an opportunity to solve small issues right on the spot.<br>- Identify actions that need to happen outside of the meeting.<br>Check that you have the right people in the room<br>Invite anyone to ask questions at any time in the meeting. Be mindful of time. If an issue comes up that can’t be solved within a couple of minutes, take an action to solve it outside of this sync meeting.<br>Start with a round of questions where each person answers the following:<br>1. Something I need to tell you<br>2. Something I need to know<br>3. What is keeping me up at night in the context of this project<br>Add Topics<br>Discuss topics<br>End with a round of actions or intentions by answering the following <br>What actions am I taking out of this meeting?</blockquote><p>Now I want to invite you to listen in to a part of this week’s meeting with the new format:</p><p>“<strong><em>Something I need to tell the group</em></strong><em>: We finally got feedback from the provider. </em><strong><em>Something I need to know</em></strong><em>: I heard Charlie talk about a new delivery and that was news to me. Is there something I need to do? </em><strong><em>What’s keeping me up at night?</em></strong><em> I worry that we still don’t have live customers using our product</em>” Sam concludes<br>“<strong><em>Something I need to tell the group</em></strong><em>: Nothing new. </em><strong><em>Something I need to know</em></strong><em>: I heard something similar from Charlie. I am also not quite sure. Let’s add that as a topic to the board to discuss? </em><strong><em>What’s keeping me up at night?</em></strong><em> I saw on the tracking board that the team’s deliveries are at risk and I don’t feel like we are setting them up for success</em>”<br>“<em>I added that as a topic</em>” Robin interrupts Alex. “<em>I saw the same thing</em>”</p><p>After the round of questions, the team discusses topics. A couple of topics goes into too much detail and the people involved take an action to solve it outside of the meeting. Some topics get solved during the meeting. It turns out Charlie’s team was working on something that was a lower priority. Luckily they caught it in time and Charlie’s team seems to be more aligned again.</p><p>The meeting ends with a round of actions taken from this meeting. The team goes around the room in the same order they started. Sam first: “<strong><em>What actions am I taking out of this meeting?</em></strong><em> Alex and I need to update the TPS impact report. Ah, and I need to start planning our next planning.</em>”<br>“<em>You forgot about syncing with me about the budget</em>” Robin adds. “<em>That’s my action too. I already booked a slot in your calendar.</em>”<br>Alex: “<em>As per Sam, the TPS report.</em>”</p><p>I checked with the people in the meeting to ask them how this compared to a couple of weeks earlier. The feedback that I got was that this format is much more engaging, it helps with focus and the team felt that they were talking about the right things. The attendance at the meeting is now better because of the clear expectations and repeating who need to be there. Some people explained that they are missing hearing an in detail view of what others are doing. I suggested they bring up a timeline of the project in their next meeting before answering their 3 questions for everyone to glance over.</p><p><strong>Here are some things to think about if this resonates with you and you want to try to change something:</strong><br>What are the needs that you are trying to address with this meeting?<br>What is the purpose of the meeting<br>Is the format helping you address these needs?<br>What can you do to amplify the good parts and dampen the bad parts?</p><p><strong>What have you done to make meetings more engaging?</strong></p><p>Thanks <a href="https://www.linkedin.com/in/fionasiseman/">Fiona Siseman</a> for helping me think about meetings and <a href="https://www.linkedin.com/in/garyniemen/">Gary Niemen</a> for helping me think about words</p><p>Say hi to me on <a href="https://twitter.com/the_jus">twitter</a> or <a href="https://www.linkedin.com/in/justinkotze/">linkedin</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a22fab491bb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>