<?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 matt rayner on Medium]]></title>
        <description><![CDATA[Stories by matt rayner on Medium]]></description>
        <link>https://medium.com/@m.rayner?source=rss-88e6b32199e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*epTodOZaG40goN9O0HVmRA.png</url>
            <title>Stories by matt rayner on Medium</title>
            <link>https://medium.com/@m.rayner?source=rss-88e6b32199e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:52:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@m.rayner/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[Agile Risk Management]]></title>
            <link>https://medium.com/@m.rayner/agile-risk-management-d517bbd9339c?source=rss-88e6b32199e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d517bbd9339c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[matt rayner]]></dc:creator>
            <pubDate>Fri, 29 Apr 2016 11:20:52 GMT</pubDate>
            <atom:updated>2016-04-29T12:24:50.723Z</atom:updated>
            <content:encoded><![CDATA[<p>Yawn. Not exactly an exciting topic I admit*, and one that is neglected I tend to find in one of two ways by many organisations;</p><ol><li>It becomes a cottage industry, fetishised and ghettoised to the point where the people who are tasked to ‘care’ about risk management are so specialised and divorced from the day-to-day team that it becomes a time consuming and largely pointless activity.</li><li>One person on the team, usually the project manager, has a spreadsheet somewhere on a network drive that only they have ever seen. It gets dusted off once in a while, either for a programme board or because they are feeling a bit guilty about it and have a spare half hour. Oh, and they’ll have another sheet somewhere for issues too of course.</li></ol><p>I have worked places where people spent significant time copying from one to the other as risks materialised into issues, and I could never quite shake off the feeling that the time would be better spent actually <em>doing</em> something about it instead. And who the hell said that <strong><em>everyone must use MS Excel</em></strong> for this?</p><p>This doesn’t strike me as being a particularly healthy approach. For me, risk management only truly works if the whole project team is engaged with it on a daily basis. This means capturing risks in stand-up, and anywhere else they might appear, promptly and with the minimum of fuss. The reason most people disengage with the process is simply because it becomes way too much of a headache, and in general people don’t like thinking about unpleasant things anyway.</p><p>So don’t give them an excuse.</p><p>There perhaps isn’t much we can do directly about the latter issue, but we can at least recognise that a light-weight approach to looking after risks is better than effectively not bothering at all. Ideally the more lightweight the better — but for the rest of this article<em> I am assuming a couple of things</em>;</p><ol><li>You need to communicate risk to a wider community than just your core team <em>and/or</em></li><li>you don’t have the luxury of all being co-located in one small area.</li></ol><p>If that isn’t you, then you probably will manage your risks and issues as part of stand-up, and track them on your (preferred brand of agile) board. Lucky you!</p><p>For the rest of us however…</p><p>Over the last couple of years I started playing around with a Kanban-style workflow based approach to managing risk. There are a lot of online tools out there now that will allow you to do this — personally I quite like Trello. It has some distinct advantages over Excel for this activity;</p><ol><li>It lends itself well to running a workflow.</li><li>It is <strong><em>really</em></strong> easy to share across distributed, multi-party teams.</li><li>Everyone can collaborate.</li><li>It encourages conversations on a topic — and they are much easier to read (and automatically time-stamped too).</li><li>You can filter cards to show only what you need.</li><li>You can allocate as many people to a task as you like.</li><li>You can re-prioritise an item just be dragging it around.</li><li>Aesthetically, it is easier to pick up as a novice and less cluttered.</li><li>You can be automatically updated when an item changes. Or not, if you prefer.</li><li>It is free.</li></ol><p>The idea now is that you have cards, pinned to a board, organised into columns, or lists if you like. These lists are effectively ‘To do’, ‘Doing’ and ‘Done’ — although sometimes I add one for ‘Not pressing, but keep a bit of an eye on it’. The idea now is that ANYONE and EVERYONE on the team is expected to contribute to the board. On Trello this is easy — they can use the web, mobile app or even just send an email directly to the board to create a new risk in the ‘To do’ column. Don’t get anyone at this point to give it a RAG status, or complicated score — that will scare them off. Instead, the focus is just about capturing some basic info to describe the risk.</p><p>The next step is to sit down, for about 30 minutes once a week with the team and go over the board. This is an opportunity for everyone to put their heads together, look over the newly raised risks and categorise them depending on what they want to do with them. Play around with this — maybe you only want a small core team in this meeting, maybe it needs to be more than 30 minutes? But I strongly suggest starting with the <em>whole team for just 30 minutes</em> to maintain involvement, pace and interest. If you have one or two people whose responsibility it is to make sure risk management is happening, then they should be constantly refining the board anyway. This is just like you would refine a backlog during a sprint, so that your final sprint planning session is a relatively quick and painless meeting to finalise what will go into sprint.</p><p>Some of the ‘To do’ items you may decide you don’t care about that much so they can go straight to done. The others should be updated with a bit of commentary as to what is going to happen next, and who will be doing it, and maybe even by when — and then dragged kicking and screaming into ‘Doing’. The important point here is to play around with things, and incorporate into your regular retrospective/feedback sessions so that you can evolve this approach over time to fit your team. Once you’ve covered all the new stuff then move on to quickly review progress on the risks being managed in ‘Doing’. For this, try putting the risks that you care about most at the top of the list, and those you care about least at the bottom. Think about what you care about here — some organisations care deeply about impact and not so much about likelihood for example — especially when it comes to risks concerning their reputation. You may even want to combine top-to-bottom position ranking with a colour label.</p><p>If you have a PMO, and maybe a not-so-agile wider organisation that you have to slot into, then this might be when they start to add a few bits of info to the cards — maybe some labels to indicate the severity and likelihood. They might want to start tidying up the descriptions into a more standard format — ‘Cause’, ‘Effect’ and ‘Mitigation’ for example. They’ll know what they need — but it is best not to get too carried away at this stage.</p><p>If you need to track issues too, then consider using another label (but again, less is more), or maybe add another column so that you have ‘To do’, ‘Doing’ ‘Issues’ and ‘Done’ for example. Same goes for assumptions and dependancies.</p><p>With all this, experiment, but try to do only that which adds value to the team. It is easy to get carried away, and end up placing an onerous burden on the team that they then disengage from. Watch out for this, and if you see signs of it, consider trimming back, or heck, maybe even asking the team what they would like to see. Last but not least, consider giving your board a name other than ‘RAID Log’, and try to avoid phrases like ‘RAG status’ as these tend to be off-putting for a lot of folks. In a bad acronym-based pun, I’ve been trying to get the term Drywall to catch on with my team; I’ll let you know how I get on with that.</p><p>I’ve added some links to example Trello risk boards I have created. Feel free to copy them, mutate them and make them your own!</p><ul><li><a href="https://trello.com/b/9PHB5iAs/a-very-simple-risk-board">A very simple risk board</a></li><li><a href="https://trello.com/b/wLZBtm1g/a-simple-risks-and-issues-board">A simple risks and issues board</a></li><li><a href="https://trello.com/b/KfqL6U8i/a-combined-risks-issues-assumptions-dependancies-board">A combined risks, issues, assumptions &amp; dependancies board</a></li><li><a href="https://trello.com/b/0QjJBqbv/a-more-complicated-risks-issues-assumptions-and-dependancies-board">A more complicated risks, issues, assumptions and dependancies board</a></li></ul><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><em>*Why is that anyway? I always thought the risky stuff in life was supposed to be fun. Or at least pulse-raising.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d517bbd9339c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Password Suggestorator]]></title>
            <link>https://medium.com/@m.rayner/password-suggestorator-60e391ece301?source=rss-88e6b32199e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e391ece301</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[applescript]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[matt rayner]]></dc:creator>
            <pubDate>Wed, 02 Mar 2016 16:31:59 GMT</pubDate>
            <atom:updated>2016-09-19T15:38:33.643Z</atom:updated>
            <content:encoded><![CDATA[<p>I know it isn’t everyone’s cuppa tea, but Safari (on the Mac anyway) is pretty nice, and works well these days with Keychain. This allows folks, who might normally otherwise set all their passwords to “AuntMabel”, to set unique and strong passwords for the MANY websites we all sign up for these days. Now of course, a lot of people avoid this by just signing into everything using Facebook or Twitter, but frankly tying my entire digital life together into one easy to trawl location gives me the heeby-jeebies.</p><p>Safari got an update a couple of years ago so that when a website prompts you for a password, it will make a suggestion and offer to save it in Keychain. Nifty. But… what about if I am using Citymapper, where there is a website AND a native mobile app? iCloud stored Keychain items <em>typically</em> aren’t available to native apps (although <a href="https://support.apple.com/en-us/HT204085">this is changing</a>, albeit <em>really</em> slowly), so whilst if you stick to (mobile) Safari you’ll never have to type that password in, you will most likely need to in an app. You can access Keychain stored passwords on iOS (look in Settings →Safari →Passwords) and copy them out of there, but maybe it would be nice to have another option when generating the password in the first place? Something other than the AB1-DE2-HI3-KL4 format — which is a pain in the backside to type on a phone, and hard to remember.</p><p>Having a trawl around the net, I found other folks had wanted something similar, to be able to generate password suggestions in the same way that the Keychain app does, but from the Terminal prompt. This got me thinking that this would then be easy to call from an AppleScript/Automator service, which can then be called either from the Safari Services menu, or via a keyboard shortcut.</p><p>First off, you will need to <a href="http://brew.sh/">install Homebrew which you can get here</a>, the package manager project for OS X. It’s pretty cool and allows you to do a bunch of stuff, but for now, we’ll just be using it for getting the password command tool. It will probably prompt you to install XCode command line tools, which is a bit of Apple dev software. Fear not, this lot only takes a few minutes to do.</p><p>Once you have that, you need to head over to <a href="https://bitbucket.org/anders/sf-pwgen/">bitbucket to pick up the Homebrew command line tool, sf-pwgen</a>. Actually, you don’t really need to pick up the code there, but I wanted you to check that page out because a) you should be aware of where the code comes from, and b) it tells you how the command works with a bunch of different options. Anyone for Japanese word-phrase passwords? Hai!Skidesu.</p><p>To actually install sf-pwgen, fire up Terminal and run this line;</p><pre>brew install sf-pwgen</pre><p>It will prompt you along the way, so pay attention!</p><p>Once you have that you need to grab the script below and paste it into Script Editor on your Mac. Read those comments in the script — they are there for a reason!</p><pre> — Script relies on installing Mac Homebrew, and sf-pwgen</pre><pre> —  <a href="https://bitbucket.org/anders/sf-pwgen">https://bitbucket.org/anders/sf-pwgen</a></pre><pre> — Get them first, else the script will NOT work!</pre><pre> — Also, check where Brew installs sf-pwgen*, and update the variable ‘brewPath’ below accordingly</pre><pre> — * do this by opening terminal and typing “brew list sf-pwgen”</pre><pre> — One suggestion: take this script and save it as an app. Then create an Automator SERVICE Workflow which takes no input and save it with a “friendly” name. Restrict to Safari or Chrome if you like. Then go into System Prefs — Keyboard — Shortcuts and create a keyboard shortcut to invoke the app (take care to use the exact text that appears in the service menu) via the service and voila! You can trigger a password anytime you need from the keyboard!</pre><pre> — WARNING: It should be fine, but I offer no warranties on the use of this script. Use at your own risk, entirely. Don’t use it for highly sensitive passwords, just to be safe!</pre><pre><strong>tell</strong> <em>application</em> “Safari”</pre><pre><strong>set</strong> brewPath <strong>to</strong> “/usr/local/somewhere/sf-pwgen/1.3/bin/”</pre><pre> — You can get sf-pwgen to return five passwords, but that would have required text mangling in Applescript lists, so it seemed easier and probably quicker to just run sf-pwgen 5 times</pre><pre><strong>set</strong> myPasswords <strong>to</strong> {<strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1”, <strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1”, <strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1”, <strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1”, <strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1”}</pre><pre> — You can skip this repeat block if you like. It simply forces the first character of the passwords suggested to be uppercase. SO many websites insist on at least one character always being upper case. Sigh…</pre><pre><strong>set</strong> counter <strong>to</strong> 1</pre><pre><strong>repeat</strong> <strong>with</strong> myPassword <strong>in</strong> myPasswords</pre><pre><strong>set</strong> UpperFirstCharString <strong>to</strong> <strong>do shell script</strong> “echo “ &amp; <em>character</em> 1 <strong>of</strong> myPassword &amp; “ | tr [:lower:] [:upper:]”</pre><pre><strong>set</strong> <em>item</em> counter <strong>of</strong> myPasswords <strong>to</strong> UpperFirstCharString &amp; <em>characters</em> 2 <strong>through</strong> -1 <strong>of</strong> myPassword</pre><pre><strong>set</strong> counter <strong>to</strong> counter + 1</pre><pre> — log “myPassword is “ &amp; myPassword</pre><pre><strong>end</strong> <strong>repeat</strong></pre><pre> — Allow user to choose from a list of five suggestions (you could omit this and just copy one option with no review stage if you like)</pre><pre><strong>set</strong> selectedP <strong>to</strong> {<strong>choose from list</strong> myPasswords} <strong>as</strong> <em>text</em></pre><pre> — Put password onto clipboard ready for user</pre><pre><strong>set the clipboard to</strong> selectedP</pre><pre><strong>end</strong> <strong>tell</strong></pre><p>Save this as an Application (File Format=Application) to your Applications folder. Use a name something like ‘Password Suggestorator’.</p><p>Next steps:</p><ul><li>Launch Automator</li><li>Select ‘File →New’</li><li>Choose option for a Service (cog icon)</li><li>In the little search box in the left pane, type ‘launch’ and then drag the ‘Launch Application’ widget over to the actions pane</li><li>Set the dropdown ‘Service receives selected’ to ‘no input’ and set ‘in’ dropdown to ‘Safari’ if you only want this available in the Safari service menu.</li><li>Change the Launch Application dropdown to target the application you saved — ‘Password Suggestorator’</li><li>Save the service — suggest you use the same name as the app — ‘Password Generator’</li><li>You will now have a new option in the Services menu when you are in the Safari</li><li>Now launch ‘System Preferences’</li><li>Open the ‘Keyboard’ preference</li><li>Click on ‘Shortcuts tab’</li><li>Click on ‘App shortcuts’</li><li>Click the + button to add a new shortcut</li><li>Set Application dropdown to Safari</li><li>In the ‘Menu Title’ box enter the new services menu names as you saved them, e.g. ‘Password Suggestorator’</li><li>Click into the ‘Keyboard Shortcut’ box and press the keyboard shortcut combo you want to use to trigger the service.</li></ul><p>Feel free to tweak the AppleScript as much as you like. For example, I don’t use the default settings for sf-pwgen, and I don’t bother with the whole 5 options to choose from in the dropdown. How about something a little Germanic?</p><pre><strong>tell</strong> <em>application</em> “Safari”</pre><pre><strong>set</strong> brewPath <strong>to</strong> “/usr/local/somewhere/sf-pwgen/1.3/bin/”</pre><pre><strong>set</strong> myPassword <strong>to</strong> {<strong>do shell script</strong> brewPath &amp; “sf-pwgen -c1 -l20 -L de”} <strong>as</strong> <em>text</em></pre><pre> — Put password onto clipboard ready for user</pre><pre><strong>set the clipboard to</strong> myPassword</pre><pre><strong>end</strong> <strong>tell</strong></pre><p>Word of caution. I am NOT a coder! You use this entirely at your own risk! I am not responsible for the Homebrew package manager nor sf-pwgen. Maybe just use this for not very important passwords…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e391ece301" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>